From: Ulrich Drepper <drepper@redhat.com>
To: Mike Black <mblack@csi-inc.com>
Cc: libc-alpha@sources.redhat.com, linux-gcc@vger.kernel.org
Subject: Re: glibc 2.3
Date: Thu, 03 Oct 2002 09:22:37 -0700 [thread overview]
Message-ID: <3D9C6ECD.3050307@redhat.com> (raw)
In-Reply-To: 018901c26af7$7b78dce0$f6de11cc@black
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mike Black wrote:
> It appears configure is using prefix /usr/local and spits out a bogus message.
THere is no bogus messages. Installing in /usr/local does not overwrite
the system's libc and is safe from this perspective. But gcc handles
/usr/local special which might lead to normal compilations picking the
headers up which might or might not lead to problems. And /usr/local is
the default prefix because this is what it always is.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9nG7N2ijCOnn/RHQRAnSbAJ4/nvyFSjpqDjqjwWZvfCnXPt115wCbB473
FZtM68iPti/03fqC28vf5kk=
=UsED
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-03 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:09 glibc 2.3 Ulrich Drepper
2002-10-03 16:11 ` Mike Black
2002-10-03 16:22 ` Ulrich Drepper [this message]
2002-10-03 16:26 ` Mike Black
2002-10-03 16:33 ` Ulrich Drepper
2002-10-05 19:35 ` Graham Murray
2002-10-05 19:39 ` Jakub Jelinek
2002-10-15 15:57 ` Keld Jørn Simonsen
2002-10-15 17:41 ` Ulrich Drepper
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=3D9C6ECD.3050307@redhat.com \
--to=drepper@redhat.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-gcc@vger.kernel.org \
--cc=mblack@csi-inc.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;
as well as URLs for NNTP newsgroup(s).