From: Albert Siersema <albert@friendly.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with propolice/SSP
Date: Tue, 10 Jul 2007 17:33:40 +0200 [thread overview]
Message-ID: <4693A6D4.9080707@friendly.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Hello,
I tried compiling buildroot (buildroot-20070709.tar.bz2 to be precise) with propolice support.
For starters: is this known to work ?
My uclibc .config contains:
#
# Security options
#
UCLIBC_BUILD_PIE=y
UCLIBC_HAS_ARC4RANDOM=y
# HAVE_NO_SSP is not set
UCLIBC_HAS_SSP=y
# UCLIBC_HAS_SSP_COMPAT is not set
# SSP_QUICK_CANARY is not set
PROPOLICE_BLOCK_ABRT=y
# PROPOLICE_BLOCK_SEGV is not set
UCLIBC_BUILD_SSP=y
UCLIBC_BUILD_RELRO=y
UCLIBC_BUILD_NOW=y
UCLIBC_BUILD_NOEXECSTACK=y
(i'm feeding it to make with UCLIBC_CONFIG_FILE=)
The make however quits with:
make[2]: *** [libc/libc.oS] Error 1
make[1]: *** [lib/libc.so.0] Error 2
make[1]: Leaving directory `buildroot/toolchain_build_i586/uClibc-0.9.29'
make: *** [buildroot/toolchain_build_i586/uClibc-0.9.29/lib/libc.a] Error 2
Host system checks:
CC clean: Ok
CXX clean: Ok
CPP clean: Ok
CFLAGS clean: Ok
INCLUDES clean: Ok
CXXFLAGS clean: Ok
which installed: Ok
sed works: Ok (/bin/sed)
GNU make version '3.81': Ok
C compiler '/usr/bin/gcc'
C compiler version '4.1.2': Ok
C++ compiler '/usr/bin/g++'
C++ compiler version '4.1.2': Ok
bison installed: Ok
flex installed: Ok
gettext installed: Ok
makeinfo installed: Ok
Build system dependencies: Ok
Anyone have any ideas ?
Cheers,
Albert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGk6bUKltZixSsH2QRA/yGAJ9Zjymxmi7R7CvRZZ6NE5fOvOWCpQCdHTqY
EAdu/f/cR+s44RthwmSQF4s=
=OEpn
-----END PGP SIGNATURE-----
reply other threads:[~2007-07-10 15:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4693A6D4.9080707@friendly.net \
--to=albert@friendly.net \
--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