From: Anthony Green <green@moxielogic.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: rmansfield@qnx.com, gcc-patches@gcc.gnu.org, ak@linux.intel.com,
DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] [PATCH] Report LTO phase in lto1 process name v2
Date: Fri, 19 Nov 2010 09:15:00 -0000 [thread overview]
Message-ID: <4CE5F69B.8030603@moxielogic.com> (raw)
In-Reply-To: <2c21fce12c39a294a70aa8b3ac943d0f.squirrel@www.firstfloor.org>
On 11/18/2010 5:41 PM, Andi Kleen wrote:
> > You shouldn't be using link tests universally in libiberty either. Many
>> newlib based targets can't build executables at this point in the
>> toolchain build.
>>
>> If you look earlier in configure.ac you'll see...
>>
>> # We are being configured as a target library. AC_REPLACE_FUNCS
>> # may not work correctly, because the compiler may not be able to
>> # link executables. Note that we may still be being configured
>> # native.
>>
>> At a minimum you should wrap all this with a test for with_newlib = no.
>>
>> The moxie-elf toolchain doesn't build right now because of this.
>
> How does it fail? In theory you should just not get
> process name support.
The configure script exits with "Link tests are not allowed after
GCC_NO_EXECUTABLES.".
AG
next prev parent reply other threads:[~2010-11-19 4:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 21:33 green
2010-11-18 23:46 ` Andi Kleen
2010-11-19 9:15 ` Anthony Green [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-06 15:49 Andi Kleen
2010-10-06 15:51 ` Diego Novillo
2010-10-06 17:32 ` Andrew Pinski
2010-10-06 17:42 ` Andi Kleen
2010-10-06 17:47 ` Richard Henderson
2010-10-06 17:49 ` DJ Delorie
2010-10-06 17:51 ` Andi Kleen
2010-10-06 20:06 ` DJ Delorie
2010-10-06 21:41 ` Andi Kleen
2010-10-06 22:07 ` DJ Delorie
2010-10-07 3:17 ` Ryan Mansfield
2010-10-07 6:32 ` Andi Kleen
2010-10-07 6:40 ` DJ Delorie
2010-10-07 7:23 ` Andi Kleen
2010-10-07 9:32 ` Andi Kleen
2010-10-07 10:03 ` Ryan Mansfield
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=4CE5F69B.8030603@moxielogic.com \
--to=green@moxielogic.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rmansfield@qnx.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).