Should include the same version of gcc as the linux kernel

[wyattwong]

I found that the latest Raspbian Debian Wheezy (updated on 16-Feb-2015) linux kernel was built with gcc-4.8.3

pi@raspberrypi / $ cat /proc/version
Linux version 3.18.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015

However, the bundled gcc is version 4.6.3. It would be nice to always bundled the *SAME* version of gcc as what the linux kernel was built with so that people can use it to build applications or device drivers.

[PeterO]

I found that the latest Raspbian Debian Wheezy (updated on 16-Feb-2015) linux kernel was built with gcc-4.8.3

pi@raspberrypi / $ cat /proc/version
Linux version 3.18.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015

However, the bundled gcc is version 4.6.3. It would be nice to always bundled the *SAME* version of gcc as what the linux kernel was built with so that people can use it to build applications or device drivers.

+1

It is a pain when you want to build a module for your own hardware and you have to find and install the appropriate gcc. The version SHOULD match. I don't ever remember them being out of step on any other platform.

PeterO

[enedil]

And why it's done that way?

Answer is simple:
Debian version used to create Raspbian is Wheezy, which is currently stable. Which means that there won't be non-security updates. So the GCC version released is 4.6. However, newer compilers provide better binary files (faster, smaller). That's the reason of compiling Linux kernel with GCC 4.8.

[sbp]

I agree.

Please fix this.

[wyattwong]

And why it's done that way?

Answer is simple:
Debian version used to create Raspbian is Wheezy, which is currently stable. Which means that there won't be non-security updates. So the GCC version released is 4.6. However, newer compilers provide better binary files (faster, smaller). That's the reason of compiling Linux kernel with GCC 4.8.

But if the kernel is built by gcc-4.8.3, the Raspbian image should include the SAME version of gcc so that user can use the same gcc for building other softwares and device drivers. I don't see any reason for not including gcc-4.8.3 into the Raspbian image.

[jojopi]

I believe this is the toolchain used to build the Foundation's kernels: https://github.com/raspberrypi/tools/tr ... spbian-x64

Since it requires an x86-64 host, there would be little point including it in a Raspbian image. You cannot use it to compile "other software" without first setting up target libraries to match those in Raspbian.

If you need extra modules, compile the whole kernel and modules using the same config. Use whatever compiler you prefer.

[PeterO]

I believe this is the toolchain used to build the Foundation's kernels: https://github.com/raspberrypi/tools/tr ... spbian-x64

Since it requires an x86-64 host, there would be little point including it in a Raspbian image. You cannot use it to compile "other software" without first setting up target libraries to match those in Raspbian.

If you need extra modules, compile the whole kernel and modules using the same config. Use whatever compiler you prefer.

Nonsense ! The correct version is available natively in the jessie repo so only a matter of back porting it into the current Raspbian. On my A+ I have it installed because I'm building I2S modules.

PeterO

[enedil]

GCC is a critical component. No one can tell that v4.8 is enough stable and bug-free to enter stable stage. Nobody wants to guarantee the non-tested software. That's why GCC 4.8 is not included. And installing GCC 4.8 is quite easy, so no need of.

[wyattwong]

GCC is a critical component. No one can tell that v4.8 is enough stable and bug-free to enter stable stage. Nobody wants to guarantee the non-tested software. That's why GCC 4.8 is not included. And installing GCC 4.8 is quite easy, so no need of.

I am sure no one (I mean anyone, everyone) can guarantee **ANY** software (be it GCC, Visual C++, Windows, OS X, Office, etc.) are stable enough and bug-free to enter stable stage. And someone use this gcc-4.8-3 (maybe not stable enough?) to build the Linux kernel for Raspbian Debian Wheezy, what is the logic behind then ?

Installed gcc-4.8 to Raspbian is different from gcc-4.8.3, I need to follow the steps in the following URL to successfully installed to my Raspbian Debian Wheezy Linux. But why the fuss that I need to do so if gcc-4.8.3 was bundled *NATIVELY* with the Raspbian Debian Wheezy Linux ?

https://github.com/notro/rpi-source/wiki

Anyway, it is ONLY my suggestion.

[PeterO]

https://github.com/notro/rpi-source/wiki

Code: Select all

Discontinued
2015-02-11
I haven't got the time to maintain this anymore. If anyone want's to pick it up, please do.
It doesn't work with the Pi2 kernel.

rpi-source installs the kernel source used to build rpi-update kernels and the kernel on the Raspian image.

OH That is bad news. I have not tried it yet on a Pi2 as my module work is on an A+, but I'm sure at some point I will want to build a module for a Pi2. Do you know if he stopping maintaining it because of the gcc version mismatch or are there other PI2 kernel issues (such as ARM version change) or is it just the time needed ?

PeterO

[AndyD]

... Do you know if he stopping maintaining it because of the gcc version mismatch or are there other PI2 kernel issues (such as ARM version change) or is it just the time needed ?

The development of fbtft has moved into the Linux Kernel, so notro probably isn't using the Raspberry Pi kernel source any longer.

[PeterO]

The development of fbtft has moved into the Linux Kernel, so notro probably isn't using the Raspberry Pi kernel source any longer.

Ah I see, I just tried to PM him on this forum but he has PMs disabled .... I would be interested in keeping it maintained if he can offer to "hand hold" for a few months.

PeterO

[wyattwong]

His steps work in my RPi 2 and I can installed gcc-4.8.3 to my RPi 2 (I got RPi 1 B+ but haven't try his steps yet). Unfortunately I was unable to build a workable rtl8188eu for my Mercury 150Mbps wifi dongle using gcc-4.8.3. Luckily someone had kindly built it and provided a binary version for me and it works. Maybe I should save the website just in case it will be gone in the near future.

[PeterO]

notro has accepted my offer of help to keep rpi-source up to date.
It will be after the Brithday Party before I get time to "get on board" though.

PeterO

[wyattwong]

You mean you will take over to maintain the page for him ?

[jojopi]

Nonsense ! The correct version is available natively in the jessie repo so only a matter of back porting it into the current Raspbian.

Not really. Linaro 2014.03 is branched from prerelease GCC 4.8.3, but it is not the same compiler as upstream. In fact, it is significantly different, especially in the area of ARM code generation, or there would be no reason for it to exist at all. Debian GCC is not upstream either, and it happens to include patches derived from Linaro, but jessie's 4.8.3-13 was released in October, so it is probably closer to Linaro 2014.11.

Quite simply, the reason the GCC version in Raspbian does not match the kernel is that the Foundation do not compile their kernels on Raspbian. It is illogical to expect them to make available a compiler that is not the one they use and could not be guaranteed to be functionally identical.

Of course, it probably works fine to compile modules with a different GCC and then load them in the Foundation kernel. Or you can compile the whole kernel and modules together, as I recommend. Compiler version is not even the biggest issue with additional or out of tree modules. They only work when the module has no non-module prerequisite configuration options.

[PeterO]

So you seem to be saying that there are multiple different compilers all claiming to be 4.8.3 ? If this is true then some need shooting as that is a totally indefensible situation !
PeterO

[PeterO]

You mean you will take over to maintain the page for him ?

And maintain the code as well as I've been using it to build a couple of very simple modules for an I2S audio input codec break out board.
PeterO

[wyattwong]

Nonsense ! The correct version is available natively in the jessie repo so only a matter of back porting it into the current Raspbian.

Not really. Linaro 2014.03 is branched from prerelease GCC 4.8.3, but it is not the same compiler as upstream. In fact, it is significantly different, especially in the area of ARM code generation, or there would be no reason for it to exist at all. Debian GCC is not upstream either, and it happens to include patches derived from Linaro, but jessie's 4.8.3-13 was released in October, so it is probably closer to Linaro 2014.11.

Quite simply, the reason the GCC version in Raspbian does not match the kernel is that the Foundation do not compile their kernels on Raspbian. It is illogical to expect them to make available a compiler that is not the one they use and could not be guaranteed to be functionally identical.

Of course, it probably works fine to compile modules with a different GCC and then load them in the Foundation kernel. Or you can compile the whole kernel and modules together, as I recommend. Compiler version is not even the biggest issue with additional or out of tree modules. They only work when the module has no non-module prerequisite configuration options.

So you mean we cannot build gcc-4.8.3 into binaries from the GNU source (http://www.gnu.org/software/gcc/) in Raspberry Pi because the Raspberry Pi Linux kernel is built with a different gcc source (i.e Linaro 2014.03) ? And using the Linaro 2014.03 source can we build the correct Raspberry Pi Linux kernel (with ARM code).

If we need to build a gcc-4.8.3 for use in Raspberry Pi, we should to use a PC or Mac for cross-build the compiler and then transfer the binary into Rapsberry Pi ?

Furthermore, if we have to build some device drivers for use in Raspberry Pi, we should build the device driver as well as the whole Linux kernel in Raspberry Pi instead of just building the device drivers into binaries. And we need to deploy both the kernel.img and the device driver binaries to Raspberry Pi to guarantee that the device driver work as expected ?

If that is so, I think the building of device drivers is more complicated in Raspberry Pi