On Mon, Nov 13, 2017 at 11:01 PM, Tomasz Kłoczko <[email protected]> wrote: > On 13 November 2017 at 10:52, Björn 'besser82' Esser > <[email protected]> wrote: <snip> > However AFAIK only reason of any issues related to use -Wl,--as-needed > is using WRONG list -l<foo> parameters (lack of some -l<foo>) and this > needs to be not treated by apply some workaround but but by apply > necessary fixes in -l<foo> linking parameters.
Off the top of my head I can see glibc leading to "over" linking: if upstream is not GNU/Linux-only it may need -lm, -lrt, -lsocket, -lnls etc for other platforms. For autotools-based projects depending on how you do the functions detection it may or may not add the -l* flags to $LIBS if provided by the libc. Dridi _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
