Updating to libpq-8.2.4 fails during confingure stage. Configure fails with error message during threads-safety test. I encountered this error on two archs x86 and amd64 only during update with emerge -uND world (update was from 8.1.8 and 8.1.9 versions). Reproducible: Couldn't Reproduce Steps to Reproduce: Way to _emulate_ this bug: 1) ebuild /usr/portage/dev-db/libpq/libpq-8.2.4.ebuild unpack 2) cd /var/tmp/portage/dev-db/libpq-8.2.4/work/postgresql-8.2.4/src/ 3) rm -Rf test 4) ebuild /usr/portage/dev-db/libpq/libpq-8.2.4.ebuild merge Actual Results: Configure error message: "configure: error: thread test program failed This platform is not thread-safe. Check the file 'config.log'for the exact reason. You can use the configure option --enable-thread-safety-force to force threads to be enabled. But you must then run the program in src/test/thread and add locking function calls to your applications to guarantee thread safety." In config.log: "conftest.c:151:43: error: ./src/test/thread/thread_test.c: No such file or directory configure:22835: $? = 1 configure: program exited with status 1 configure: failed program was:" Expected Results: If unpack manually postgresql-test-8.2.4.tar.bz2 archive into work directory, configure must (!) complete normally, but sometimes it completes like bug #158509: "./configure: line 22838: 23774 Segmentation fault ./conftest$ac_exeext configure:22840: $? = 139 configure: program exited with status 139" (config.log) Maybe this is a portage bug. emerge --version on amd64: "Portage 2.1.2.6 (default-linux/amd64/2006.1, gcc-4.1.2, glibc-2.5-r2, 2.6.21-gentoo x86_64)" On x86 same version.
*** This bug has been marked as a duplicate of bug 176742 ***
Created attachment 118333 [details] Ebuild from official portage tree Ok, it was my mistake - I forgot to say that I have _already_fixed_ ebuild. (Not by patch from bug #176742, this is official ebuild from emerge --sync) There is fragment of ebuild " DESCRIPTION="PostgreSQL libraries." HOMEPAGE="http://www.postgresql.org/" SRC_URI="mirror://postgresql/source/v${PV}/postgresql-base-${PV}.tar.bz2 mirror://postgresql/source/v${PV}/postgresql-opt-${PV}.tar.bz2 threads? ( mirror://postgresql/source/v${PV}/postgresql-test-${PV}.tar.bz2 ) " LICENSE="POSTGRESQL" SLOT="4" IUSE="kerberos nls pam pg-intdatetime readline ssl threads zlib" " You see - "threads? ( mirror://postgresql/source/v${PV}/postgresql-test-${PV}.tar.bz2 )" - fetching of test-tarball depends of "threads" USE flag. But sometimes, when unpacking, this tar missed (but fetched!). So, it's very likely bug of portage, because unpack command is " src_unpack() { unpack ${A} cd "${S}" epatch "${FILESDIR}/${PN}-${PV}-gentoo.patch" } ", where A, I think, is a spechial variable for unpacking all fetched archives. (?).
So, i disagree with your verdict and reopens this bug
Post your emerge --info and attach the complete emerge log here.
Created attachment 118343 [details] emerge.log and log of problem "emerge libpq" Emerge log? What you exactly need? emerge.log? config.log? or _log_of_emerge_? This is tarball with emerge.log and one _log_of_emerge_ with error.
Portage 2.1.2.6 (default-linux/amd64/2006.1, gcc-4.1.2, glibc-2.5-r2, 2.6.21-gentoo x86_64) ================================================================= System uname: 2.6.21-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Gentoo Base System release 1.12.10 Timestamp of tree: Sat, 05 May 2007 19:20:01 +0000 dev-java/java-config: 1.3.7, 2.0.32 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.linux.ee/pub/gentoo/distfiles/ ftp://ftp.linux.ee/pub/gentoo/distfiles/ ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo http://mirror.gentoo.no/ http://mirror.aiya.ru/pub/gentoo/ ftp://mirror.aiya.ru/pub/gentoo/ http://ftp.ncnu.edu.tw/Linux/Gentoo/ ftp://ftp.ncnu.edu.tw/Linux/Gentoo/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="ru_RU.UTF-8" LC_ALL="" LINGUAS="ru" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/xeffects /usr/portage/local/layman/armagetron /usr/local/portage" SYNC="rsync://192.168.1.2/gentoo-portage" USE="X aac alsa amd64 arts async berkdb bitmap-fonts cdr cli cracklib crypt cups cvs dbus dri dsub dvd encode flac fortran gdbm gif gpm iconv ieee1394 isdnlog jabber javascript jpeg jpeg2k kde kdgraphics kerberos krb5 ldap ldapsam libg++ mad mailwrapper md5sum midi mp3 mpeg nas ncurses network nls nptl nptlonly nsplugin nvidia objc objc++ objc-gc odbc ogg opengl pam pcre pdf perl png postgres ppds pppd python qt3 qt4 readline reflection samba session spell spl ssl symlink tcpd theora threads tiff toolbar truetype truetype-fonts type1-fonts unicode usb utf8 vcd vorbis wine xcomposite xine xinerama xml xorg xprint xscreensaver zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 118345 [details] emerge log
<snip> This platform is not thread-safe. Check the file 'config.log'for the exact reason. </snip> Attach the whole config.log here (plaintext, no tarballs please).
Created attachment 118346 [details] config.log. As you wish...
Requied information provided, what next?
<snip> ./configure: line 22838: 15991 Segmentation fault ./conftest$ac_exeext </snip> Shrug; this is exact dupe of Bug 158509, so why did you exactly file this one? *** This bug has been marked as a duplicate of bug 158509 ***
Created attachment 118347 [details] config.log with "not found" error Sorry, I've attached wrong config file.
Well, file a new bug then. This one's already messy enough.
That's great. Open a new bug? Why? I have already provided you _all_ information you need. I have already solved MY problem, and tried to save time for others, but now it's YOUR problem, and you have all needed info to resolve it. Говоря по-русски: Вам, блин, пытаешься помочь, а к тебе относятся, как будто ты их обмануть хочешь. Запад, блин, культура, оплот, блин, цивилизации неверия. Нах нам такая цивилицация?
(In reply to comment #14) > That's great. Open a new bug? Why? <snip> conftest.c:151:43: error: ./src/test/thread/thread_test.c: No such file or directory </snip> is a dupe of Bug 176742; either you attached a wrong log again or I really fail to see what are you after here. If you have something different than dupes of Bug 176742 or dupe of Bug 158509, then go file a *new* bug for that issue; otherwise move to the relevant bugs posted above.
Please read the _first_ post, before making any desicions And i repeat _again_. This is NOT a Bug 176742, because this is _already_fixed_ebuild_. And this is NOT a Bug 158509, because the segmentstion fault error makes possible only after resolving "not found" bug. And i wrote this into the _first_ post. I even refer to corresponding bug, so I already read it when making this bug. I've post config.log, while in the _first_ post was all needed information from it. I've post emerge --info, while in _first_ post was all needed information about portage version. I even said where this bug could be - file fetched, but not unpacked, so bug is _inside_ebuild_ build-it variable "A", if it is built-in variable. I provide you all information that you asked for, but you just close bug again ang again marking it as duplicate of another two bugs, while I already post all differences beetwen this bugs. And now you ask me just to open a new bug? To start all this again? No, thanks. If you are not interested in resolving this bug - this is you problems now. Good luck.
