From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-22
Date: Thu, 23 Jul 2015 23:20:58 +0200 [thread overview]
Message-ID: <55B15ABA.7080106@openwide.fr> (raw)
In-Reply-To: <20150723231451.29f5fd92@free-electrons.com>
Thomas,
Le 23/07/2015 23:14, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
>
> On Thu, 23 Jul 2015 23:03:43 +0200, Romain Naour wrote:
>
>> Here is the content of CFLAGS_FOR_TARGET and CXXFLAGS_FOR_TARGET:
>>
>> CFLAGS_FOR_TARGET="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>> -D_FILE_OFFSET_BITS=64 -mlongcalls -mtext-section-literals -Os "
>>
>> CXXFLAGS_FOR_TARGET="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>> -D_FILE_OFFSET_BITS=64 -mlongcalls -mtext-section-literals -Os "
>>
>> Probably -mtext-section-literals is the culprit...
>>
>> Ah! did you notice the typo in Alexey's patch ?
>> +# Propagate options used for target software building to GCC target libs
>> +HOST_GCC_COMMON_CONF_ENV += CFLAGS_FOR_TARGET="$(GCC_COMMON_TARGET_CXXFLAGS)"
>> ^^^ ^^^
>
> Well spotted. But since the CFLAGS and CXXFLAGS are the same, how is it
> going to fix anything?
It doesn't fix anything for the xtensa issue :)
It's for the correctness.
Romain
>
> Thomas
>
next prev parent reply other threads:[~2015-07-23 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-22 Thomas Petazzoni
2015-07-23 12:54 ` Julien CORJON
2015-07-23 17:51 ` Romain Naour
2015-07-23 20:11 ` Thomas Petazzoni
2015-07-23 21:03 ` Romain Naour
2015-07-23 21:14 ` Thomas Petazzoni
2015-07-23 21:20 ` Romain Naour [this message]
2015-07-23 21:30 ` Max Filippov
2015-07-23 21:53 ` Thomas Petazzoni
2015-07-24 9:31 ` Max Filippov
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=55B15ABA.7080106@openwide.fr \
--to=romain.naour@openwide.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.