From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-27
Date: Wed, 28 May 2014 08:46:02 +0200 [thread overview]
Message-ID: <20140528084602.4cc48b8d@free-electrons.com> (raw)
In-Reply-To: <20140528064358.GB3510@free.fr>
Dear Yann E. MORIN,
On Wed, 28 May 2014 08:43:58 +0200, Yann E. MORIN wrote:
> > bfin | monit-5.7 | NOK | http://autobuild.buildroot.net/results/67623f87f8bc2c73f30bdc3943c58238686c106e/
>
> src/process/sysdep_LINUX.c: In function 'initprocesstree_sysdep':
> src/process/sysdep_LINUX.c:207: error: 'GLOB_ONLYDIR' undeclared (first
> use in this function)
>
> Not sure, but GLOB_ONLYDIR should come from the C library. I will
> investigate.
GLOB_ONLYDIR is a GNU extension, and Blackfin toolchains have a uClibc
configuration without the appropriate option. However, GLOB_ONLYDIR is
only a hint:
GLOB_ONLYDIR
This is a hint to glob() that the caller is interested only in
directories that match the pattern. If the implementation can
easily determine file-type information, then nondirectory files
are not returned to the caller. However, the caller must still
check that returned files are directories. (The purpose of this
flag is merely to optimize performance when the caller is inter?
ested only in directories.)
So a potential fix would be:
#ifndef GLOB_ONLYDIR
#define GLOB_ONLYDIR 0
#endif
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-28 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-27 Thomas Petazzoni
2014-05-28 6:43 ` Yann E. MORIN
2014-05-28 6:46 ` Thomas Petazzoni [this message]
2014-05-28 6:52 ` Peter Korsgaard
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=20140528084602.4cc48b8d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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