35969 ld: warning: file libmozjs.so: required by ../../toolkit/library/libxul.so, not found

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

35969 ld: warning: file libmozjs.so: required by ../../toolkit/library/libxul.so, not found

Richard PALO
after building libxul.so, there are issues building plugin-container and xpcshell where
libmozjs.so (needed by libxul.so) isn't provided.

One of the easier workarounds seems to be adding
>SHARED_LIBS += $(DEPTH)/js/src/libmozjs.so
after
>SHARED_LIBS += $(DEPTH)/toolkit/library/libxul.so
in the respective backend.mk

since backend.mk is a generated file, what would be the "right" way to add libmozjs.so?
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: 35969 ld: warning: file libmozjs.so: required by ../../toolkit/library/libxul.so, not found

Mike Hommey
On Sat, Jul 18, 2015 at 09:32:36AM +0200, Richard PALO wrote:

> after building libxul.so, there are issues building plugin-container and xpcshell where
> libmozjs.so (needed by libxul.so) isn't provided.
>
> One of the easier workarounds seems to be adding
> >SHARED_LIBS += $(DEPTH)/js/src/libmozjs.so
> after
> >SHARED_LIBS += $(DEPTH)/toolkit/library/libxul.so
> in the respective backend.mk
>
> since backend.mk is a generated file, what would be the "right" way to add libmozjs.so?

The "right" way would be to not build libmozjs.so. That is supposed to
be the default, btw. That said, there /is/ a subtle problem here that
should be fixed somehow, but isn't a problem in practice, at least
for default builds. Please file a bug.

Mike
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: 35969 ld: warning: file libmozjs.so: required by ../../toolkit/library/libxul.so, not found

Richard PALO
In reply to this post by Richard PALO
Le 18/07/15 11:27, Mike Hommey a écrit :

> On Sat, Jul 18, 2015 at 09:32:36AM +0200, Richard PALO wrote:
>> after building libxul.so, there are issues building plugin-container and xpcshell where
>> libmozjs.so (needed by libxul.so) isn't provided.
>>
>> One of the easier workarounds seems to be adding
>>> SHARED_LIBS += $(DEPTH)/js/src/libmozjs.so
>> after
>>> SHARED_LIBS += $(DEPTH)/toolkit/library/libxul.so
>> in the respective backend.mk
>>
>> since backend.mk is a generated file, what would be the "right" way to add libmozjs.so?
>
> The "right" way would be to not build libmozjs.so. That is supposed to
> be the default, btw. That said, there /is/ a subtle problem here that
> should be fixed somehow, but isn't a problem in practice, at least
> for default builds. Please file a bug.
>
> Mike
>

Ah, yes, I usually have --enable-shared-js with --with-system-libxul and --with-libxul-sdk
(which no longer works -(
this is because I can usually build fine xulrunner, but libxul.so under firefox non-shared balks with
> ld: fatal: relocation error: R_386_GOTOFF: file ../../js/src/Unified_cpp_js_src11.o: symbol vtable for JS::CustomAutoRooter: a GOT relative relocation must reference a local symbol
> ld: fatal: relocation error: R_386_GOTOFF: file ../../js/src/Unified_cpp_js_src11.o: symbol vtable for JS::CustomAutoRooter: a GOT relative relocation must reference a local symbol
> ld: fatal: relocation error: R_386_GOTOFF: file ../../js/src/Unified_cpp_js_src11.o: symbol vtable for JS::CustomAutoRooter: a GOT relative relocation must reference a local symbol
> ld: fatal: relocation error: R_386_GOTOFF: file ../../js/src/Unified_cpp_js_src11.o: symbol vtable for JS::CustomAutoRooter: a GOT relative relocation must reference a local symbol
> collect2: error: ld returned 1 exit status

I'll file a bug...

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds