From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: can't run gcc 4.5.3/4.6.0 under ubuntu 11.04
Date: Thu, 19 May 2011 10:39:00 -0000 [thread overview]
Message-ID: <4DD4CDCC.8000505@wippies.com> (raw)
In-Reply-To: <20110519044837.25100@gmx.net>
19.5.2011 7:48, Klaus Rudolph kirjoitti:
> Marc Glisse wrote:
>>
>> If you keep only the system ld (don't install your own) and compile a new
>> gcc, does it work?
>
> Without building own binutils it works.
Yes, the 'ld -> ld.bfd' in Ubuntu 11.04 seems to be patched to search
from more places than the usual '/lib*' and '/usr/lib*'. Using the
command :
ld -verbose | less
will show the built-in search directories and linker script...
>>> Using system ld instead of system gcc is changing nothing, or?
>>
>> The difference is whether gcc passes different options to ld or ld was
>> compiled with different options (or patches). If you insist on compiling
>> your own, the first thing to do would be to check how the ubuntu versions
>> were compiled.
>>
>
> There is already a bug report for this item:
> https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/738098
>
> In hope the changes for ubuntu could shared with standard binutils or a bugfix for ubuntu will arise.
>
> I will begin with building without own binutils
This whole issue is one-eyed and forgets cross-compiling completely,
with this one as default will :
- use the original Ubuntu 11.04 glibc etc C libraries in their native
install scheme in a $sysroot
- produce GNU binutils from sources, usually from the Linux ones at
ftp.kernel.org
- produce GCC from sources, usually from the FSF ones
I wouldn't expect the '--with-sysroot=' changing the default search
paths in 'ld' in the 'i686-ubuntu-linux-gnu' case in any way although
it seems that Ubuntu isn't any normal/standard Linux at all but tries
to be a custom one with customized install paths for its C libraries.
Nothing however disables one to normalize the install directories in
the $sysroot to follow the expected Linux standards...
next prev parent reply other threads:[~2011-05-19 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 8:22 Klaus Rudolph
2011-05-18 9:06 ` Axel Freyn
2011-05-18 9:43 ` Marc Glisse
2011-05-18 10:20 ` Klaus Rudolph
2011-05-18 10:41 ` Marc Glisse
2011-05-18 12:18 ` Klaus Rudolph
2011-05-18 13:25 ` Marc Glisse
2011-05-19 7:59 ` Klaus Rudolph
2011-05-19 10:39 ` Kai Ruottu [this message]
2011-05-18 9:53 ` Jonathan Wakely
2011-05-18 10:05 ` Klaus Rudolph
2011-05-18 20:52 ` kevin diggs
2011-05-19 0:11 ` Jonathan Wakely
2011-05-18 10:23 Klaus Rudolph
2011-05-19 0:26 ` Ian Lance Taylor
2011-05-19 4:48 ` Jeffrey Walton
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=4DD4CDCC.8000505@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@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).