Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 655220 - Firefox ebuilds fail to emerge because of autoconf issue
Summary: Firefox ebuilds fail to emerge because of autoconf issue
Status: RESOLVED DUPLICATE of bug 654600
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords: Bug, EBUILD
Depends on:
Blocks:
 
Reported: 2018-05-07 20:42 UTC by Povilas Brilius
Modified: 2018-05-08 03:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info '=www-client/firefox-59.0.2::gentoo (emerge.info,6.14 KB, text/plain)
2018-05-07 20:42 UTC, Povilas Brilius
Details
emerge -pqv '=www-client/firefox-59.0.2::gentoo (file_655220.txt,735 bytes, text/plain)
2018-05-07 20:44 UTC, Povilas Brilius
Details
/var/tmp/portage/www-client/firefox-59.0.2/temp/build.log (build.log,6.62 KB, text/x-log)
2018-05-07 20:45 UTC, Povilas Brilius
Details
/var/tmp/portage/www-client/firefox-59.0.2/temp/autoconf-1.out (autoconf-1.out,317 bytes, text/plain)
2018-05-07 20:46 UTC, Povilas Brilius
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Povilas Brilius 2018-05-07 20:42:29 UTC
Created attachment 530382 [details]
emerge --info '=www-client/firefox-59.0.2::gentoo

The ~amd64 gnome-base/gnome and profile unable to resolve none of firefox ebuilds, triggering "Failed Running autoconf" message.
Comment 1 Povilas Brilius 2018-05-07 20:44:08 UTC
Created attachment 530384 [details]
emerge -pqv '=www-client/firefox-59.0.2::gentoo
Comment 2 Povilas Brilius 2018-05-07 20:45:46 UTC
Created attachment 530386 [details]
/var/tmp/portage/www-client/firefox-59.0.2/temp/build.log
Comment 3 Povilas Brilius 2018-05-07 20:46:35 UTC
Created attachment 530388 [details]
/var/tmp/portage/www-client/firefox-59.0.2/temp/autoconf-1.out
Comment 4 Coacher 2018-05-08 03:41:23 UTC

*** This bug has been marked as a duplicate of bug 654600 ***