On 04/15/2013 01:46 PM, Tanstaafl wrote: > On 2013-04-15 11:42 AM, Michael Mol <mike...@gmail.com> wrote: >> On 04/15/2013 11:37 AM, Tanstaafl wrote: >>> Hi all, >>> >>> Help!!!!! :( >> >> [snip] >> >>> >>> I've tried recompiling both (both compile/install ok), but when I try to >>> start SSHD I get: >>> >>> # /etc/init.d/sshd start >>> /etc/init.d/sshd: line 18: 2079 Illegal instruction "${SSHD_BINARY}" -t >>> ${SSHD_OPTS} >>> * ERROR: sshd failed to start >> >> ^^ That screams 'CFLAGS' issue. Verify that the CFLAGS for your prod >> server are the same (or close enough) to that of your dev server. >> >> Guessing the new host has different CPU capabilities exposed to the >> guest, either because of a differing hypervisor configuraiton, or >> because of the different underlying hardware. > > Ok, as I said, I got SSH working now and am making progress, updating > @system a little at a time... > > Before I started updating everything in @system though, I tried ncurses > again (one of the first ones that failed on me), and it still dies with > this: > > INFO: setup > Package: sys-libs/ncurses-5.9-r2 > Repository: gentoo > Maintainer: base-sys...@gentoo.org > USE: abi_x86_32 cxx elibc_glibc gpm kernel_linux unicode > userland_GNU x86 > FEATURES: sandbox > INFO: unpack > Applying ncurses-5.8-gfbsd.patch ... > Applying ncurses-5.7-nongnu.patch ... > Applying ncurses-5.9-rxvt-unicode-9.15.patch ... > Applying ncurses-5.9-fix-clang-build.patch ... > ERROR: compile > ERROR: sys-libs/ncurses-5.9-r2 failed (compile phase): > (no error message) > > Call stack: > ebuild.sh, line 93: Called src_compile > environment, line 2340: Called do_compile 'narrowc' > environment, line 467: Called die > The specific snippet of code: > emake ${make_flags} || die > > If you need support, post the output of `emerge --info > '=sys-libs/ncurses-5.9-r2'`, > the complete build log and the output of `emerge -pqv > '=sys-libs/ncurses-5.9-r2'`. > The complete build log is located at > '/var/tmp/portage/sys-libs/ncurses-5.9-r2/temp/build.log'. > The ebuild environment file is located at > '/var/tmp/portage/sys-libs/ncurses-5.9-r2/temp/environment'. > Working directory: '/var/tmp/portage/sys-libs/ncurses-5.9-r2/work/narrowc' > S: '/var/tmp/portage/sys-libs/ncurses-5.9-r2/work/ncurses-5.9' > > Ideas?
I'd guess that something used as part of ncurses's build process is failing. Were this one of my systems (none of which is in a prod scenario, so take it with a grain of salt), I'd emerge -e --keep-going @system, and then emerge --resume a few times. You're stuck in something not unlike a bootstrap scenario. >
signature.asc
Description: OpenPGP digital signature