public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/3335] In function `__getcwd': undefined reference to `MAX' Date: Tue, 31 Oct 2006 20:06:00 -0000 [thread overview] Message-ID: <20061031200619.30697.qmail@sourceware.org> (raw) In-Reply-To: <20061011094058.3335.mkl@pengutronix.de> ------- Additional Comments From vapier at gentoo dot org 2006-10-31 20:06 ------- ive seen this failure in a couple of ports ... i dont really care to try and track down the implicit include path in every one as simply including the header that defines MAX() in the file that uses MAX() seems a lot saner to me -- http://sourceware.org/bugzilla/show_bug.cgi?id=3335 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-10-31 20:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-11 9:41 [Bug ports/3335] New: " mkl at pengutronix dot de 2006-10-13 19:24 ` [Bug ports/3335] " vapier at gentoo dot org 2006-10-31 16:05 ` drow at sources dot redhat dot com 2006-10-31 20:06 ` vapier at gentoo dot org [this message] 2006-10-31 20:07 ` drow at sources dot redhat dot com 2006-10-31 20:12 ` vapier at gentoo dot org [not found] <bug-3335-131@http.sourceware.org/bugzilla/> 2012-02-15 18:10 ` jsm28 at gcc dot gnu.org 2012-02-15 18:37 ` vapier at gentoo dot org 2012-02-15 20:45 ` joseph at codesourcery dot com 2012-02-16 3:11 ` vapier at gentoo dot org 2012-02-16 4:19 ` joseph at codesourcery dot com
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=20061031200619.30697.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: 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).