After the following message is displayed, configure is not progress. checking whether pnmtops can handle the -nosetpage option... FYI, relevant part of configure { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether pnmtops can handle the -nosetpage option" >&5 $as_echo_n "checking whether pnmtops can handle the -nosetpage option... " >&6; } if echo P2 2 2 255 0 1 2 0 | pnmtops -nosetpage > /dev/null 2>&1 ; then { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 $as_echo "yes" >&6; } pnmtops_nosetpage="pnmtops -nosetpage" else { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 $as_echo "no" >&6; } pnmtops_nosetpage="pnmtops" fi Reproducible: Always Steps to Reproduce: 1. emerge media-libs/netpbm (pnmtops is included in this package) 2. cd /usr/portage/sys-apps/groff 3. ebuild groff-1.22.2.ebuild clean configure
Created attachment 354388 [details] results of ps aux I created it after one minute.
Created attachment 354390 [details, diff] sample patch for portage-2.2.0_alpha190/pym/portage/process.py Applying this patch, configure passed...
(In reply to Yuta SATOH from comment #2) > Created attachment 354390 [details, diff] [details, diff] > sample patch for portage-2.2.0_alpha190/pym/portage/process.py > > Applying this patch, configure passed... This patch doesn't look right to me. I've tested on FreeBSD 9.1 (GhostBSD 3.1 livecd), where it uses /dev/fd and it seems to work fine. The /proc/self/fd and /proc/$BASHPID/fd directories simply do not exist.
I've done some testing and is seems that /dev/fd does not work as expected on FreeBSD. Using python, os.listdir('/dev/fd') only reports ['0', '1' '2'] even after other files are opened. So, I've committed a variation of your patch: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ffc50e4d32706b8962d66cadd21fcd1d0cd58f13
I've confirmed that it's fixed in portage-2.2.0_alpha191. thanks!
