public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jocke at vmlinux dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/41818] Error building cross compiler caused by changing LD_LIBRARY_PATH environment variable in Makefile
Date: Wed, 06 Jan 2010 13:53:00 -0000 [thread overview]
Message-ID: <20100106135309.32335.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41818-17617@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from jocke at vmlinux dot org 2010-01-06 13:53 -------
I can confirm this issue while building an armeb-unknown-uclibcgnueabi
(big-endian) cross toolchain on i686 (Ubuntu 9.10 32-bit) using crosstool-NG.
However, I cannot replicate it on any host running x86_64 (Ubuntu 9.04 or 9.10,
64-bit). Also, when building a arm-unknown-uclibcgnueabi (little-endian) this
bug is not triggered. Maybe that helps.
Some of the messages in the official mailing list archive related to this issue
have somehow been lost (?),
http://gcc.gnu.org/ml/gcc-bugs/2009-10/msg02122.html (see the thread view). I
found
http://old.nabble.com/Re:-Error-when-building-cross-compiler-td25755999.html
where Kai Ruottu gave some interesting insight.
The bug can be worked around by adding the --disable-shared configure option to
the last (final) stage in the compiler build.
--
jocke at vmlinux dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jocke at vmlinux dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41818
next prev parent reply other threads:[~2010-01-06 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 20:08 [Bug bootstrap/41818] New: " denis dot onischenko at gmail dot com
2009-10-24 20:23 ` [Bug bootstrap/41818] " denis dot onischenko at gmail dot com
2009-10-25 21:00 ` pinskia at gcc dot gnu dot org
2009-10-25 21:01 ` pinskia at gcc dot gnu dot org
2010-01-06 13:53 ` jocke at vmlinux dot org [this message]
2010-01-06 17:33 ` rwild at gcc dot gnu dot org
2010-01-06 20:19 ` denis dot onischenko at gmail dot com
2010-01-06 20:32 ` jocke at vmlinux dot org
2010-01-07 19:54 ` rwild at gcc dot gnu dot org
2010-01-07 19:57 ` rwild at gcc dot gnu dot org
2010-02-27 1:21 ` pinskia at gcc dot gnu dot org
2010-08-05 23:29 ` lacombar at gmail dot com
2010-08-06 0:01 ` lacombar at gmail dot com
2010-08-07 14:18 ` rwild 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=20100106135309.32335.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).