https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220103
--- Comment #26 from Dimitry Andric <d...@freebsd.org> ---
In any case, I just tried www/chromium, and it does exactly the same dumb thing
as mplayer:
$ cat
/wrkdirs/usr/ports/www/chromium/work/chromium-68.0.3440.106/build/linux/chrome.map
{
global:
__bss_start;
__data_start;
data_start;
_edata;
_end;
_IO_stdin_used;
[...]
local:
*;
};
I think that the idea is to explicitly "whitelist" any variables that are safe
to export from the main executable, and hide everything else under local. What
the use of such a scheme is, is not really clear.
If we don't want to mess with this system too much, we might want to simply add
"environ" and any other necessary symbols to the global list
Alternatively, we could just get rid of the linker script completely, and use a
similar approach for mplayer. We certainly don't need the glibc specific
_IO_stdin_used hack.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
