SQLite and Ubuntu 11.10 64bit

[shane2]

Hello All,

I have a project that I can compile just find on Ubuntu 11.04 64bit. After upgrading to 11.10 64bit, building Poco from scratch, I now get compile errors. It looks like it has to deal with the building of sqlite3 during the Poco build process (although I can build all of Poco without error).

Below is the errors that I get:

Code: Select all

g++ -m64 -pthread -ldl    -o dist/Debug/GNU-Linux-x86/pocosqlitetest build/Debug/GNU-Linux-x86/main.o -L../../poco-1.4.3p1-all/lib/Linux/x86_64 -lPocoDataSQLited -lPocoDatad -lPocoFoundationd
../../poco-1.4.3p1-all/lib/Linux/x86_64/libPocoDataSQLited.a(sqlite3.o): In function `unixDlOpen':
/home/spechacek/poco-1.4.3p1-all/Data/SQLite/src/sqlite3.c:29885: undefined reference to `dlopen'
../../poco-1.4.3p1-all/lib/Linux/x86_64/libPocoDataSQLited.a(sqlite3.o): In function `unixDlError':
/home/spechacek/poco-1.4.3p1-all/Data/SQLite/src/sqlite3.c:29899: undefined reference to `dlerror'
../../poco-1.4.3p1-all/lib/Linux/x86_64/libPocoDataSQLited.a(sqlite3.o): In function `unixDlSym':
/home/spechacek/poco-1.4.3p1-all/Data/SQLite/src/sqlite3.c:29925: undefined reference to `dlsym'
../../poco-1.4.3p1-all/lib/Linux/x86_64/libPocoDataSQLited.a(sqlite3.o): In function `unixDlClose':
/home/spechacek/poco-1.4.3p1-all/Data/SQLite/src/sqlite3.c:29930: undefined reference to `dlclose'
collect2: ld returned 1 exit status


Is there something in the Poco build that needs to be tweaked to allow it to compile properly?

Attached is the Netbeans project that I used to produce this error. This is the example code from the Poco data examples.

Thanks in advance!

Regards,
Shane

[shane2]

Has anyone been able to confirm that there are build issues with using Poco on Ubuntu 11.10 64bit?

I would really like to get this solved soon, otherwise I'll have to ditch using Poco and find something else, which I really do not want to do.

Thanks.

[Royce]

I got a face full of this this weekend. Its not Poco or SQLite specific. Apparently something changed in g++ between 11.04 and 11.10. The new behavior is obnoxious. The way you have it, the system will attempt to locate your library files, and complain if it can't find them, but if it can find the libs it will proceed to NOT search them for your symbols and instead spew reams of undefined symbol messages.

The order that you pass the arguments to g++ is now critical to avoid this. The recipe I have had success with:
include paths (-I),
source code files (.cpp)
outfile name (-o)
linker search directories (-L)
linked library names (-l)

Figuring this out wasted 8+ hours of my life this weekend. I was not amused. If specifying the arguments out of order is such a bad thing, the system should complain about the order of the arguments, not about missing symbols that it never bothered to look for.

[shane2]

Gotta hand it to you Royce, nice work if you were able to get it to work!

I use Netbeans for my IDE and will see if I can replicate your work and post my results. I may have to resort to a manual build if NB doesn't want to do it the way you have suggested.

I haven't tried it yet with Ubuntu 12.04 since it was broke in 11.10 and have since switched to using Fedora 16 64bit (which is odd that it works in Fedora but not Ubuntu...go figure)

Do you know what version of g++ is used in Ubuntu 11.10?

I may have to fire up a 12.04 install and see if the same thing happens or if it is still broke.

Thanks for posting this! Again...kudos to you!