emerging firefox fails because of 097_noxul_glibc-maxpathlen.patch: * Failed Patch: 097_noxul_glibc-maxpathlen.patch ! * ( /var/tmp/portage/www-client/mozilla-firefox-3.0.13/work/patch/097_noxul_glibc-maxpathlen.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/www-client/mozilla-firefox-3.0.13/temp/097_noxul_glibc-maxpathlen.patch-10356.out * * ERROR: www-client/mozilla-firefox-3.0.13 failed. * Call stack: * ebuild.sh, line 49: Called src_prepare * environment, line 3346: Called epatch '/var/tmp/portage/www-client/mozilla-firefox-3.0.13/work/patch' * environment, line 1779: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: 097_noxul_glibc-maxpathlen.patch! Reproducible: Always
Created attachment 202309 [details] build log
Created attachment 202310 [details] patch output
Yes, that is known, but because of security vulnerabilities it was decied to ignore that failure as nobody will built without USE=xulrunner. :) We were wrong.
Yes, you are ;). But i already noticed that support for xulrunner flag is dropped in more recent versions of firefox so i decided to enable USE=xulrunner which hopefully fixes it. It would be nice if you could tell me what xulrunner is needed for or if you point me to a site where this is explained (i switched xulrunner off because i couldnt figure out whats its useful for).
From https://developer.mozilla.org/en/XULRunner "XULRunner provides an environment for developers to build XUL-based applications such as Firefox and Thunderbird. It provides mechanisms for installing, upgrading, and uninstalling applications." So XULRunner is the base on which Firefox is built on.
Either the patching should be fixed, or the xulrunner flag should be forced for this ebuild. Compiling with -xulrunner is a time and download saver when you dont have any other firefox-dependent ebuilds. AFAIK, there is no behavior difference between having the flag on or off ?
Fixed
