[gcc 4.7.0] enable gcc 4.7.0 with crosstool-ng 1.15.2

[Ovanes Markarian]

Hello Yann,


On Sat, May 12, 2012 at 10:50 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Ovanes, All,
>
> [Please, keep the list CCed when you reply, so all can benefit from the
> discussion (questions+answers) by searching the archives.]
Sorry, I used other mailing lists before and they were configured to
have reply address being the mailing list itself and not the user's
private one. I have overseen that now.

>
> On Saturday 12 May 2012 19:20:43 Ovanes Markarian wrote:
>> On Sat, May 12, 2012 at 5:31 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>> >> There is no gcc 4.7.0 version listed in the compiler list. How do I enable it?
>> > It's an 'experimental' feature, so you have to enable EXPERIMENTAL in the
>> > "Paths and Misc. options" sub-menus. Support for gcc-4.7.0 is very new, so
>> > be prepared for breakage.
>> Can you please specify which breakage you mean? I need 4.7 as I would
>> like to use the C++ 11 features.
>
> I have no specific in mind. As an example, there was a bug in the pristine
> release of 4.7.0 that broke uClibc, and so crosstool-NG bundles a
> patch to gcc-4.7.0 (as it does for all versions of gcc).
Ok, I use eglibc and it works fine. But now I run in the issue, where
I would like to statically link the toolchain (Experimental feature as
well) and the problem is that binutils no longer compile. I get two
errors that BFD_VERSION_STRING and REPORT_BUGS_TO are not set. Don't
know why it has to do with static linking but that is the blocking
point for me now. As a quick work-around I tried to set CFLAGS
environment variable (in additional config options for binutils) which
defined these two items, but it did not work either. Since (I don't
know which of the build steps) the ' " ' were stripped from the
define, so:
CFLAGS="-DBFD_VERSION_STRING=\"2.22\" -DREPORT_BUGS_TO=((char*)\"\")"
becomes in the command line when invoked:
-DBFD_VERSION_STRING=2.22 -DREPORT_BUGS_TO=((char*))

I don't know if other tools are going to build as well, but I would be
interested to know, how this Experimental feature was tested? Because
I tried it with all binutils versions ranging form 2.18a until 2.22
and all failed.

I decided to go with static linking because on some machines, where I
tested it CLooG and PPL were not installed and therefore not found.
What I actually need is only statically linked GCC. binutils can be
used as a shared lib. Is there any chance to configure the toolchain
that way?

>
>> The most discouraging point was that
>> after menu config crosstool-ng started the compilation without finding
>> out that choosen lib versions were not compatible, e.g. after spending
>> like half an hour building the toolchain I was notified that PPL must
>> be version 11 or higher for the choosen config.
>
> Yes, it is a known /limitation/. There is no easy way to overcome this
> limitation without complicating the configuration and keep it maintainable.
>
>> If someone likes, I can post my config script.
>
> Yes, please. If it is not already covered by an existing sample, I'll add
> it to the samples bundled with crosstool-NG.
As soon as I will fix the issues I will post it.

>
> Regards,
> Yann E. MORIN.

Many thanks for you help,
Ovanes

--
For unsubscribe information see http://sourceware.org/lists.html#faq