From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: buildroot@busybox.net
Subject: [Buildroot] sstrip and segmentation violation ( was: can't develope any programs using ssl in the root )
Date: Thu, 24 Jan 2008 17:30:37 +0800 [thread overview]
Message-ID: <047901c85e6b$c7237340$8119fea9@MingChing> (raw)
In-Reply-To: 20080124082818.GA1078@zelow.no
From: "Thomas Lundquist" <lists@zelow.no>
>
> > 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.
>
Oh I see. This buildroot thingie is rather new to me, so I am gaining
experience on it.
So it not quite a bug then, it is an not-so-obvious feature which
one can tumble on it. :-)
Last but not least, I seem to only get all the wrong things with me now.
I managed to compile the rootfs.i686.ext2, using a few different
combinations of gcc ( 3.4.6, 4.1.0, 4.2.0 ), uclibc version ( 0.9.28.3
and 0.9.29 ). But consistantly I get random segmentation violation
error when I compile stuff inside the rootfs. Looks like stack
corruption or something. Now perhaps I need to change my host
OS compiler instead ( I am using 4.1.2 20061028 ).
Anyone knows if the host compiler version will have an impact
on the quality of the rootfs ?
Regards.
next prev parent reply other threads:[~2008-01-24 9:30 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
2008-01-24 9:30 ` Ming-Ching Tiew [this message]
2008-01-24 22:38 ` 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='047901c85e6b$c7237340$8119fea9@MingChing' \
--to=mingching.tiew@redtone.com \
--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