From: Florian Lohoff <flo@rfc822.org>
To: Jun Matsuda <jmatsu@cse.canon.co.jp>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: patch for glibc-2.0.6
Date: Tue, 21 Dec 1999 16:54:44 +0100 [thread overview]
Message-ID: <19991221165444.W272@paradigm.rfc822.org> (raw)
In-Reply-To: <19991221210256U.jmatsu@cse.canon.co.jp>; from Jun Matsuda on Tue, Dec 21, 1999 at 09:02:56PM +0900
On Tue, Dec 21, 1999 at 09:02:56PM +0900, Jun Matsuda wrote:
> Hi,
>
> I plan to construct the cross compilation environment as
> described in the Linux/MIPS-HOWTO. But I could not find the
> patch for glibc-2.0.6 (glibc-2.0.6-mips.patch) and without
> this patch, I failed to compile glibc-2.0.6.
>
> Does anyone tell me the place where to find it?
There is a source rpm for it somewhere - Or a debian source package
for 2.0.7.981112 or something at
ftp://ftp.rfc822.org/pub/local/debian/debian/experimental
or something like that - It doesnt compile out of the box because
the tic and rpcgen get linked to the wrong lib ...
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice
prev parent reply other threads:[~1999-12-21 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 23:44 Snapshot Ralf Baechle
1999-12-07 5:07 ` Snapshot A. Wrasman
[not found] ` <Pine.OSF.3.96.991206221350.25177A-100000@osf1.gmu.edu>
1999-12-07 11:11 ` Snapshot Ralf Baechle
1999-12-09 15:49 ` Snapshot Florian Lohoff
1999-12-09 19:02 ` Snapshot Ralf Baechle
1999-12-09 21:00 ` Snapshot Harald Koerfgen
1999-12-21 12:02 ` patch for glibc-2.0.6 Jun Matsuda
1999-12-21 14:19 ` Ralf Baechle
1999-12-21 23:59 ` Jun Matsuda
1999-12-21 15:54 ` Florian Lohoff [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=19991221165444.W272@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=jmatsu@cse.canon.co.jp \
--cc=linux@cthulhu.engr.sgi.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