From: David Brown <david@westcontrol.com>
To: buildroot@busybox.net
Subject: [Buildroot] avr32 - directfb compile failure in release buildroot 2.3.0
Date: Mon, 05 Jan 2009 17:27:55 +0100 [thread overview]
Message-ID: <gjtcei$egs$1@ger.gmane.org> (raw)
I'm not sure if this is something that should be considered a buildroot
issue, a DirectFB issue, or an AVR32-specific issue. Hopefully someone
will point me in the right direction if this is not a suitable mailing
list for this issue.
My build environment is buildroot 2.3.0 from Atmel, configured for the
AVR32 (with "make atstk1002_defconfig" and a few small changes).
Builds of DirectFB (version 1.2.6) are failing with an error message
that "PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP" is not defined (in
lib/direct/interface.c, amongst other files). I've traced this to a
difference in the ./configure script and the actual compilation - the
./configure script defines the "_GNU_SOURCE" symbol before checking for
the "PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP" macro, and thus finds it
defined. The actual library code does not define the "_GNU_SOURCE"
symbol (according to the changelog, this definition was in older
DirectFB versions, but has since been removed), and thus (via
<features.h> and <pthread.h>) "PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP"
is not defined during compilation.
I've got DirectFB to compile by adding a "#define _GNU_SOURCE 1" to the
start of "config.h", and now the DirectFB demo programs are compiled and
seem to be working.
mvh.,
David Brown
Norway.
reply other threads:[~2009-01-05 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gjtcei$egs$1@ger.gmane.org' \
--to=david@westcontrol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.