From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
Date: Thu, 24 Jan 2008 09:28:18 +0100 [thread overview]
Message-ID: <20080124082818.GA1078@zelow.no> (raw)
In-Reply-To: <00c401c85e2a$9de7f140$8119fea9@MingChing>
On Thu, Jan 24, 2008 at 09:44:10AM +0800, Ming-Ching Tiew wrote:
>
> I have found a workaround for it, I delete the entire
>
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/
>
> Looks to me like a bug. Since I can proceed now, I am staying with
> this for a while.
weird but not sure why.
> BTW, the sstrip thingie looks to me also a bug. It happens to not
> just SSL shared library. The uClibc libraries could also be
> sstripped. This will be quite disasterous.
Not unless you want to build within the buildroot. I do sstrip on all
libraries on the resulting rootfs (floppyfw and others) but you are
probably right about sstripping when you have
CONFIG_BR2_PACKAGE_GCC_TARGET set.
When building the floppyfw devkit I also set CONFIG_BR2_STRIP_none.
I would consider it a but if any of the packages .mk files
does strip anything even when CONFIG_BR2_STRIP_none is set.
Bbut stripping the libraries when the target is a normal rootfs seems
correct to me.
Thomas.
next prev parent reply other threads:[~2008-01-24 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 3:15 [Buildroot] can't develope any programs using ssl in the root Ming-Ching Tiew
2008-01-24 1:44 ` [Buildroot] [Merak Spam 5.26] " Ming-Ching Tiew
2008-01-24 8:28 ` Thomas Lundquist [this message]
2008-01-24 9:30 ` [Buildroot] sstrip and segmentation violation ( was: can't develope any programs using ssl in the root ) Ming-Ching Tiew
2008-01-24 22:38 ` [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root Hamish Moffatt
2008-01-25 1:02 ` [Buildroot] " Ming-Ching Tiew
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=20080124082818.GA1078@zelow.no \
--to=lists@zelow.no \
--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