Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nkukard at uclibc.org <nkukard@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/x86/grub
Date: Mon, 12 May 2008 11:56:12 -0700 (PDT)	[thread overview]
Message-ID: <20080512185612.873053C5D1@busybox.net> (raw)

Author: nkukard
Date: 2008-05-12 11:56:11 -0700 (Mon, 12 May 2008)
New Revision: 21974

Log:
features.h should never be included explicitly. 
This fixes the bug where "File not found" error is reported by grub.
This fix works under both uclibc and glibc.


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	2008-05-12 14:35:56 UTC (rev 21973)
+++ trunk/buildroot/target/x86/grub/grub.300-honor_UCLIBC_HAS_LFS.patch	2008-05-12 18:56:11 UTC (rev 21974)
@@ -5,7 +5,7 @@
   *  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
   */
  
-+#include <features.h>
++/* #include <features.h> - NK */
 +#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>
++/* #include <features.h> - NK */
 +#if !defined __UCLIBC__ || (defined __UCLIBC__ && defined __UCLIBC_HAS_LFS__)
  /* Try to use glibc's transparant LFS support. */
  #define _LARGEFILE_SOURCE       1

             reply	other threads:[~2008-05-12 18:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 18:56 nkukard at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-31 12:30 [Buildroot] svn commit: trunk/buildroot/target/x86/grub jacmet at uclibc.org
2009-01-31 12:29 jacmet at uclibc.org
2008-11-08 22:24 tpetazzoni 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=20080512185612.873053C5D1@busybox.net \
    --to=nkukard@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