From: Thierry Bultel <tbultel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] grub2 failure with gcc-4.9
Date: Thu, 05 Feb 2015 15:56:00 +0100 [thread overview]
Message-ID: <54D38480.3040101@free.fr> (raw)
In-Reply-To: <54D37B54.7080700@free.fr>
Le 05/02/2015 15:16, Thierry Bultel a ?crit :
> Le 05/02/2015 14:20, Thomas Petazzoni a ?crit :
>> Dear Thierry Bultel,
>>
>> On Thu, 05 Feb 2015 13:54:17 +0100, Thierry Bultel wrote:
>>
>>> After some (printf) debugging, I found out that when 'loading' the
>>> builtin modules at startup, some modules names are corrupted.
>>> I am about to get into deeper investigation, but has anyone
>>> encountered it ?
>>
>> Interesting.
>>
>> First suggestions:
>>
>> - try with another gcc 4.9 toolchain (distro toolchain or something)
>>
>> - try with different optimization levels (default of Buildroot is -Os,
>> try with -O0 and -O2)
>>
>
> It seems that when building the target part, grub is using CXXFLAGS
> (from $(HOST_CONFIGURE_OPTS)) in addition of TARGET_CFLAGS.
> Thus we have both -0s and -O2 in command line.
>
> Unfortunately that is not the cause of the bug, because -02 (twice)
> makes it happen.
>
> Trying another toolchain ...
FYI, loops rebooting with gcc-4.7 from
BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_X86_201209
>
>> Thomas
>>
>
next prev parent reply other threads:[~2015-02-05 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 12:54 [Buildroot] grub2 failure with gcc-4.9 Thierry Bultel
2015-02-05 13:20 ` Thomas Petazzoni
2015-02-05 14:16 ` Thierry Bultel
2015-02-05 14:56 ` Thierry Bultel [this message]
2015-02-05 16:15 ` Thierry Bultel
2015-02-05 16:16 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2015-02-19 16:03 [Buildroot] Fwd: " Steve Kenton
2015-02-20 16:34 ` [Buildroot] " tbultel at free.fr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D38480.3040101@free.fr \
--to=tbultel@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.