| View previous topic :: View next topic |
| Author |
Message |
djpenguin
Guru
Joined: 02 Sep 2004
Posts: 386
|
 Posted: Sun Feb 19, 2006 7:58 pm Post subject: glibc won't compile - router [SOLVED] |
 |
|
I am working on setting up an old 500MHz Katmai box as a router for my home LAN. I have done a successful stage3 install from an x86 universal LiveCD, and now I am working on adding some security functionality with help from the Hardened Gentoo project. I have installed and compiled hardened-sources with PaX enabled, and successfully booted the machine. Now I am trying to recompile the toolchain with the hardened USE flag turned on, but the emerge fails every time on glibc, with a very unhelpful error message:
| Code: | /var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.o:/var/tmp/portage/glibc-2.3.5-r2/work
/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.S:15: undefined reference to `.LC2'
/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.o:/var/tmp/portage/glibc-2.3.5-r2/work
/build-default-i686-pc-linux-gnu-linuxthreads/csu/crtn.S:38: undefined reference to `.LC3'
collect2: ld returned 1 exit status
make[2]: *** [/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/iconv/iconvconfig] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconv'
make[1]: *** [iconv/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
make: *** [all] Error 2
!!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
!!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.
|
I really have no idea what to do here, so any help at all would be greatly appreciated. Here is the "emerge info" output for the machine:
| Code: | dirtbag ~ # emerge info
Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.4.20041102-r1, 2.6.14-hardened-r5 i686)
=================================================================
System uname: 2.6.14-hardened-r5 i686 Pentium III (Katmai)
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python: 2.3.5-r2
sys-apps/sandbox: 1.2.11
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils: 2.16.1
sys-devel/libtool: 1.5.18-r1
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -pipe -fstack-protector-all -mmmx -msse"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium3 -pipe -fstack-protector-all -mmmx -msse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv"
GENTOO_MIRRORS="http://gentoo.osuosl.org"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="x86 acl acpi alsa apm avi bash-completion berkdb bitmap-fonts bzip2 cdr clamav crypt cups eds emboss encode ethe
eal expat foomaticdb fortran ftp gdbm gif gpm gstreamer gtk2 hardened imlib jpeg libg++ libwww mad mikmod mmx motif m
3 mpeg ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pcre pdflib perl php png python quicktime readline sdl
pell sse ssl tcpd truetype truetype-fonts type1-fonts udev usb vorbis xml2 xmms xv zlib userland_GNU kernel_linux eli
c_glibc"
Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
|
_________________
Don't put your system specs in your sig. Nobody cares.
Last edited by djpenguin on Tue Feb 21, 2006 12:04 am; edited 1 time in total |
|
| Back to top |
|
 |
yther
Apprentice
Joined: 25 Oct 2002
Posts: 151
Location: Charlotte, NC (USA)
|
| Posted: Sun Feb 19, 2006 9:23 pm Post subject: |
|
|
Unfortunately, as I have discovered, not all packages can yet be built on hardened systems. glibc remains one of them. See this bug, and search "glibc hardened" for others.
The easiest way past this is to use gcc-config to change your profile to vanilla, emerge glibc, set it back to normal, and continue with your updates. That's the only way I've been able to build it here. |
|
| Back to top |
|
|
curtis119
Bodhisattva
Joined: 10 Mar 2003
Posts: 2160
Location: Toledo, Ohio,USA, North America, Earth, SOL System, Milky Way, The Universe, The Cosmos, and Beyond.
|
|
| Back to top |
|
|
djpenguin
Guru
Joined: 02 Sep 2004
Posts: 386
|
| Posted: Mon Feb 20, 2006 7:26 am Post subject: |
|
|
First, I have read a fair number of the Hardened project docs, I'm just brand new to this whole thing. I never ask questions on the forum unless I have been unable to find an answer with the docs, forums, and google. The reason I put -fstack-protector-all in the CFLAGS is because the PaX Quickstart Guide suggests doing so :
| Code: | | Note: In newer versions of SSP, it is possible to apply SSP to all functions, adding protection to functions whose buffer would normally be below the size limit for SSP. This is enabled via the CFLAG -fstack-protector-all. |
I put -mmmx and -msse in there because Ihave been running my P4 machine with those settngs for a year or so with no problems at all. I was unaware that they caused problems with the hardened toolchain.
I'll move them all to the USE flags section and try it again.
_________________
Don't put your system specs in your sig. Nobody cares. |
|
| Back to top |
|
|
djpenguin
Guru
Joined: 02 Sep 2004
Posts: 386
|
| Posted: Mon Feb 20, 2006 11:56 pm Post subject: |
|
|
Well, I've successfully compiled glibc, but I would still like to know if the PaX quickstart guide is wrong about -fstack-protector-all being a CFLAG.
_________________
Don't put your system specs in your sig. Nobody cares. |
|
| Back to top |
|
|
curtis119
Bodhisattva
Joined: 10 Mar 2003
Posts: 2160
Location: Toledo, Ohio,USA, North America, Earth, SOL System, Milky Way, The Universe, The Cosmos, and Beyond.
|
| Posted: Tue Feb 21, 2006 12:11 am Post subject: |
|
|
| djpenguin wrote: | | Well, I've successfully compiled glibc, but I would still like to know if the PaX quickstart guide is wrong about -fstack-protector-all being a CFLAG. |
Me too. I'll see if I can get one the relevant devs to comment here about it.
_________________
Gentoo: it's like wiping your ass with silk. |
|
| Back to top |
|
|
spb
Retired Dev
Joined: 02 Jan 2004
Posts: 2135
Location: Cambridge, UK
|
| Posted: Tue Feb 21, 2006 12:17 am Post subject: |
|
|
| djpenguin wrote: | | Well, I've successfully compiled glibc, but I would still like to know if the PaX quickstart guide is wrong about -fstack-protector-all being a CFLAG. |
It's a valid compiler flag, but you shouldn't put it in your CFLAGS. The hardened GCC specfiles take care of enabling it where it's beneficial and won't break stuff. |
|
| Back to top |
|
|
djpenguin
Guru
Joined: 02 Sep 2004
Posts: 386
|
| Posted: Wed Feb 22, 2006 6:51 pm Post subject: |
|
|
Excellent, thanks so much for taking the time to clear that up.
_________________
Don't put your system specs in your sig. Nobody cares. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
