| Summary: | VLC needs a full mozilla-sdk to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jure Repinc <jlp.bugs> |
| Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | josejx, mozilla |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jure Repinc
2005-06-26 23:47:42 UTC
Same error here, but with Intel Pentium-M, so not only a AMD64 problem. With USE flag 'mozilla' disabled, it builds correctly. Howto reproduce: # USE="mozilla" emerge vlc Ok this is going to require a bit of work also for mozilla herd. As for now, vlc hardly requires www-client/mozilla (suite) also if it just needs the development support. The problem is that just www-client/mozilla installs mozilla-config command (but firefox installs xpidl as does gecko-sdk). I'm going to disable mozilla support from 0.8.2 until a gecko-sdk which installs binaries and libraries in sane places and which provides all the needed files is in portage. I'm not going to change where gecko-sdk installs its files to, it is for applications that use the gecko-sdk framework only and I don't want it to collide with mozilla apps that install the same files. See the mplayerplug-in for an app that uses it. That said, what does exactly does VLC require that isn't provided by gecko-sdk? mozilla-config is the command that gecko-sdk misses. I don't want gecko-sdk to collide with other mozilla stuff, but putting binaries and libraries in /usr/share isn't good, and at least for amd64 multilib this is going to be a big headache. Where should I put it then so it doesn't collide with other packages? I'm open to suggestions that don't break mplayerplug-in. mozilla-config is not part of the gecko-sdk as distributed by mozilla, so VLC should really not depend on it being there unless it does actually depend on mozilla. Does VLC actually depend on Gecko-SDK or does it depend on Mozilla? VLC should build with just gecko-sdk also if it's not prepared to do so by default (the linux building procedure is quite a bit "if it works it works". It uses gecko-sdk on Win32 for example. About installing them elsewhere, installing them in /usr/$(get_libdir)/gecko-sdk[/bin] is a feasible option? Thats fine with me as long as it's okay to put the rest of the stuff currently in /usr/share/gecko-sdk into there as well. Would it be possible to get VLC to compile without providing mozilla-config or is that also requirement? I could probably try to hack its configure script not to use mozilla-configure, but if you are able to provide that, too, it's probably more portable for other software, too. vlc-0.8.2-r1 in portage works fine with +nsplugin . |
