From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libssp still missing from target
Date: Fri, 5 Aug 2011 00:34:19 +0200 [thread overview]
Message-ID: <20110805003419.4934e4bf@skate> (raw)
In-Reply-To: <j1eiv7$irk$1@dough.gmane.org>
Hello,
Le Thu, 4 Aug 2011 16:56:07 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> This has come up before, and IIRC, I ended up tweaking ext-tool.mk to
> work around it.
>
> I've just upgraded to Buildroot 2011.05, and it seems ext-tool.mk
> still isn't copying libssp to the target. It's need by (among other
> things) ssh:
>
> Starting network...
> ip: RTNETLINK answers: File exists
> Generating ECDSA Key...
> THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!
>
> /usr/bin/ssh-keygen: can't load library 'libssp.so.0'
> Starting sshd: /usr/sbin/sshd: can't load library 'libssp.so.0'
>
> Is there some configuration option I've missed?
I guess libssp only exists on toolchains that have stack protection
support enabled. None of my CodeSourcery or Buildroot-built toolchains
have a libssp. I guess I'll have to build a CT-NG toolchain with libssp
support.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-08-04 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 16:56 [Buildroot] libssp still missing from target Grant Edwards
2011-08-04 22:34 ` Thomas Petazzoni [this message]
2011-08-05 7:46 ` Peter Korsgaard
2011-08-06 9:38 ` Mike Frysinger
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=20110805003419.4934e4bf@skate \
--to=thomas.petazzoni@free-electrons.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