public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yakov at emc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
Date: Mon, 24 Mar 2008 20:29:00 -0000 [thread overview]
Message-ID: <20080324202912.2228.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35679-13942@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from yakov at emc dot com 2008-03-24 20:29 -------
Subject: Re: Cannot build cross compiler for i686-pc-linux-gnu:
configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
Brian,
first, thank you very much for such a quick response.
Actually, this target is i[3456789]86-*-elf) /*gcc-4.3.0/configure */
sincerely,
yakov
brian at dessent dot net wrote:
> ------- Comment #1 from brian at dessent dot net 2008-03-24 19:54 -------
> Subject: Re: New: Cannot build cross compiler for
> i686-pc-linux-gnu: configure: error: Link tests are not allowed after
> GCC_NO_EXECUTABLES
>
> yakov at emc dot com wrote:
>
>
>> --target=i686-emc-elf --enable-languages=c++ --disable-multilib --with-gnu-as
>>
>
> Your title for this bug is misleading as it seems you're building a
> cross for a newlib bare metal target, not i686-pc-linux-gnu. That's
> just the host, and is irrelevant to the issue.
>
> There is currently a known problem with the libstdc++ configury and bare
> metal newlib targets. You can fix it either by providing BSP files
> (crt*.o, linker script, etc) for your board so that test programs can be
> linked, or you can disable the AC_LIBTOOL_DLOPEN check in
> libstc++-v3/configure.ac for newlib targets, as in
> <http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html>. For a summary of the
> history of this issue:
> <http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html>.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35679
next prev parent reply other threads:[~2008-03-24 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:34 [Bug libstdc++/35679] New: " yakov at emc dot com
2008-03-24 19:55 ` [Bug libstdc++/35679] " brian at dessent dot net
2008-03-24 20:29 ` yakov at emc dot com [this message]
2008-03-30 20:20 ` pinskia at gcc dot gnu dot org
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=20080324202912.2228.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).