g++ -fno-exceptions -shared -o libqsqlite.so .obj/smain.o .obj/qsql_sqlite.o .obj/attach.o .obj/auth.o .obj/btree.o .obj/btree_rb.o .obj/build.o .obj/copy.o .obj/date.o .obj/delete.o .obj/expr.o .obj/func.o .obj/hash.o .obj/insert.o .obj/main.o .obj/opcodes.o .obj/os.o .obj/pager.o .obj/parse.o .obj/pragma.o .obj/printf.o .obj/random.o .obj/select.o .obj/shell.o .obj/table.o .obj/tokenize.o .obj/trigger.o .obj/update.o .obj/util.o .obj/vacuum.o .obj/vdbe.o .obj/vdbeaux.o .obj/where.o -L/usr/lib/mysql -L/var/tmp/portage/qt-3.3.4-r8/work/qt-x11-free-3.3.4/lib -L/usr/X11R6/lib -lqt-mt -lmng -ljpeg -lpng -lz -lXi -lXrender -lXrandr -lXcursor -lXft -lfreetype -lfontconfig -lXext -lX11 -lm -lSM -lICE -ldl -lpthread mv -f libqsqlite.so ../../../sqldrivers/ make[3]: Leaving directory `/var/tmp/portage/qt-3.3.4-r8/work/qt-x11-free-3.3.4/plugins/src/sqldrivers/sqlite' make[2]: Leaving directory `/var/tmp/portage/qt-3.3.4-r8/work/qt-x11-free-3.3.4/plugins/src/sqldrivers' make[1]: *** [sub-sqldrivers] Error 2 make[1]: Leaving directory `/var/tmp/portage/qt-3.3.4-r8/work/qt-x11-free-3.3.4/plugins/src' make: *** [sub-plugins] Error 2 !!! ERROR: x11-libs/qt-3.3.4-r8 failed. !!! Function src_compile, Line 187, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message.
Please provide more output as that does not show the error at all.
Ok, im compiling qt again, i emerge --synced in the meantime, which has had the result that some other things need compiling aswell, however emerge -uN qt seems to want mysql and sqlite to be updated/rebuilt first, which wasnt the case before, maybe this is the cause of the error. I had afterall added the mysql and sqlite useflags. More info to follow, as the compile happens.
compilation is not the problem. what seemed to be the problem is that by adding the sqlite useflag it wanted to emerge qt with sqlite support even thought the emerging of sqlite was schedule for later in that same emerge run.
I think Qt links against it's own internal copy of sqlite and not the portage supplied copy, so I don't think that's a problem.
That would still not explain why it emerged correctly after sqlite had been emerged and not before.
True, but the output you should above doesn't actually show any error, just that there was an error, so it isn't possible to tell you what went wrong.
yeah, i realise that. i am trying to reproduce this when i have free time, but so far i have not been particularly successfull.
closing for now, if i reproduce i will reopen or file again.
