Pardon? I DID put the c file before any library, as I have clearly written in my bug report.
I cannot see how any of the comments in the release notes or changed link tool chain relate to my problem: I am putting an explicit -lm in the command line, and then the linker opens that library, and it sees the right symbols, and yet, it does not link libm, probably because also libfoo would have used it, too, but since libfoo isn't been linked, libm is apparently kicked out. Sorry, this is a misbehavior. Please reconsider this issue! It breaks the AC_CHECK_LIB macro of autoconf, as well as complex make environments where the use of certain libraries in specific executables is difficult to predict in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945927 Title: ld incorrectly gives 'undefined reference' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/945927/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
