Bug 289531 – gnome-base/libgtop-2.26.1: emerge fails with "could not determine how to read list of mounted filesystems" (mnttab)

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Frederic Leroy 2009-10-17 23:09:20 UTC]

when emerging libgtop-2.26.1, it fails with the following error : 
[...]
checking whether it is possible to resort to fread on /etc/mnttab... no
configure: error: could not determine how to read list of mounted filesystems

!!! Please attach the following file when seeking support:
[...]

Reproducible: Always

Steps to Reproduce:
emerge libgtop

[Comment 1 Frederic Leroy 2009-10-17 23:12:43 UTC]

Created attachment 207435 [details]
build.log

[Comment 2 Frederic Leroy 2009-10-17 23:13:40 UTC]

Created attachment 207437 [details]
config.log

[Comment 3 Frederic Leroy 2009-10-17 23:14:09 UTC]

Created attachment 207439 [details]
ebuild environment file

[Comment 4 Romain Perier (RETIRED) 2009-10-18 10:01:04 UTC]

--> CFLAGS='-O3 -march=pentium-m -pipe' <--

Please have a look at this link http://www.gentoo.org/doc/en/gcc-optimization.xml
especially this line "Using -O3 is not recommended for gcc 4.x."

so please re-try with standard and stable CFLAGS, by replacing -O3 with -O2

[Comment 5 Gilles Dartiguelongue (RETIRED) 2009-10-18 10:34:50 UTC]

emerge --info please

[Comment 6 Frederic Leroy 2009-10-18 10:50:28 UTC]

Created attachment 207466 [details]
output of emerge --info

I didn't notice yesterday the configure message "configure: WARNING: sys/bitypes.h: present but cannot be compiled"
I use a custom kernel and modify my linux-headers for some reason, it may be related.

[Comment 7 Gilles Dartiguelongue (RETIRED) 2009-10-18 10:51:59 UTC]

sounds likely.

[Comment 8 Frederic Leroy 2009-10-18 11:06:08 UTC]

after emerging sys-kernel/linux-headers, the error disappeared.
No other problem to report.

Thank you for your time :)

[Comment 9 Gilles Dartiguelongue (RETIRED) 2009-10-18 11:13:19 UTC]

reopening per provided information.

[Comment 10 Gilles Dartiguelongue (RETIRED) 2009-10-18 11:13:45 UTC]

closing invalid per comment #6 and comment #8. Thanks for reporting.