From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/fakeroot
Date: Thu, 20 Sep 2007 10:47:32 -0700 (PDT) [thread overview]
Message-ID: <20070920174732.1E8D0A45EE@busybox.net> (raw)
Author: aldot
Date: 2007-09-20 10:47:30 -0700 (Thu, 20 Sep 2007)
New Revision: 19920
Log:
- of course we also define glibc. argh!
Modified:
trunk/buildroot/package/fakeroot/fakeroot-uclibc-LFS.diff
Changeset:
Modified: trunk/buildroot/package/fakeroot/fakeroot-uclibc-LFS.diff
===================================================================
--- trunk/buildroot/package/fakeroot/fakeroot-uclibc-LFS.diff 2007-09-20 17:41:21 UTC (rev 19919)
+++ trunk/buildroot/package/fakeroot/fakeroot-uclibc-LFS.diff 2007-09-20 17:47:30 UTC (rev 19920)
@@ -1,13 +1,14 @@
diff -u fakeroot-1.7.1.orig/communicate.h fakeroot-1.7.1/communicate.h
--- fakeroot-1.7.1.orig/communicate.h 2005-10-02 17:35:36.000000000 +0200
-+++ fakeroot-1.7.1/communicate.h 2007-09-20 19:36:52.000000000 +0200
-@@ -35,7 +35,8 @@
++++ fakeroot-1.7.1/communicate.h 2007-09-20 19:43:38.000000000 +0200
+@@ -35,7 +35,9 @@
#endif
/* Then decide whether we do or do not use the stat64 support */
-#if defined(sun) || __GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1)
-+#if defined(sun) || __GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1) \
-+ || (defined __UCLIBC__ && defined UCLIBC_HAS_LFS)
++#if defined(sun) \
++ || (!defined __UCLIBC__ && (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1))) \
++ || (defined __UCLIBC__ && defined UCLIBC_HAS_LFS)
# define STAT64_SUPPORT
#else
# warning Not using stat64 support
next reply other threads:[~2007-09-20 17:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 17:47 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 9:08 [Buildroot] svn commit: trunk/buildroot/package/fakeroot jacmet at uclibc.org
2008-09-07 14:31 jacmet at uclibc.org
2008-03-13 7:38 jacmet at uclibc.org
2008-03-12 13:58 ninevoltz at uclibc.org
2008-03-11 19:31 jacmet at uclibc.org
2008-03-11 13:32 ninevoltz at uclibc.org
2008-03-11 13:45 ` Sunil Gupta
2008-03-11 13:11 ninevoltz at uclibc.org
2008-03-11 13:17 ` Nigel Kukard
2008-03-11 13:30 ` Sunil Gupta
2008-01-21 11:07 thomasez at uclibc.org
2007-12-27 11:23 thomasez at uclibc.org
2007-10-18 21:49 vanokuten at uclibc.org
2007-10-13 23:13 ulf at uclibc.org
2007-10-02 11:06 aldot at uclibc.org
2007-09-21 14:22 aldot at uclibc.org
2007-09-20 17:41 aldot at uclibc.org
2007-08-13 8:12 ulf at uclibc.org
2007-06-06 18:10 aldot at uclibc.org
2007-04-03 15:36 jacmet at uclibc.org
2007-04-03 18:09 ` Benedict, Michael
2007-03-05 11:06 jacmet at uclibc.org
2007-01-22 20:26 aldot at uclibc.org
2007-01-22 18:16 andersen at uclibc.org
2006-12-15 14:18 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=20070920174732.1E8D0A45EE@busybox.net \
--to=aldot@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