Undefined reference to 'sqrt'

Printable View

10-06-2009
VascoP

Undefined reference to 'sqrt'

-lm lib was indicated at the start of the project.

Im using the math.h include also.

So why do I keep getting it when using sqrt?

Kdevelop btw.
10-06-2009
quzah

Your problem is right there.
No, there. That's it.

Quzah.
10-06-2009
VascoP

Im sorry?
10-06-2009
tabstop

It may well be how you specified -lm. I don't use kdevelop so I can't say.
10-06-2009
brewbuck

When linking on UNIX, if a code module A depends on code module B, then module B must be listed after module A on the link line.

This is wrong:

Code:

gcc -lm -o myprogram myprogram.c

This is right:

Code:

gcc -o myprogram myprogram.c -lm
10-06-2009
quzah

Oh, I was just using my psychic powers to spot the issue. I assumed you'd use yours to see where I found the problem. Or you could search the forums and see what everyone else did. Or you could just compile it via command line:

gcc -o foo foo.c -lm

Quzah.
10-07-2009
VascoP

If a bit of thinking would solve it I would not browse the web trying to get an answer and ultimatly posting.

Im quite new to this and so I asked, thanks for the replies though, I can understand that every other thread is made by someone with a bit more knowledge so you're used to that :P
10-07-2009
core_cpp

While I can't presume to speak for quzah, I'm assuming he was just referring to your original post when you said:

Quote:

-lm lib was indicated at the start of the project

That jumped out at me right away before even reading the replies. So it almost seemed like you answered your own question right there. But I can certainly understand the whole deal... hey we've all been there.

Has nobody mentioned circular references yet? I haven't had to deal with those since my days on the DEC Alpha... either my code has gotten better or the linker has gotten smarter.
10-07-2009
brewbuck

Quote:

Originally Posted by core_cpp

Has nobody mentioned circular references yet? I haven't had to deal with those since my days on the DEC Alpha... either my code has gotten better or the linker has gotten smarter.

Yes, I've had problems with circular references before. Usually it means that two libraries which are separate are actually just two parts of a single library and should be merged. But in some cases the code is broken into libraries only for reasons of convenience. In either case the circular references are painful, but can always be resolved by:

Code:

-lA -lB -lA

Where A and B are mutually dependent libraries.