From: Kai Ruottu <karuottu@mbnet.fi>
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: Wed, 19 Dec 2007 15:00:00 -0000 [thread overview]
Message-ID: <476933CB.6060700@mbnet.fi> (raw)
In-Reply-To: <47692CD3.7040708@cadenas.de>
Thomas Mittelstaedt wrote:
> Okay, restartet from scratch with the following, but the
I/usr/include/i486-linux-gnu/ would still not propagate.
A 64-bit Linux should have its bi-arch (for 64- and 32-bit) native
headers in fully usual '/usr/include'. So your '-I'
should be totally vain....
> /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or
directory
This should come with the optional 32-bit development headers &
libraries, in an install package like:
ftp://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive/pool/main/g/glibc/libc6-dev-i386_2.7-4ubuntu1_amd64.deb
Just check what your installed glibc version is and then try to find the
missing component for it. Maybe there
is some simple "package installer" in Ubuntu, letting you to choose
something like "32-bit development libraries"
to be installed.
next prev parent reply other threads:[~2007-12-19 15:00 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 [this message]
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
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=476933CB.6060700@mbnet.fi \
--to=karuottu@mbnet.fi \
--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).