From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] OpenSSL build system knowledge somewhere ?
Date: Wed, 15 Apr 2009 15:50:01 +0200 [thread overview]
Message-ID: <87vdp681rq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090415154103.53f867d1@surf> (Thomas Petazzoni's message of "Wed\, 15 Apr 2009 15\:41\:03 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> From a quick look it seems to just be a matter of adding
>> CFLAG='$(TARGET_CFLAGS) <extra flags>' on the make command line, where
>> <extra flags> are the flags openssl uses internally (something like
>> -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLCFN -DHAVE_DLFCN_H -DTERMIO).
Thomas> How do I know, in a proper way, what these <extra flags> are ? (I mean,
Thomas> without hardcoding them in Buildroot's .mk file)
You don't. Either you do like we used to do and fix the makefile with
sed (s/^CFLAG = /CFLAG = -sysroot .../) and live with the fact that
openssl likes to compile with -O3 no mather what optimization level
you have selected in BR, or you hardcode the list in openssl.mk (it
probably doesn't change that often).
>> The question is why is all of a sudden failed?
Thomas> I have no idea, I've never myself compiled openssl with
Thomas> external toolchain.
Ahh ok.
Thomas> What's your suggestion to work around the issue ?
One of the options above (hardcoded list or sed invocation).
Thomas> Moreover, the --sysroot option is just part of
Thomas> $(TARGET_CFLAGS), which might as well contain other flags
Thomas> (march, mtune, mcpu, Os, O2 or whatever), so the .mk should
Thomas> be written so that the build process of all packages really
Thomas> take into account $(TARGET_CFLAGS). And if they do, then
Thomas> there's no point in adding a wrapper script specially for the
Thomas> --sysroot case.
Ok.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-04-15 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 3:46 [Buildroot] buildroot openssl compile error Brad Johnson
2009-04-13 18:03 ` Peter Korsgaard
2009-04-13 20:08 ` Thomas Petazzoni
2009-04-14 3:10 ` Brad Johnson
2009-04-14 7:09 ` Thomas Petazzoni
2009-04-14 8:41 ` Thomas Petazzoni
2009-04-15 9:06 ` [Buildroot] OpenSSL build system knowledge somewhere ? Thomas Petazzoni
2009-04-15 12:57 ` Peter Korsgaard
2009-04-15 13:41 ` Thomas Petazzoni
2009-04-15 13:50 ` Peter Korsgaard [this message]
2009-04-15 19:28 ` Gustavo Zacarias
2009-04-15 13:59 ` Gustavo Zacarias
2009-04-14 2:00 ` [Buildroot] buildroot openssl compile error Brad Johnson
2009-04-28 21:06 ` Thomas Petazzoni
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=87vdp681rq.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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