public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/3335] In function `__getcwd': undefined reference to `MAX' Date: Wed, 15 Feb 2012 18:10:00 -0000 [thread overview] Message-ID: <bug-3335-131-bt4n2gHBX9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-3335-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=3335 Joseph Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-15 18:09:37 UTC --- ARM old-ABI support is removed and new-ABI builds OK, so I think we can take the build problem as fixed. However, I think source files should also include headers whose API actually includes providing whatever definitions the source file needs. That is, I think adding the missing #include to libc is an obvious fix. I'm pinging it on libc-alpha. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2012-02-15 18:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-3335-131@http.sourceware.org/bugzilla/> 2012-02-15 18:10 ` jsm28 at gcc dot gnu.org [this message] 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 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 2006-10-31 20:07 ` drow at sources dot redhat dot com 2006-10-31 20:12 ` vapier at gentoo dot org
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=bug-3335-131-bt4n2gHBX9@http.sourceware.org/bugzilla/ \ --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).