From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/x86/grub
Date: Sat, 31 Jan 2009 12:30:02 +0000 (UTC) [thread overview]
Message-ID: <20090131123003.248B376219@busybox.osuosl.org> (raw)
Author: jacmet
Date: 2009-01-31 12:30:02 +0000 (Sat, 31 Jan 2009)
New Revision: 25178
Log:
grub: revert r21974 (features.h should never be included explicitly)
features.h (or something including it) is needed for __UCLIBC* to get
defined - E.G. without that the build breaks without largefile support.
Nigel, what was the reason for your commit and what file not found error
did you see?
Modified:
trunk/buildroot/target/x86/grub/grub.300-honor_UCLIBC_HAS_LFS.patch
Changeset:
Modified: trunk/buildroot/target/x86/grub/grub.300-honor_UCLIBC_HAS_LFS.patch
===================================================================
--- trunk/buildroot/target/x86/grub/grub.300-honor_UCLIBC_HAS_LFS.patch 2009-01-31 12:29:55 UTC (rev 25177)
+++ trunk/buildroot/target/x86/grub/grub.300-honor_UCLIBC_HAS_LFS.patch 2009-01-31 12:30:02 UTC (rev 25178)
@@ -5,7 +5,7 @@
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
-+/* #include <features.h> - NK */
++#include <features.h>
+#if !defined __UCLIBC__ || (defined __UCLIBC__ && defined __UCLIBC_HAS_LFS__)
/* Try to use glibc's transparant LFS support. */
#define _LARGEFILE_SOURCE 1
@@ -22,7 +22,7 @@
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
-+/* #include <features.h> - NK */
++#include <features.h>
+#if !defined __UCLIBC__ || (defined __UCLIBC__ && defined __UCLIBC_HAS_LFS__)
/* Try to use glibc's transparant LFS support. */
#define _LARGEFILE_SOURCE 1
next reply other threads:[~2009-01-31 12:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 12:30 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-31 12:29 [Buildroot] svn commit: trunk/buildroot/target/x86/grub jacmet at uclibc.org
2008-11-08 22:24 tpetazzoni at uclibc.org
2008-05-12 18:56 nkukard at uclibc.org
2008-05-01 17:14 ninevoltz at uclibc.org
2008-02-22 19:37 sjhill at uclibc.org
2008-02-28 15:25 ` Fathi Boudra
2007-09-30 18:06 aldot at uclibc.org
2007-05-15 11:39 aldot at uclibc.org
2007-02-07 10:43 aldot at uclibc.org
2007-01-29 22:12 aldot at uclibc.org
2007-01-29 18:34 aldot at uclibc.org
2006-12-20 17:08 aldot at uclibc.org
2006-11-29 20:26 aldot at uclibc.org
2006-11-29 12:17 aldot at uclibc.org
2006-11-22 15:22 aldot at uclibc.org
2006-11-17 11:47 aldot at uclibc.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=20090131123003.248B376219@busybox.osuosl.org \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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