checking whether mknod can create fifo without root privileges... configure: error: in `/var/tmp/portage/app-arch/tar-1.24/work/tar-1.24': configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check) See `config.log' for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-arch/tar-1.24/work/tar-1.24/config.log * ERROR: app-arch/tar-1.24 failed: * econf failed
Created attachment 251901 [details] config.log
Created attachment 251903 [details, diff] patch Kind of obvious, but oh well :P
I confirm. I don't have userpriv in FEATURES and it fails with this exact error message... Another solution is, as mentioned in the message, to FORCE_UNSAFE_CONFIGURE=1 emerge -1 tar.
same error checking whether mbrtowc works as well as mbtowc... (cached) guessing yes checking whether mbrtowc handles incomplete characters... (cached) guessing yes checking whether mbrtowc works as well as mbtowc... (cached) guessing yes checking whether mbsrtowcs works... guessing yes checking for mempcpy... (cached) yes checking for memrchr... yes checking whether mkdir handles trailing slash... yes checking whether mkdir handles trailing dot... yes checking for mkdtemp... yes checking whether mkfifo rejects trailing slashes... yes checking whether mknod can create fifo without root privileges... configure: error: in `/var/tmp/portage/app-arch/tar-1.24/work/tar-1.24': configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check) See `config.log' for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-arch/tar-1.24/work/tar-1.24/config.log * ERROR: app-arch/tar-1.24 failed: * econf failed * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 2701: Called econf '--enable-backup-scripts' '--bindir=/bin' '--libexecdir=/usr/sbin' '--enable-nls' * ebuild.sh, line 558: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of 'emerge --info =app-arch/tar-1.24', * the complete build log and the output of 'emerge -pqv =app-arch/tar-1.24'. * The complete build log is located at '/var/log/portage/app-arch:tar-1.24:20101025-101620.log'. * The ebuild environment file is located at '/var/tmp/portage/app-arch/tar-1.24/temp/environment'. * S: '/var/tmp/portage/app-arch/tar-1.24/work/tar-1.24' * Messages for package app-arch/tar-1.24:
(In reply to comment #3) > I confirm. I don't have userpriv in FEATURES and it fails with this exact error > message... > > Another solution is, as mentioned in the message, to FORCE_UNSAFE_CONFIGURE=1 > emerge -1 tar. > (In reply to comment #3) > I confirm. I don't have userpriv in FEATURES and it fails with this exact error > message... > > Another solution is, as mentioned in the message, to FORCE_UNSAFE_CONFIGURE=1 > emerge -1 tar. > Confirming as well, on ~amd64. Same error message. Setting the FORCE_UNSAFE_CONFIGURE=1 worked around the problem. martijn@martijndesktop ~ $ emerge -pv tar These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] app-arch/tar-1.24 [1.23-r4] USE="nls -static" 0 kB
There is no need to say "Me too.". The issue is known and clear. Any posts from here on out are plain spam... so add yourself to CC list if you want, but that's it.
I don't know if it matters to the functionality of tar, but when configured with FORCE_UNSAFE_CONFIGURE=1, the result of the "checking whether mknod can create fifo without root privileges..." test is "no". However, if tar is configured by a non-root user on a Linux system, the result of this test should be "yes".
(In reply to comment #7) > I don't know if it matters to the functionality of tar, but when configured > with FORCE_UNSAFE_CONFIGURE=1, the result of the "checking whether mknod can > create fifo without root privileges..." test is "no". However, if tar is > configured by a non-root user on a Linux system, the result of this test should > be "yes". Replying to myself: when this test results in "no", MKNOD_FIFO_BUG is defined in config.h. The only use of this is in gnu/mknod.c and the only effect of this define is to cause mkfifo() to be called instead of mknod() to create FIFOs. The man page mknod(2) hints that mkfifo(3) is the preferred way of creating FIFOs nowadays, so the "no" result of the test should be perfectly harmless.
the var should be on a new line just like the "gl_cv_xxx" var above it. feel free to commit with that change.
+ 26 Oct 2010; Samuli Suominen <ssuominen@gentoo.org> tar-1.24.ebuild: + Fix ./configure with FEATURES="-userpriv" wrt #342593.
*** Bug 342737 has been marked as a duplicate of this bug. ***
