Skinning the cat...
Jul. 23rd, 2000 03:58 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpI don't know why I can't leave some things like this linking error alone when there are other things that need to be done around here. Maybe it's because they eat away at me. Maybe it's the basic geek need to conquer the machine. I don't know.
But I do know that there is often more than one way of getting to a goal. In this case, I changed the command line offered by `make', to
wit:
gcc -g -O2 -lxxxxx -o yyy yyy.o zzz.o
to the following:
gcc -g -O2 -o yyy yyy.o zzz.o /usr/lib/libxxxxx.a
Basically, the first line says "create executable yyy, using the object files yyy.o and zzz.o, and search libxxxxx.a for any unresolved references." The second line says the same thing, but lists the library along with the object files.
The sucker links.
FWIW, this involves using `gcc version 2.95.3 19991030 (prerelease)', which is pretty new, but apparently has a slight problem [in my opinion] with the `-l' flag.
Okay, now we can really go off and do around-the-house type stuff.
Cheers...
But I do know that there is often more than one way of getting to a goal. In this case, I changed the command line offered by `make', to
wit:
gcc -g -O2 -lxxxxx -o yyy yyy.o zzz.o
to the following:
gcc -g -O2 -o yyy yyy.o zzz.o /usr/lib/libxxxxx.a
Basically, the first line says "create executable yyy, using the object files yyy.o and zzz.o, and search libxxxxx.a for any unresolved references." The second line says the same thing, but lists the library along with the object files.
The sucker links.
FWIW, this involves using `gcc version 2.95.3 19991030 (prerelease)', which is pretty new, but apparently has a slight problem [in my opinion] with the `-l' flag.
Okay, now we can really go off and do around-the-house type stuff.
Cheers...
