From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: B B <dev@thecercle.org>
Cc: "ron.stubbs@duke.edu" <ron.stubbs@duke.edu>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Compilation Error
Date: Wed, 15 Aug 2012 19:25:00 -0000 [thread overview]
Message-ID: <CAH6eHdS-Gutd+SqNavq5PBAVR2EOkQnHfJimo6wX2p535=SzEg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
Resending as plain text mail....
On 15/08/2012, Jonathan Wakely wrote:
> On Wednesday, 15 August 2012, B B <dev@thecercle.org> wrote:
>> I guess for Scientific Linux it's something like
>> yum -y install glibc-devel
>>
>> ...?
>
>
> glibc-devel.i686
>
>
>
>> B.
>>
>>
>> On 8/15/12 7:57 PM, "Ron Stubbs" <rons@duke.edu> wrote:
>>
>>>Hi,
>>>
>>>I get the following errors when building gcc-4.8-20120812:
>>>======================================
>>>In file included from /usr/include/features.h:385:0,
>>> from /usr/include/stdio.h:28,
>>> from ../../.././libgcc/../gcc/tsystem.h:88,
>>> from ../../.././libgcc/libgcc2.c:29:
>>>/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file
>>>or directory
>>> # include <gnu/stubs-32.h>
>>> ^
>>>compilation terminated.
>>>make[5]: *** [_muldi3.o] Error 1
>>>make[5]: Leaving directory
>>>`/opt/gcc-4.8-20120812/x86_64-unknown-linux-gnu/32/libgcc'
>>>make[4]: *** [multi-do] Error 1
>>>make[4]: Leaving directory
>>>`/opt/gcc-4.8-20120812/x86_64-unknown-linux-gnu/libgcc'
>>>make[3]: *** [all-multi] Error 2
>>>make[3]: Leaving directory
>>>`/opt/gcc-4.8-20120812/x86_64-unknown-linux-gnu/libgcc'
>>>make[2]: *** [all-stage1-target-libgcc] Error 2
>>>make[2]: Leaving directory `/opt/gcc-4.8-20120812'
>>>make[1]: *** [stage1-bubble] Error 2
>>>make[1]: Leaving directory `/opt/gcc-4.8-20120812'
>>>make: *** [all] Error 2
>>>========================================
>>>
>>>Suggestions?
>>>
>>>Thanks,
>>>Ron
>>>
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>Ron Stubbs MS CS
>>>Senior Systems Programmer
>>>Research Computing
>>>Pratt School of Engineering
>>>410 Teer Bldg. P.O. Box 90271
>>>Duke University, Durham, N.C. 27708-0271
>>>office: (919)660-5339 cell:(919)641-5689
>>>fax: (919) 613-9156
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>
next prev parent reply other threads:[~2012-08-15 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 14:34 Configuration Error Ron Stubbs
2012-08-15 15:43 ` Jonathan Wakely
2012-08-15 17:49 ` B B
2012-08-15 17:57 ` Jonathan Wakely
2012-08-15 18:03 ` Compilation Error Ron Stubbs
2012-08-15 18:14 ` Marc Glisse
2012-08-15 18:46 ` B B
[not found] ` <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
2012-08-15 19:25 ` Jonathan Wakely [this message]
2012-08-15 19:36 ` Ron Stubbs
2012-08-16 3:59 ` Marc Glisse
2012-08-16 13:29 ` Ron Stubbs
2012-08-16 15:15 ` Tim Prince
2012-08-16 20:06 ` Marc Glisse
2012-08-17 0:12 ` Ron Stubbs
2012-08-17 7:23 ` Marc Glisse
2012-08-17 8:23 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2011-06-08 12:25 compilation error Rony Paul
2011-06-08 13:31 ` Jonathan Wakely
2011-06-08 13:47 ` Ian Lance Taylor
2006-10-07 18:58 ranjith kumar
2006-10-07 19:36 ` Tim Prince
2005-07-18 4:24 Compilation error Oleg Kotsyurbiy
2005-07-18 5:51 ` Ian Lance Taylor
2005-07-18 7:45 ` Arturas Moskvinas
2000-02-21 10:27 Jose Miguel A.C.Pires
2000-02-21 10:39 ` llewelly
2000-04-01 0:00 ` llewelly
2000-04-01 0:00 ` Jose Miguel A.C.Pires
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='CAH6eHdS-Gutd+SqNavq5PBAVR2EOkQnHfJimo6wX2p535=SzEg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dev@thecercle.org \
--cc=gcc-help@gcc.gnu.org \
--cc=ron.stubbs@duke.edu \
/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).