From: "Jean-Pierre Schwickerath" <gcc-list@schwicky.net>
To: "GCC-List" <gcc-help@gcc.gnu.org>
Subject: RE: Installation problem with gcc 2.95
Date: Thu, 15 Mar 2001 07:31:00 -0000 [thread overview]
Message-ID: <E14dZii-000161-00@mrvdom03.kundenserver.de> (raw)
In-Reply-To: <718D38CAB6E0D011B2C90060970C28A5642747@EXCHANGESERVER>
I'm wondering what's going on between gcc and the glibc
'cause you need a patch to compile gcc 2.95 with glibc 2.2. and glibc 2.2
doesn't compile with the gcc 3 pre snapshots...
I think there is some synchonizeing to be done in the next time....
Jean-Pierre
On Wed, 14 Mar 2001 17:10:30 -0000, David Korn said:
> >-----Original Message-----
> >From: Pipin, Janusz [ mailto:Janusz.Pipin@nrc.ca ]
> >Sent: 14 March 2001 16:11
>
> >On my workstation I've installed Linux version 7.0 and gcc installed is
> >2.96-54, however what I need is gcc version 2.95. I am getting
> >the following error messages from make bootstrap:
> >
> >make[2]: *** [indstream.o] Error 1
> >make[2]: Leaving directory
> >`/home/jpipin/gcc/gcc_object/i686-pc-linux-gnu/libio'
> >make[1]: *** [all-target-libio] Error 2
> >make[1]: Leaving directory `/home/jpipin/gcc/gcc_object'
> >make: *** [bootstrap] Error 2
>
> Unfortunately you trimmed your output too soon, and haven't shown the
> actual error. Something went wrong during the compilation of indstream.cc
> but all you've shown us is the make process noticing that it went wrong
> and aborting. We need a bit more context!
>
> However I'll take a quick guess, because this looks like a FAQ: you are
> trying to build gcc 2.95.2 on a system that has glibc 2.2 installed, and
> the error message you are getting is something like
>
> struct streampos used where a 'int' was expected
>
> and you this is because glibc 2.2 is not quite backwardly compatible with
> gcc 2.95.2; you will need to get the patch referred to here:
>
> http://gcc.gnu.org/install/specific.html#*-*-linux-gnu
>
> and apply it to the gcc / libio sources.
>
> DaveK
> --
> All your base are belong to us!
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
--
Jean-Pierre Schwickerath - Powered by GNU/LinuX!
E-Mail: email@schwicky.net - http://schwicky.net
PGP Key ID: 0x48C39212 - AIM: Schwicky - ICQ's UIN: 4690141
Nothing's impossible... Everything is relative!
next prev parent reply other threads:[~2001-03-15 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 9:10 David Korn
2001-03-15 7:31 ` Jean-Pierre Schwickerath [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-14 8:11 Pipin, Janusz
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=E14dZii-000161-00@mrvdom03.kundenserver.de \
--to=gcc-list@schwicky.net \
--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).