Dear all, I successfully compiled stage3 and stage1 from scratch but I can't compile stage2.. it seems there is a problem with klibc.. any ideas ? Best regards, Jo
Dear all, I successfully compiled stage3 and stage1 from scratch but I can't compile stage2.. it seems there is a problem with klibc.. any ideas ? Best regards, João Brázio. # make stage2 rm gnap_make* >/dev/null 2>&1 gnap_make -t livecd-stage2 \ -p /root/gnap/snapshots/portage.tar.bz2 \ -c /root/gnap/livecds/foobar/catalyst/catalyst.conf \ -s /root/gnap/livecds/foobar/core/stage3-x86-foobar.tar.bz2 \ -e /root/gnap/livecds/foobar/specs \ -v foobar GNAP Core Building tool gnap_make version 1.8.2 * Checking parameters... [ ok ] * The following targets will be called: * [livecd-stage2] * Preparing portage snapshot... [ ok ] * [livecd-stage2] stage (kernel and LiveCD builds)... [ !! ] * [livecd-stage2] failed, see ./gnap_make-foobar.err and .out for details [ !! ] * Cleaning temporary directories... [ ok ] Build failed, try man gnap_make for more help make: *** [stage2] Error 1 # cat chroot()/var/log/genkernel.log (..) klibc/recv.o: In function `recv': klibc/recv.c:9: undefined reference to `__guard' klibc/recv.c:11: undefined reference to `__stack_smash_handler' klibc/libgcc/__divdi3.o: In function `__divdi3': klibc/libgcc/__divdi3.c:11: undefined reference to `__guard' klibc/libgcc/__divdi3.c:29: undefined reference to `__stack_smash_handler' klibc/libgcc/__moddi3.o: In function `__moddi3': klibc/libgcc/__moddi3.c:11: undefined reference to `__guard' klibc/libgcc/__moddi3.c:29: undefined reference to `__stack_smash_handler' klibc/libgcc/__udivdi3.o: In function `__udivdi3': klibc/libgcc/__udivdi3.c:11: undefined reference to `__guard' klibc/libgcc/__udivdi3.c:13: undefined reference to `__stack_smash_handler' klibc/libgcc/__umoddi3.o: In function `__umoddi3': klibc/libgcc/__umoddi3.c:11: undefined reference to `__guard' klibc/libgcc/__umoddi3.c:16: undefined reference to `__stack_smash_handler' klibc/libgcc/__udivmoddi4.o: In function `__udivmoddi4': klibc/libgcc/__udivmoddi4.c:5: undefined reference to `__guard' klibc/libgcc/__udivmoddi4.c:32: undefined reference to `__stack_smash_handler' make[3]: *** [klibc/libc.so] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [all] Error 2 make[1]: *** [klibc] Error 2 make[1]: Leaving directory `/var/tmp/genkernel/16955.29235.3942.16318/klibc-1.1.16' * --udev is deprecated and no longer necessary as udev is on by default * Gentoo Linux Genkernel; Version 3.3.11 * Running with options: --no-bootsplash --no-mountboot --kerneldir=/usr/src/linux --kernel-config=/var/tmp/gentoo.config --minkernpackage=/usr/portage/packages/gk_binaries/gentoo-foobar.tar.bz2 all --kernel-cc=/usr/lib/ccache/bin/gcc --utils-cc=/usr/lib/ccache/bin/gcc --udev * ERROR: Failed to compile the "ARCH=i386" target... * -- Grepping log... -- * -- End log... -- * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively. * * Please do *not* report compilation failures as genkernel bugs! # cat chroot()/etc/genkernel.conf (..) UDEV_VER="077" UDEV_DIR="udev-${UDEV_VER}" UDEV_SRCTAR="${GK_SHARE}/pkg/udev-${UDEV_VER}.tar.bz2" UDEV_BINCACHE="%%CACHE%%/udev-${UDEV_VER}-%%ARCH%%.tar.bz2" KLIBC_VER="1.1.16" KLIBC_DIR="klibc-${KLIBC_VER}" KLIBC_SRCTAR="${GK_SHARE}/pkg/klibc-${KLIBC_VER}.tar.bz2" KLIBC_BINCACHE="%%CACHE%%/klibc-${KLIBC_VER}-%%ARCH%%.tar.bz2" (..) # emerge --info Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r3, 2.6.15-gentoo-r1 i686) ================================================================= System uname: 2.6.15-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=i686 -O2 -pipe" 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="-march=i686 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apm berkdb bzip2 ccache cdr crypt ctype dba elibc_glibc gdbm idn kernel_linux memlimit ncurses nptl pam pcre perl posix python readline samba sdl session sockets tcpd udev userland_GNU x86 zlib" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
This is dupe of Bug 120678, don't know which klibc version this stage and genkernel uses, but apparently needs a bump.
I think.. # cat chroot()/etc/genkernel.conf (..) UDEV_VER="077" UDEV_DIR="udev-${UDEV_VER}" UDEV_SRCTAR="${GK_SHARE}/pkg/udev-${UDEV_VER}.tar.bz2" UDEV_BINCACHE="%%CACHE%%/udev-${UDEV_VER}-%%ARCH%%.tar.bz2" KLIBC_VER="1.1.16" KLIBC_DIR="klibc-${KLIBC_VER}" KLIBC_SRCTAR="${GK_SHARE}/pkg/klibc-${KLIBC_VER}.tar.bz2" KLIBC_BINCACHE="%%CACHE%%/klibc-${KLIBC_VER}-%%ARCH%%.tar.bz2" (..)
(In reply to comment #1) > This is dupe of Bug 120678, don't know which klibc version this stage and > genkernel uses, but apparently needs a bump. >------- Comment #4 From Jonathan Leatherwood 2006-02-11 20:16 PST [reply] ------- >This bug is fixed in klibc-1.2.1-r1. How can I tell GNAP/Genkernel to use klibc-1.2.1 ?
(In reply to comment #3) > >This bug is fixed in klibc-1.2.1-r1. > > How can I tell GNAP/Genkernel to use klibc-1.2.1 ? Unfortunately genkernel uses its own klibc so it needs an update. You should mask genkernel-3.3.11 which includes a buggy version, until genkernel gets fixed (plasmaroo is working on it). That way GNAP will use genkernel-3.3.10 which works ok. Translated into GNAP words : Add ">sys-kernel/genkernel-3.3.10" to your specs/portage_confdir/package.mask and rerun your gnap_make (at least from livecd-stage1 to get the correct genkernel version emerged).
(In reply to comment #4) > (In reply to comment #3) > > >This bug is fixed in klibc-1.2.1-r1. > > > > How can I tell GNAP/Genkernel to use klibc-1.2.1 ? > > Unfortunately genkernel uses its own klibc so it needs an update. You should > mask genkernel-3.3.11 which includes a buggy version, until genkernel gets > fixed (plasmaroo is working on it). That way GNAP will use genkernel-3.3.10 > which works ok. > > Translated into GNAP words : > > Add ">sys-kernel/genkernel-3.3.10" to your specs/portage_confdir/package.mask > and rerun your gnap_make (at least from livecd-stage1 to get the correct > genkernel version emerged). > Perfect, I'm compiling it with genkernel-3.3.10 and so far so good. Does this genkernel-3.3.11 bug applies only to GNAP or can it be reproduced on a "real" Gentoo system ?
(In reply to comment #5) > Perfect, > I'm compiling it with genkernel-3.3.10 and so far so good. > > Does this genkernel-3.3.11 bug applies only to GNAP or can it be reproduced on > a "real" Gentoo system ? Only if it's running Gentoo/Hardened. Koon, this is fixed in 3.3.11a.
Fixed in GNAP 2.0rc1 Available for test at http://dev.gentoo.org/~koon/gnap-2.0rc1/
Version 2.0 is out
