From: Ralf Baechle <ralf@oss.sgi.com>
To: Keith M Wesolowski <wesolows@foobazco.org>
Cc: Steven Liu <stevenliu@psdc.com>, linux-mips@oss.sgi.com
Subject: Re: glibc 2.0.6 building problem.
Date: Fri, 17 Aug 2001 12:02:21 +0200 [thread overview]
Message-ID: <20010817120220.A4792@bacchus.dhis.org> (raw)
In-Reply-To: <20010816212727.A27405@foobazco.org>; from wesolows@foobazco.org on Thu, Aug 16, 2001 at 09:27:27PM -0700
On Thu, Aug 16, 2001 at 09:27:27PM -0700, Keith M Wesolowski wrote:
> > It seems that I need to copy the kernel's include files and lib to
> > somewhere. I could not figure it out.
>
> Thankfully, you won't have to. I've already fully documented the
> entire process at http://foobazco.org/~wesolows/mips-cross.html.
>
> Repeat after me, "This mailing list is no substitute for Google."
As for me I'll forward glibc 2.0 questions to my watercooled /dev/zero.
Ralf
next prev parent reply other threads:[~2001-08-17 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 17:33 glibc 2.0.6 building problem Steven Liu
2001-08-16 17:33 ` Steven Liu
2001-08-17 4:27 ` Keith M Wesolowski
2001-08-17 10:02 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-25 0:31 Steven Liu
2001-08-25 0:31 ` Steven Liu
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=20010817120220.A4792@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=stevenliu@psdc.com \
--cc=wesolows@foobazco.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