From: Tim Prince <tprince@computer.org>
To: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux
Date: Thu, 20 Dec 2007 01:56:00 -0000 [thread overview]
Message-ID: <4769CBC8.8060705@computer.org> (raw)
In-Reply-To: <47694E5D.10207@cadenas.de>
Thomas Mittelstaedt wrote:
> and x86_64-unknown-linux-gnu/32/libmudflap/config.log says:
>
> configure:2308: checking for C compiler default output file name
> configure:2311: /localbuild/gcc-build/./gcc/xgcc
> -B/localbuild/gcc-build/./gcc/
> -B/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/bin/
> -B/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/lib/ -isystem
> /opt/gcc-4.2.2/x86_64-unknown-linux-gnu/include -isystem
> /opt/gcc-4.2.2/x86_64-unknown-linux-gnu/sys-include -m32
> -I/usr/include/i486-linux-gnu/ conftest.c >&5
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.so when
> searching for -lc
> /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.a when searching
> for -lc
> /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.so when
> searching for -lc
> /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.a when searching
> for -lc
> /usr/bin/ld: warning: i386:x86-64 architecture of input file
> `/usr/lib/../lib/crt1.o' is incompatible with i386 output
> /usr/bin/ld: warning: i386:x86-64 architecture of input file
> `/usr/lib/../lib/crti.o' is incompatible with i386 output
> /usr/bin/ld: warning: i386:x86-64 architecture of input file
> `/usr/lib/../lib/crtn.o' is incompatible with i386 output
Ubuntu decided to find a 64- vs 32- bit setup incompatible with
predecessor distros. Presumably, there is an ubuntu patch set for this,
but it's quite inconvenient that they chose to break the scheme chosen
by their predecessors. The scheme chosen by everyone else is to put the
64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib. Pretty
much the kind of mess Bill Gates wanted to see the alternatives get into.
next prev parent reply other threads:[~2007-12-20 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 9:09 Thomas Mittelstaedt
2007-12-19 12:36 ` John (Eljay) Love-Jensen
2007-12-19 13:34 ` Thomas Mittelstaedt
2007-12-19 14:32 ` Thomas Mittelstaedt
2007-12-19 15:00 ` Kai Ruottu
2007-12-19 15:14 ` Kai Ruottu
2007-12-19 15:03 ` Thomas Mittelstaedt
2007-12-19 16:55 ` Thomas Mittelstaedt
2007-12-20 1:56 ` Tim Prince [this message]
2007-12-20 6:17 ` Brian Dessent
2007-12-20 13:33 ` Problem building gcc-4.2.2 on 64-bit ubuntu linux, SUCCESS!! Thomas Mittelstaedt
2007-12-20 7:21 ` Problem building gcc-4.2.2 on 64-bit ubuntu linux Fabian Cenedese
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=4769CBC8.8060705@computer.org \
--to=tprince@computer.org \
--cc=T.Mittelstaedt@cadenas.de \
--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).