From: Shing-Gene Yung <shing@cz3.nus.edu.sg>
To: egcs@egcs.cygnus.com
Subject: Re: glibc-2.1 + egcs -- no go
Date: Wed, 10 Mar 1999 17:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.05.9903110951190.25642-100000@kabod.cz3.nus.edu.sg> (raw)
In-Reply-To: < u8vhg98d3l.fsf@arthur.rhein-neckar.de >
yes, I did read through the FAQ and saw that entry. I've checked
/usr/lib/libc.so and it does have that "group". So I'm at a loss at what
to do next.
thanks,
--shing
On 10 Mar 1999, Andreas Jaeger wrote:
> >>>>> Shing-Gene Yung writes:
>
> > Hi,
> > I've managed to compile and install glibc-2.1 (from the rawhide dist)
> > using egcs-1.1.2-pre3...no errors. But when I try to rebuild
> > egcs-1.1.2pre3 or even just egcs-1.1.1, the make bootstrap fails with
> > undefined reference to fstat, stat, etc. What's the next step?
> You forgot the first step;-). Read the FAQ that comes with glibc
> 2.1, especially question 2.7:
> 2.7. Looking through the shared libc file I haven't found the
> functions `stat', `lstat', `fstat', and `mknod' and while
> linking on my Linux system I get error messages. How is
> this supposed to work?
>
> --
> Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
> for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de
>
WARNING: multiple messages have this Message-ID
From: Shing-Gene Yung <shing@cz3.nus.edu.sg>
To: egcs@egcs.cygnus.com
Subject: Re: glibc-2.1 + egcs -- no go
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.05.9903110951190.25642-100000@kabod.cz3.nus.edu.sg> (raw)
Message-ID: <19990331234600.0PXDZwhx8B98j7-1NFWftbiajwwzTXVhKX1vMS_6BTg@z> (raw)
In-Reply-To: <u8vhg98d3l.fsf@arthur.rhein-neckar.de>
yes, I did read through the FAQ and saw that entry. I've checked
/usr/lib/libc.so and it does have that "group". So I'm at a loss at what
to do next.
thanks,
--shing
On 10 Mar 1999, Andreas Jaeger wrote:
> >>>>> Shing-Gene Yung writes:
>
> > Hi,
> > I've managed to compile and install glibc-2.1 (from the rawhide dist)
> > using egcs-1.1.2-pre3...no errors. But when I try to rebuild
> > egcs-1.1.2pre3 or even just egcs-1.1.1, the make bootstrap fails with
> > undefined reference to fstat, stat, etc. What's the next step?
> You forgot the first step;-). Read the FAQ that comes with glibc
> 2.1, especially question 2.7:
> 2.7. Looking through the shared libc file I haven't found the
> functions `stat', `lstat', `fstat', and `mknod' and while
> linking on my Linux system I get error messages. How is
> this supposed to work?
>
> --
> Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
> for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de
>
next prev parent reply other threads:[~1999-03-10 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 8:18 Shing-Gene Yung
1999-03-10 10:26 ` Andris Pavenis
1999-03-31 23:46 ` Andris Pavenis
1999-03-10 11:29 ` Andreas Jaeger
[not found] ` < u8vhg98d3l.fsf@arthur.rhein-neckar.de >
1999-03-10 17:54 ` Shing-Gene Yung [this message]
1999-03-31 23:46 ` Shing-Gene Yung
1999-03-31 23:46 ` Andreas Jaeger
1999-03-31 23:46 ` Shing-Gene Yung
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=Pine.LNX.4.05.9903110951190.25642-100000@kabod.cz3.nus.edu.sg \
--to=shing@cz3.nus.edu.sg \
--cc=egcs@egcs.cygnus.com \
/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).