From: Sylvain Raybaud <sylvain.raybaud@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] scons and check
Date: Wed, 27 May 2015 17:03:00 +0200 [thread overview]
Message-ID: <5565DCA4.5040002@green-communications.fr> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I'm trying to create a package for Galera, a library needed by mariadb
galera cluster. It builds with scons. Galera depends on check so I
created a package for this library too, which seems to build and
install correctly.
A few packages in buildroot already use scons (exfat, exfat-utils,
benejson, gpsd). Their build commands look like this:
FOO_SCONS_ENV = $(TARGET_CONFIGURE_OPTS)
FOO_SCONS_OPTS = "prefix=/usr"
define FOO_BUILD_CMDS
cd $(@D) && \
$(FOO_SCONS_ENV) \
CROSS=$(TARGET_CROSS) \
$(SCONS) $(FOO_SCONS_OPTS)
endef
So I wrote my .mk file the same way. However scons does not seem to
find the Check library. Building galera fails with:
Checking for C header file check.h... no
Error: check header file not found or not usable
and corresponding config.log shows a "check.h: file not found" error.
Now the disturbing thing is that it only happens when I build on a
system on which check is not installed system-wise. If the build host
has check installed, galera builds. Does this mean that scons uses
host haeders instead of those provided by buildroot packages? Any idea
how to make it behave properly?
Cheers,
- --
Sylvain Raybaud
www.green-communications.fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJVZdykAAoJEEkkwl4JtJ9yhFQP/1Tz1R+MTfKofn6mR5cRHhsQ
v9vZubtiWsbJ5iIBHWOiY6axhRxeizlmXy1MdCtJ6V6vWpo4IQsAOi1T5iDYsNvc
F6q1JUJWLxF3cpeqDULbjdySyJL2193SNvakf5yVCpJH2/ZF0r1UYXZz6aNPkfZv
ADz0dPc2XaZRFuinW24NbZyz6//HLTl9C0U006PzZO3ztCTA3jv09gGW4WSyX5Mn
yEN+WsQ3pjRIJwhrHKjA9/4Dtk7HIG1p6ln2swiiMYxZarIQik70aRIFHchwDS9J
sLrLVSLQHvY8OR0pnmdIoY1RBBAC2sUlbSh57Fb+bJEI0vommRgkZjPP6my4WW7F
SMtaAwzuXNDN/XYb5JoCfJVjyByV/0OLPxWGHFZ77W32xQ59n5jDi10RHL85wnvP
kmgJ7LSvvwgfMioBo8QC/t0zI9kvU0emq136khuROMKRbFAKnAZqRr97OCJ3s5Uz
qjAW2iY5MufgNWdyQG+M5plnt+3hqgFAKJwQwgyuyeVPgHI0N1ZZ6wQYff3LV4xm
QWULAwVyiyNgqRb45OfP7JWqCFhoP8gQiWCYMVlRmTEfY/lLMxd20AK8qz1v4uTA
p4t9n6ql6dXloeWcw2dlxQVS6ZHqK/6xxfh6d2RsnekN5OVjRvEE3KaKt/5ae3pa
F+NzawlBLBStsW73P6LZ
=twcI
-----END PGP SIGNATURE-----
next reply other threads:[~2015-05-27 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:03 Sylvain Raybaud [this message]
2015-05-27 15:41 ` [Buildroot] scons and check Samuel Martin
2015-05-27 16:46 ` Sylvain Raybaud
2015-05-27 18:08 ` Thomas Petazzoni
2015-05-28 7:47 ` Peter Bouda
2015-05-28 10:55 ` Sylvain Raybaud
2015-05-28 12:07 ` Sylvain Raybaud
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=5565DCA4.5040002@green-communications.fr \
--to=sylvain.raybaud@green-communications.fr \
--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