From: Ian Lance Taylor <iant@google.com>
To: Olumide <50295@web.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Wed, 19 Jan 2011 16:21:00 -0000 [thread overview]
Message-ID: <mcrtyh4985i.fsf@google.com> (raw)
In-Reply-To: <4D37089F.50700@web.de> (Olumide's message of "Wed, 19 Jan 2011 15:51:59 +0000")
Olumide <50295@web.de> writes:
> On 19/01/2011 15:02, Cedric Roux wrote:
>> On 01/19/2011 03:48 PM, Olumide wrote:
>>> /usr/include/gnu/stubs.h:7:27:/usr/include/gnu/stubs.h:7:27:
>>> error: error: gnu/stubs-32.h: No such file or directorygnu/stubs-32.h:
>>> No such file or directory
>>
>> pass --disable-multilib to configure
>
> The build fails with the following error:
>
> make[6]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build/gcc'
> echo timestamp > stmp-multilib
> make[5]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build/gcc'
> echo timestamp > stage3_build
> echo stage3_build > stage_last
> make[4]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build/gcc'
> make[3]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build/gcc'
> make[2]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/transfer/gcc412/gcc-4.1.2/build'
You did not include enough of the make log. You need to look farther up
to see what the actual error is.
Ian
next prev parent reply other threads:[~2011-01-19 16:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51 ` Olumide
2011-01-19 16:21 ` Ian Lance Taylor [this message]
2011-01-19 16:37 ` Olumide
2011-01-19 16:39 ` Andrew Haley
2011-01-19 17:08 ` Olumide
2011-01-19 17:11 ` Andrew Haley
2011-01-19 20:13 ` Olumide
2011-01-19 21:51 ` David Daney
2011-01-20 13:56 ` Olumide
2011-01-20 17:23 ` Olumide
2011-01-20 20:04 ` Jonathan Wakely
2011-01-25 10:30 ` Olumide
2011-01-25 10:59 ` Kai Ruottu
2011-01-25 10:59 ` Jonathan Wakely
2011-01-25 11:34 ` Olumide
2011-01-25 11:56 ` Jonathan Wakely
2011-01-25 13:51 ` Olumide
2011-01-19 16:43 ` Cedric Roux
2011-01-19 16:47 ` Jonathan Wakely
2011-01-19 15:19 ` Jeff Law
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=mcrtyh4985i.fsf@google.com \
--to=iant@google.com \
--cc=50295@web.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).