that's right: printf error (well, I lie a bit. It core dumps bc an exception that tests that the error string is empty fails. But when I add a printf ...)
-
-
Show this thread
-
3/ so OF COURSE I've already added the extra library to the link line, but it doesn't help. ok, now about to fart with LDPATH bc maybe by "not linked" it means ".so not in path"...
Show this thread -
4/ ok, maybe I can modify the program to specify options in the init function that use a compression library that IS linked in? ONWARD
Show this thread -
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 -
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.