https://sourceware.org/bugzilla/show_bug.cgi?id=27360
--- Comment #15 from Nick Alcock <nick.alcock at oracle dot com> --- The real question is where the -L/usr/lib is coming from. If you dig into config.status it should become clear. I bet this is derived from some .la file somewhere, so that libtool thinks it needs -L/usr/lib -lfoo to get at libfoo, and this causes trouble for everything else later in the link line. Including syslibdirs in libtool .la files like that is generally considered to be a problem with the local system's setup (though because libtool has no real way to work around it or stop it from happening, it is depressingly common). -- You are receiving this mail because: You are on the CC list for the bug.
