Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/portage-2.0.51-r3 to / >>> md5 src_uri ;-) portage-2.0.51-r3.tar.bz2 >>> Unpacking source... >>> Unpacking portage-2.0.51-r3.tar.bz2 to /var/tmp/portage/portage-2.0.51-r3/work bzip2: Caught a SIGSEGV or SIGBUS whilst decompressing. Possible causes are (most likely first): (1) The compressed data is corrupted, and bzip2's usual checks failed to detect this. Try bzip2 -tvv my_file.bz2. (2) This computer has unreliable memory or cache hardware (a surprisingly common problem; try a different machine.) (3) A bug in the compiler used to create this executable (unlikely, if you didn't compile bzip2 yourself.) (4) A real bug in bzip2 -- I hope this should never be the case. The user's manual, Section 4.3, has more info on (2) and (3). If you suspect this is a bug in bzip2, or are unsure about (2) or (3), feel free to report it to me at: jseward@acm.org. Section 4.3 of the user's manual describes the info a useful bug report should have. If the manual is available on your system, please try and read it before mailing me. If you don't have the manual or can't be bothered to read it, mail me anyway. Input file = /usr/portage/distfiles/portage-2.0.51-r3.tar.bz2, output file = (stdout) It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. tar: Read 1120 bytes from - tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Reproducible: Always Steps to Reproduce: 1.untar stage1-x86.tar.bz2 && portage-20041124.tar.bz2 2.cd /usr/portage && scripts/bootstrap.sh 3. Actual Results: Caught a SIGSEGV or SIGBUS whilst decompressing. Expected Results: finish bootstrap Gentoo Linux; http://www.gentoo.org/ Copyright 1999-2004 Gentoo Foundation; Distributed under the GPLv2 Starting Bootstrap of base system ... ------------------------------------------------------------------------------- * Using baselayout : >=sys-apps/baselayout-1.9.4-r3 * Using portage : >=sys-apps/portage-2.0.51 * Using os-headers : virtual/os-headers * Using binutils : >=sys-devel/binutils-2.14.90.0.8-r1 * Using gcc : >=sys-devel/gcc-3.3.4-r1 * Using gettext : sys-devel/gettext * Using libc : virtual/libc * Using texinfo : sys-apps/texinfo * Using zlib : sys-libs/zlib * Using ncurses : sys-libs/ncurses ------------------------------------------------------------------------------- Configuring environment ... * GENTOO_MIRRORS='http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/ distributions/gentoo' * PORTDIR='/usr/portage' * DISTDIR='/usr/portage/distfiles' * PKGDIR='/usr/portage/packages' * PORTAGE_TMPDIR='/var/tmp' * CFLAGS='-march=i586 -O2 -mcpu=i586 -fomit-frame-pointer -pipe' * CHOST='i586-pc-linux-gnu' * CXXFLAGS='-march=i586 -O2 -mcpu=i586 -fomit-frame-pointer -pipe' * MAKEOPTS='-j2' * ACCEPT_KEYWORDS='x86' * FEATURES='autoaddcvs autoconfig ccache distlocks sandbox sfperms' ------------------------------------------------------------------------------- Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/portage-2.0.51-r3 to / >>> md5 src_uri ;-) portage-2.0.51-r3.tar.bz2 >>> Unpacking source... >>> Unpacking portage-2.0.51-r3.tar.bz2 to /var/tmp/portage/portage-2.0.51-r3/ work bzip2: Caught a SIGSEGV or SIGBUS whilst decompressing. Possible causes are (most likely first): (1) The compressed data is corrupted, and bzip2's usual checks failed to detect this. Try bzip2 -tvv my_file.bz2. (2) This computer has unreliable memory or cache hardware (a surprisingly common problem; try a different machine.) (3) A bug in the compiler used to create this executable (unlikely, if you didn't compile bzip2 yourself.) (4) A real bug in bzip2 -- I hope this should never be the case. The user's manual, Section 4.3, has more info on (2) and (3). If you suspect this is a bug in bzip2, or are unsure about (2) or (3), feel free to report it to me at: jseward@acm.org. Section 4.3 of the user's manual describes the info a useful bug report should have. If the manual is available on your system, please try and read it before mailing me. If you don't have the manual or can't be bothered to read it, mail me anyway. Input file = /usr/portage/distfiles/portage-2.0.51-r3.tar.bz2, output file = (stdout) ****************************make.conf******************************************* These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-march=i586 -O2 -mcpu=i586 -fomit-frame-pointer -pipe" CHOST="i586-pc-linux-gnu" CXXFLAGS="${CFLAGS}" USE="xv slang readline gpm berkdb mmx 3dnow gdbm tcpd pam libwww ssl nls mitshm arts inlib sdl oggvorbis gtk X qt kde notif opengl avi png tiff gif" LINGUAS="pl" ***************************************end**************************************
Are you sure the hardware is good? Are you sure your download was good of portage?
can you verify the integrity of your hardware?
