From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] libssp missing from target
Date: Tue, 31 Aug 2010 18:39:01 +0000 (UTC) [thread overview]
Message-ID: <i5ji85$mrr$2@dough.gmane.org> (raw)
In-Reply-To: 20100831200709.11d5a800@surf
On 2010-08-31, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> On Tue, 31 Aug 2010 14:52:34 +0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> I just added a package (systemtap) that uses libssp. I find libssp.so
>> et al. are present in output/staging/lib but missing from
>> output/target/lib. Is there something I need to do in my package
>> makefile to tell buildroot that my package needs libssp to be copied
>> from staging into target?
>
> What is libssp?
I don't really know. Here are the text symbols it defines:
__chk_fail
__stack_chk_fail
__stack_chk_fail_local
__gets_chk
__memcpy_chk
__memmove_chk
__mempcpy_chk
__memset_chk
__stpcpy_chk
__strcat_chk
__strcpy_chk
__strncat_chk
__strncpy_chk
My guess is it's some internal uClibc stuff.
> Who needs it (besides systemtap)
Nothing that I happen to be building (as far as I know).
> and for what?
I don't know. Does it matter?
> It seems to exist in uClibc toolchains, but not in glibc toolchains.
OK.
Why not run "ldd" on the binaries in output/target/bin and
output/target/usr/bin and just copy whatever libraries they need?
Does buildroot need to know exactly for what a library is used by each
binary?
--
Grant Edwards grant.b.edwards Yow! I want to kill
at everyone here with a cute
gmail.com colorful Hydrogen Bomb!!
next prev parent reply other threads:[~2010-08-31 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 14:52 [Buildroot] libssp missing from target Grant Edwards
2010-08-31 16:20 ` Grant Edwards
2010-08-31 18:05 ` Thomas Petazzoni
2010-08-31 18:29 ` Grant Edwards
2010-08-31 18:07 ` Thomas Petazzoni
2010-08-31 18:39 ` Grant Edwards [this message]
2010-09-01 8:56 ` Will Newton
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='i5ji85$mrr$2@dough.gmane.org' \
--to=grant.b.edwards@gmail.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 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.