From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] using BR2 variables to find a specific header file
Date: Tue, 14 Oct 2014 22:58:28 +0200 [thread overview]
Message-ID: <543D8E74.8080109@mind.be> (raw)
In-Reply-To: <20141013123003.49dcf374@core2quad.morethan.org>
On 13/10/14 19:30, Mike Zick wrote:
> On Mon, 13 Oct 2014 19:10:13 +0200
> Sylvain Raybaud <sylvain.raybaud@green-communications.fr> wrote:
>
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Dear all
>> >
>> > I'm trying to integrate a cmake based package wich is not very
>> > cross-compiling friendly (MariaDB galera cluster). During normal
>> > compile this package runs some tests in order to determine if stacks
>> > grows downward or upward. During cross-compile these tests cannot be
>> > run therefore the package expects -DSTACK_DIRECTION=+/-1 to be passed
>> > to cmake. Of course you cannot do it in buildroot.
>> >
> I think that the only processor where the stack grows up is PA-RISC.
> Which is not one of the Buildroot supported processors.
>
> So just hard code it (by patching if required) to down.
I did a quick check in the gcc 4.9.1 sources, and indeed it seems that the only
architectures that don't have it downward are PA-RISC, Xstormy16 and VMS. So
you're safe with hardcoding it.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-10-14 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 17:10 [Buildroot] using BR2 variables to find a specific header file Sylvain Raybaud
2014-10-13 17:30 ` Mike Zick
2014-10-14 20:58 ` Arnout Vandecappelle [this message]
2014-10-13 19:42 ` Samuel Martin
2014-10-14 10:58 ` Sylvain Raybaud
2014-10-14 12:18 ` Samuel Martin
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=543D8E74.8080109@mind.be \
--to=arnout@mind.be \
--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.