From: Steven Lucy <slucy@uchicago.edu>
To: Nicholas Hockey <tilt@bluecherry.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] glibc
Date: Wed, 29 Jan 2003 22:20:41 -0600 [thread overview]
Message-ID: <20030129222041.A22052@harper.uchicago.edu> (raw)
In-Reply-To: <1043898001.9268.1.camel@blackhole>; from tilt@bluecherry.net on Wed, Jan 29, 2003 at 10:40:01PM -0500
On Wed, Jan 29, 2003 at 10:40:01PM -0500, Nicholas Hockey <tilt@bluecherry.net> said
> unset LD_LIBRARY_PATH and try re-emerging glibc
of course that's what i did, i was just suggesting that the ebuild could do
this for you...
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-30 4:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 0:38 [gentoo-dev] glibc Steven Lucy
2003-01-30 3:40 ` Nicholas Hockey
2003-01-30 4:20 ` Steven Lucy [this message]
2003-02-03 21:41 ` Martin Schlemmer
2003-02-03 22:11 ` Matt Tucker
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 19:19 Christian Loitsch
2001-06-05 7:22 [gentoo-dev] GlibC Mathijs Kwik (-=TRoXX=-)
2001-06-05 20:52 ` Collins Richey
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=20030129222041.A22052@harper.uchicago.edu \
--to=slucy@uchicago.edu \
--cc=gentoo-dev@gentoo.org \
--cc=tilt@bluecherry.net \
/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