From: Andreas Jaeger <aj@suse.de>
To: Sergey Ostrovsky <sostrovs@kns.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Glibc - mailing list ?
Date: Thu, 19 Apr 2001 13:11:00 -0000 [thread overview]
Message-ID: <u8itk03beb.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <3ADF1946.114F058C@eng.kns.com>
Sergey Ostrovsky <sostrovs@kns.com> writes:
> Hello,
> I have glibc-related questions.
> Yes, this is the gcc mailing list, but couldn't find the glibc list.
> The one at tux.org is full with spam ( and _only_ spam ) for months.
> Sorry about that ...
> I wonder what the configuration parameters
> --with-gmp
That's maintainer only, don't use it.
> --with-gd
> --with-gd-include
> --with-gd-lib
> for glibc-2.2.2 mean ?
Did you run configure --help?
> Any help ( including links to proper glibc mailing list )
Check http://www.gnu.org/software/libc and
http://sources.redhat.com/libc
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-04-19 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 9:58 Sergey Ostrovsky
2001-04-19 12:51 ` OT: " Gordon Sadler
2001-04-19 13:11 ` Andreas Jaeger [this message]
2001-04-19 13:40 ` Sergey Ostrovsky
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=u8itk03beb.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=sostrovs@kns.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 read-only IMAP folder(s) and NNTP newsgroup(s).