work emo: download library, write sample program, compile it, resolve all linkage requirements, run it, get a RUN TIME printf "library X isn't linked". No, it's not. OK, back up. Use makefile to compile & link example program that comes with the lib. Run it. Guess what?
-
-
5/ Nope. I specifically turn off the snappy compression, and try "none". Same error msg. OK, LZ compression. Nope, same error msg. Now rebuilding library w debugging symbols and line info and using gdb to step through it.
Show this thread -
6/ WHAT THE EVER LIVING !@#!@ ?!?!? I rebuild the library with a higher debug level, link my test program against it ...AND THIS TIME IT GIVES A LINK ERROR FOR THE MISSING LIBRARY! Everything is built out of bricks made of feces, and they slump and shift in the rain.
Show this thread -
7/ and...it works. So, just to recap: * compile lib X * link my .c w X, it complains AT RUN TIME bc Y isn't present * add Y to the compile / link line * ...same error * compile lib X w debug flags (-O2 removed), and then compile and link app and X, and get link error "need Y"
Show this thread
End of conversation
New conversation -
-
-
Sometimes, it's a rabbit hole. Others times, its a literal tunnel to China. Sometimes, I sit and fantasize about torturing the makers of autoconf, m4, etc..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.