From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-11
Date: Sun, 13 Jul 2014 00:21:20 +0200 [thread overview]
Message-ID: <20140712222120.GF3582@free.fr> (raw)
In-Reply-To: <20140712063006.DDD28100E08@stock.ovh.net>
Thomas, All,
On 2014-07-12 08:30 +0200, Thomas Petazzoni spake thusly:
> arm | perl-net-ssleay-1.64 | NOK | http://autobuild.buildroot.net/results/c7787542651e047631213e7be781008c60d48e0f/
Brain-damage.
The build system for perl-net-ssleay is completely f*ked-up for
cross-compilation. It tries to execute the openssl binary, and *runs* it
to verify a few things about openssl: availability, version...
Then it looks for openssl/ssl.h in host-system locations:
$prefix/include $prefix/inc32 /usr/kerberos/include
Of course $prefix is /usr, so it picks the host system openssl.
Ditto for the -L paths.
Totally brain-damaged.
And it is happy to just state:
*** Found OpenSSL-1.0.1f installed in /usr
Yeah, we're packaging openssl-1.0.1h in Buildroot. 1.0.1f is on my host
system's openssl...
Grrr...
/me reaches for his chainsaw...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-07-12 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-11 Thomas Petazzoni
2014-07-12 9:55 ` Yann E. MORIN
2014-07-12 10:07 ` Yann E. MORIN
2014-07-12 22:21 ` Yann E. MORIN [this message]
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=20140712222120.GF3582@free.fr \
--to=yann.morin.1998@free.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