From: Dong Liu <dliu@npiww.com>
To: ralf@uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: glibc problem
Date: Mon, 27 Apr 1998 19:37:42 -0400 [thread overview]
Message-ID: <199804272337.TAA14149@pluto.npiww.com> (raw)
In-Reply-To: <199804241600.MAA05998@pluto.npiww.com>
Dong Liu writes:
> ralf@uni-koblenz.de writes:
> >
> > Thanks for your report. An untested patch to be applied to
> > libc/sysdeps/unix/sysv/linux/mips/syscalls.list is attached below.
> >
> > > my glibc is glibc-2.0.6-1, so I went ftp.redhat.com downloaded
> > > glibc-2.0.7, but I can't build it. Where can I found sgi-linux
> > > specific patches for glibc.
> >
> > You can find the patches In the rpm packages on ftp.linux.sgi.com.
> >
> > I don't know if the MIPS patches for glibc 2.0.6 are working for 2.0.7.
> > Unless I missed the announcement 2.0.7 hasn't been released yet and I
> > don't try to follow the beta releases, no time ...
> >
> > Ralf
>
> Nope, after 4 hours building new glibc, it gives me same error for
> undefined reference to __libc_accept ... :=*(.
>
Sorry, I didn't install it properly, now my program links, but it
still give segementation fault.
Dong.
BTW, can some one make a tarball of strace and gdb, I don't think I
can check them out from CVS.
next prev parent reply other threads:[~1998-04-27 23:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-22 21:19 glibc problem Dong Liu
1998-04-22 21:13 ` Alex deVries
1998-04-22 21:43 ` ralf
1998-04-23 2:23 ` Alex deVries
1998-04-23 3:17 ` ralf
1998-04-23 3:28 ` Alex deVries
1998-04-22 21:48 ` Dong Liu
1998-04-23 3:04 ` ralf
1998-04-24 16:00 ` Dong Liu
1998-04-27 23:37 ` Dong Liu [this message]
1998-04-27 23:33 ` ralf
1998-04-28 19:11 ` Dong Liu
-- strict thread matches above, loose matches on Subject: below --
1998-04-22 23:24 Dong Liu
2000-10-25 15:06 Glibc Problem Ian Chilton
2000-10-25 15:45 ` Keith M Wesolowski
2000-10-25 15:54 ` Andreas Jaeger
2001-07-26 9:09 glibc problem Andre.Messerschmidt
2001-07-26 13:46 ` Ralf Baechle
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=199804272337.TAA14149@pluto.npiww.com \
--to=dliu@npiww.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.