Summary: | www-client/firefox ignores CC/CXX | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
www-client:firefox-38.4.0:20151108-080056.log.xz
www-client:firefox-45.2.0:20160703-150541.log.xz |
Description
Jeroen Roovers (RETIRED)
2015-11-08 09:35:57 UTC
Could you attach the full build.log? This /lib/cpp for the C preprocessor and C++ preprocessor looks very odd, I'd like to see the rest of the configure output.. Created attachment 417010 [details]
www-client:firefox-38.4.0:20151108-080056.log.xz
All versions are now affected. I have no idea if this will help or not, but, please try firefox-46.0 from the mozilla overlay. I've just pushed the various changes (except for one patch related to the system-NSS detection in the build system) that has allowed me to successfully cross-build firefox and thunderbird. I don't know if this will suffice or not, but it's worth a shot. The only other possible option will be to assing CC, CXX, etc via MOZ_MAKE_FLAGS, but I honestly don't think that's going to make any difference. New versions in the tree now with the changes described, please check. In 45.2.0 I see it is still using `cc` to compile nsinstall early on in the build process. It is likely that it picks `cc` by default, i.e. for that part of the build CC is not set. Since it's a build only tool, I guess this will still make the build fail when using distcc. Created attachment 439692 [details]
www-client:firefox-45.2.0:20160703-150541.log.xz
Did these changes go into 45.2.0 at all?
(In reply to Jeroen Roovers from comment #7) > Created attachment 439692 [details] > www-client:firefox-45.2.0:20160703-150541.log.xz > > Did these changes go into 45.2.0 at all? Some did, some didn't it seems. 46.0 was the one I pushed everything to. That said I've just committed a change to the mozcoreconf eclass that I think will resolve these things once and for all. Give it another shot and let me know? How does firefox-45.3 do? If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team |