From: npsimons@nmt.edu
To: (H.J. Lu) <hjl@lucon.org>
Cc: egcs@cygnus.com
Subject: Re: Successful egcs-1.0.2 compile!
Date: Fri, 27 Mar 1998 15:18:00 -0000 [thread overview]
Message-ID: <XFMail.980327104910.npsimons@nmt.edu> (raw)
In-Reply-To: <m0yIH8D-00058JC@ocean.lucon.org>
-----BEGIN PGP SIGNED MESSAGE-----
On 26-Mar-98 H.J. Lu wrote:
>> I thought I would try compiling and installing egcs because a friend
>of
>> mine said it works better with glibc and it might fix this little problem:
>>
>> Mysteria:~/Projects/class_check$ gcc lud2.c -o lud2
>> /tmp/cca056251.o: In function `main':
>> /tmp/cca056251.o(.text+0x75): undefined reference to `stat'
>> /tmp/cca056251.o(.text+0x1bb): undefined reference to `stat'
>>
>> It's installed, but I guess I need to recompile glibc with egcs so that it
>will
>> fix that problem. BTW, I first ran into this problem with gcc 2.8.1 and
>glibc
>
>You screwed up your /usr/lib/libc.so, which, BTW, is not a symlink
>for glibc 2. It should be a text file for the linker as linker
>script.
>
>
>H.J.
Yeah, I went through and found that out. Thanks!
- -----------------------------------------------------------------
Nathan Paul Simons | Life on the cutting edge
npsimons@nmt.edu | Linux 2.1.90
http://www.nmt.edu/~npsimons | glibc 2.0.6
http://Mysteria.rcn.nmt.edu:8080 | egcs 1.0.2
- ------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNRvmlq2TiEsw6BOVAQFjqgP/WZcVBX3hHLr82V3ONm2STL9/5Dzyo0gs
lMKWX1DlREY1Z9EhfReXDc41PuB+2wkC+7w5/X4WmU3PYkmqLhsI1DgT5fzUqvT/
RwMR4S+W1I1dx+eTxyua8lwaWsXFiSfE5xHA1LGbjSeXmwymKzba1XoLi/3d6eOV
NGdDmoynsjI=
=inEG
-----END PGP SIGNATURE-----
prev parent reply other threads:[~1998-03-27 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 21:05 npsimons
1998-03-27 15:18 ` H.J. Lu
1998-03-27 15:18 ` npsimons [this message]
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=XFMail.980327104910.npsimons@nmt.edu \
--to=npsimons@nmt.edu \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).