| Summary: | www-client/firefox-17.0.1 fails to build due to missing dependencies | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Steven Trogdon <strogdon> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
bzip of build.log without libvorbis installed
bzip of build.log with libvorbis installed |
||
|
Description
Steven Trogdon
2012-12-28 19:55:32 UTC
Created attachment 333618 [details]
bzip of build.log with libvorbis installed
Comment on attachment 333618 [details]
bzip of build.log with libvorbis installed
bzip of build.log with libvorbis installed
sorry for the duplicate comments I believe this is a PREFIX-only issue. libvorbis is not needed to build firefox-17.0.1 in native Gentoo. It would seem that the "missing" header vorbis/codec.h is really present in
${WORKDIR}/mozilla-release/media/libvorbis/include/vorbis/codec.h
and it is not being found in prefix. I suspect something similar to be the source of the "undefined references" since libogg is not needed either.
(In reply to comment #4) > I believe this is a PREFIX-only issue. libvorbis is not needed to build > firefox-17.0.1 in native Gentoo. It would seem that the "missing" header > vorbis/codec.h is really present in > > ${WORKDIR}/mozilla-release/media/libvorbis/include/vorbis/codec.h > > and it is not being found in prefix. I suspect something similar to be the > source of the "undefined references" since libogg is not needed either. What are you building on top of? That will be the keep input we need if we are gonna help address this issue. (In reply to comment #5) > (In reply to comment #4) > > I believe this is a PREFIX-only issue. libvorbis is not needed to build > > firefox-17.0.1 in native Gentoo. It would seem that the "missing" header > > vorbis/codec.h is really present in > > > > ${WORKDIR}/mozilla-release/media/libvorbis/include/vorbis/codec.h > > > > and it is not being found in prefix. I suspect something similar to be the > > source of the "undefined references" since libogg is not needed either. > > What are you building on top of? That will be the keep input we need if we > are gonna help address this issue. I'm not quite sure what it is you're asking. I've tried building firefox-17.0.1 on ~x86-linux and ~amd64-linux where the host OS is Debian. The emerge --info above is for the ~x86-linux prefix. On both prefixes vorbis/code.h cannot be found and the build fails. I've had no problem building the subject firefox on amd64 where libvorbis and libogg were not installed. I should have looked at the logs a little more closely. In the build.log "without libvorbis installed" there is the following:
>>> Configuring source in /storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/work/mozilla-release ...
/storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/environment: line 4190: mozversion_is_new_enough: command not found
/storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/environment: line 4216: mozversion_is_new_enough: command not found
/storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/environment: line 4237: mozversion_is_new_enough: command not found
The mozversion_is_new_enough() function is in the newer mozcoreconf-2.eclass but not in the mozcoreconf-2.eclass from the prefix-overlay. Without the newer eclass firefox-17.0.1 isn't building its internal libvorbis and libogg libraries. If I use the newer eclass then firefox-17.0.1 builds here in ~x86-linux and ~amd64-linux prefixes.
(In reply to comment #7) > I should have looked at the logs a little more closely. In the build.log > "without libvorbis installed" there is the following: > > >>> Configuring source in /storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/work/mozilla-release ... > /storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/ > environment: line 4190: mozversion_is_new_enough: command not found > /storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/ > environment: line 4216: mozversion_is_new_enough: command not found > /storage/strogdon/gentoo/var/tmp/portage/www-client/firefox-17.0.1/temp/ > environment: line 4237: mozversion_is_new_enough: command not found > > The mozversion_is_new_enough() function is in the newer mozcoreconf-2.eclass > but not in the mozcoreconf-2.eclass from the prefix-overlay. Without the > newer eclass firefox-17.0.1 isn't building its internal libvorbis and libogg > libraries. If I use the newer eclass then firefox-17.0.1 builds here in > ~x86-linux and ~amd64-linux prefixes. reassigning based on new info. I updated the eclass firefox-17.0.1 is gone, but firefox-17.0.2 fails to build in prefix for the same reason as the previous version. I believe the mozcoreconf-2.eclass in the prefix-overlay still needs to be sync'd against the current version in the main tree. Using this newer eclass does allow firefox to build. firefox-18.0 also doesn't build in prefix for other reasons, but that's another bug once the eclass issue is resolved. ah, I did never commit my sync of the eclass :( Done now. Sorry, this bug needs revisiting. |
