public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: Bauke Jan Douma <bjdouma@xs4all.nl> To: glibc-bugs@sourceware.org Subject: glibc-2.5: 'make check' reports quite a few errors Date: Sun, 12 Nov 2006 17:40:00 -0000 [thread overview] Message-ID: <45575C9E.2010905@xs4all.nl> (raw) Sorry, there was an editing/pasting error in my previous post. Don't know how that happened, but anyway: --with-tls \foo bar should be: --with-tls \ and in fact that's how glibc is compiled. bjd
next reply other threads:[~2006-11-12 17:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-12 17:40 Bauke Jan Douma [this message] -- strict thread matches above, loose matches on Subject: below -- 2006-11-12 17:36 Bauke Jan Douma
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=45575C9E.2010905@xs4all.nl \ --to=bjdouma@xs4all.nl \ --cc=glibc-bugs@sourceware.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: linkBe 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).