From: Luca Berra <bluca@comedia.it>
To: Nix <nix@esperi.org.uk>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: [PATCH*2] mdadm works with uClibc from SVN
Date: Sat, 24 Jun 2006 10:26:30 +0200 [thread overview]
Message-ID: <20060624082629.GA12050@percy.comedia.it> (raw)
In-Reply-To: <87veqrk650.fsf@hades.wkstn.nix>
On Fri, Jun 23, 2006 at 08:45:47PM +0100, Nix wrote:
>On Fri, 23 Jun 2006, Neil Brown mused:
>> Is there some #define in an include file which will allow me to tell
>> if the current uclibc supports ftw or not?
it is not only depending on the uClibc version, but also if ftw support
was compiled in or not.
>I misspoke: ftw was split into multiple files in late 2005, but it was
>originally added in September 2003, in time for version 0.9.21.
>
>Obviously the #defines in <ftw.h> don't exist before that date, but
>that's a bit late to check, really.
>
><features.h> provides the macros __UCLIBC_MAJOR__, __UCLIBC_MINOR__, and
>__UCLIBC_SUBLEVEL__: versions above 0.9.20 appear to support ftw()
>(at least, they have the function, in 32-bit form at least, which
>is certainly enough for this application!)
the following would be the correct check.
#include <features.h>
#ifdef __UCLIBC_HAS_FTW__
.....
#else
.....
#endif /* __UCLIBC_HAS_FTW__ */
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-06-24 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 22:06 [PATCH*2] mdadm works with uClibc from SVN Nix
2006-06-20 23:03 ` Nix
2006-06-23 7:33 ` Nix
2006-06-23 8:12 ` Neil Brown
2006-06-23 19:45 ` Nix
2006-06-24 8:26 ` Luca Berra [this message]
2006-06-24 13:08 ` Nix
2006-06-26 4:32 ` Neil Brown
2006-06-27 9:40 ` Nix
2006-06-27 9:55 ` Neil Brown
2006-06-27 10:58 ` Nix
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=20060624082629.GA12050@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nix@esperi.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).