Thanks for the suggestion, but changing the order dint work either, putting the cryptographic library "before" gives thousands of other linker errors, so I had to put it "after". Tried both combinations for the other ones, but dint work :(
On Oct 23, 11:15 pm, Robert Roessler <[EMAIL PROTECTED]> wrote: > Cyptmon wrote: > > I looked into the symbols for a few of the libraries, I havent checked > > for all the missing symbols but whatever of the missing symbols i > > searched for are there in the libraries included. > > > I dont know why this is not working, it works fine for compiling even > > the SPEC benchmarks and they run fine > > Hey - I can have vague ideas too! ;) I know that the Linux linker often > drives me crazy - one of the issues can come from the specific ordering > of the object files and libraries as they are presented to ld... I don't > remember its particular demands in this area, but some linkers insist on > seeing libs BEFORE references to contained globals, while others are > just the reverse, making sure the libs are presented AFTER the globals > they are intended to resolve are already known to be "wanted". > > Robert Roessler > [EMAIL PROTECTED]://www.rftp.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
