Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Change error message when linking fails #1709
I just lost half a day of work because the error message for linker failures is extremely misleading:
This suggests that the library isn't there, or at least not on cabals library search path. I had to turn on -v3 to find out that the problem wasn't that the library couldn't be found, but that it requires libm which wasn't linked to.
I suggest that upon failure to link the real error message (in this case, the one from gcc - I don't know what's being used on windows or osx) should always be reported. In any case, an error message shouldn't give a wrong impression of what the actual point of failure is if it can be helped at all.