maintainer-feedback requested: [Bug 230239] graphics/mesa-libs: fails to build on i386 with lld as /usr/bin/ld

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
Bugzilla Automation <[email protected]> has asked freebsd-x11 mailing list
<[email protected]> for maintainer-feedback:
Bug 230239: graphics/mesa-libs: fails to build on i386 with lld as /usr/bin/ld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230239



--- Description ---
The migration to the LLVM project's lld linker as the system linker
(/usr/bin/ld) for FreeBSD is in progress - it is the case for arm64 and amd64
today, and i386 will switch once ports issues are addressed - see exp-run in
PR214864.

Attempting to link mesa-libs on i386 with lld fails with:

/usr/bin/ld: error: can't create dynamic relocation R_386_32 against symbol:
_glapi_Dispatch in readonly segment; recompile object files with -fPIC
>>> defined in .libs/shared_glapi_libglapi_la-u_current.o
>>> referenced by entry.c
>>>		  .libs/shared_glapi_libglapi_la-entry.o:(.text+0x1)

/usr/bin/ld: error: can't create dynamic relocation R_386_PC32 against symbol:
_glapi_get_dispatch in readonly segment; recompile object files with -fPIC
>>> defined in .libs/shared_glapi_libglapi_la-u_current.o
>>> referenced by entry.c
>>>		  .libs/shared_glapi_libglapi_la-entry.o:(.text+0xC)

/usr/bin/ld: error: can't create dynamic relocation R_386_32 against symbol:
_glapi_Dispatch in readonly segment; recompile object files with -fPIC
>>> defined in .libs/shared_glapi_libglapi_la-u_current.o
>>> referenced by entry.c
>>>		  .libs/shared_glapi_libglapi_la-entry.o:(.text+0x21)

...

http://package18.nyi.freebsd.org/data/headi386PR214864-default/2018-07-30_18h09
m59s/logs/errors/mesa-libs-18.1.4.log
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.