Re: [avr-libc-dev] Re: headers only / bootstrapping an avr toolchain

[Sven Köhler]

Rick Altherr schrieb:
>> Weddington, Eric schrieb:
>>> Do Gentoo developers not know how to read documentation?:
>>> <http://www.nongnu.org/avr-libc/user-manual/install_tools.html>
>>
>> I'm not sure who developed the avr-libc package for Gentoo. But it
>> turns out, that running
>>  crossdev --without-headers -S -t avr
>>
>> works just fine.
>>
>>> Information on how to build an AVR toolchain has been in the avr-libc
>>> user manual for a long time.
>>> If you just want to build a C and C++ toolchain for the AVR then
>>> build, in order:
>>> - binutils
>>> - gcc
>>> - avr-libc
>>> I also happen to build the Objective C compiler for the AVR (not that
>>> anyone in their right mind would use it), and I end up doing:
>>> - binutils
>>> - gcc, C compiler only (in essence just enough to build avr-libc)
>>> - avr-libc
>>> - gcc, full build for c, c++, objc
>>> I do this because the objc compiler needs to have the headers built
>>> and installed first. The C and C++ compilers don't seem to have a
>>> problem with that (at least for the AVR).
>>
>> So that could be a problem. So actually there is a dependency of the
>> gcc-package (including objc) on the avr-libc headers? So instead of
>> building gcc twice, it might be better to install avr-libc's headers
>> after binutils and before gcc?
>>
> 
> gcc only has a dependency on the avr-libc headers when building the objc
> compiler.  Since no one is likely to ever use objc, you could simply
> adjust the crossdev scripts to not attempt to build the objc compiler
> when building gcc.

Turns out, that even that problem has been solved already.

"crossdev --without-headers -S -s4 -t avr" builds packages in this order:
- binutils
- gcc (C only)
- avr-libc
- gcc (everything)

That should be fine.


Regards,
  Sven

signature.asc
Description: OpenPGP digital signature