issues with building QMYSQL plugin

SGaist

Hi,

You are likely using the wrong qmake. Use the full path to your Qt 5.8 qmake.

Also since you installed Qt in /opt, your user likely doesn't have the permission to write in that folder.

mzimmers

You are likely using the wrong qmake. Use the full path to your Qt 5.8 qmake.

Aargh...someday, I will remember that you've told me this multiple times.

The correct qmake worked. Now when I run make, I'm getting that compiler flag error. I looked in my Makefile and see this line:

CXXFLAGS      = -pipe -O2 -std=c++1z ...

So, I'm curious...why am I getting this inclusion now? And, what would you recommend I do about it.

Also, about installing Qt into /opt...where is the appropriate location for it when installing on Linux? I'd assume it would go somewhere outside of my userspace, right? So that it could be shared if there were multiple users?

Thanks, SGaist.

SGaist

That's the right place when you want a shared installed.

However, you don't need to build the plugin in-place, you can use an out of source build.

The compiler flags just indicates that it want's to use the latest available standard.

What error are you getting exactly ?

mzimmers

That's pretty much the whole error message on the command line (and in Creator):

g++: error: unrecognized command line option ‘-std=c++1z’

Is there some verbose flag I could set to try to get more information? My g++ is also in /usr/bin if that makes a difference.

SGaist

Which version of gcc is it ?

mzimmers

mzimmers@debian:/opt/Qt/5.8/Src/qtbase/src/plugins/sqldrivers/mysql$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)

Oh, I see...it's using the old version that I keep to do cross builds to my BBB, isn't it? How best to handle when you want to keep multiple versions of something?

jsulm

@mzimmers c++1z is C++17 - your compiler (GCC 4.9) for sure does not support it. You should check the mysql.pro file and change it to c++11.

mzimmers

@jsulm thanks for the reply. I recognize that this flag isn't compatible with my current compiler. Of greater concern to me is: where is this flag coming from? It's not in my .pro file, and none of the other projects I've built using Creator have generated this flag.

I'm looking into upgrading my compiler, but someone on the Debian forum told me that this might not be a good idea, so that's on hold for a bit.

EDIT: OK, it looks like upgrading my compiler without upgrading the version of Debian I'm running is a bad idea. At this point, it seems like it would be the tail wagging the dog anyway. So, I'm back to this question: where is that flag coming from? Does qmake actually parse the code to the point where it might detect that such a flag would be necessary?

Question #2: Sgaist referred to "an out of source build" above. I'm not sure I know what this mean -- does it mean redirecting the output of the build to another directory? If so, is this accomplished with a qmake variable? Because I didn't see one in the documentation that looked like it would alter this.

Thanks.

jsulm

@mzimmers qmake does not parse any source code, it only parses pro files. Can you post that pro file or a link to it? This flag should be in that file. You also should check the output of the qmake command, maybe it gives some hints.
Out of source simply means that you call qmake and make from a directory outside of the source code you're going to build. This way all the build artefacts are not in the source directory - you keep the source code directory clean.

mzimmers

@jsulm here's the project file. I put in the last line myself.

TARGET = qsqlmysql

HEADERS += $$PWD/qsql_mysql_p.h
SOURCES += $$PWD/qsql_mysql.cpp $$PWD/main.cpp

#QMAKE_USE += mysql

OTHER_FILES += mysql.json

PLUGIN_CLASS_NAME = QMYSQLDriverPlugin
include(../qsqldriverbase.pri)

QMAKE_CXXFLAGS -= "-std=c++1z"

I'm still getting this error, though:

/opt/Qt/5.8/Src/qtbase/mkspecs/features/qt_plugin.prf:62: error: Cannot touch /mkspecs/modules/qt_plugin_qsqlmysql.pri: Operation not permitted.

It's trying to write to mkspecs as a root directory. I verified this by running as root; it creates a mkspecs root directory. I think the cause is some undefined symbols, as the lines that form this symbol are:

38    mod_work_pfx = $$MODULE_QMAKE_OUTDIR/mkspecs/modules
44    MODULE_FWD_PRI = $$mod_work_pfx/qt_plugin_$${MODULE}.pri
62            touch($$MODULE_FWD_PRI, $$MODULE_PRI)

Thanks for any assistance.

SGaist

To avoid losing time, just copy the qtbase module sources in you home folder so you don't have that touch problem.

mzimmers

I just tried this; got a few errors. I took care of all but one:

error: Project has no top-level .qmake.conf file.

I still think there's something wrong with my variables or symbols if it was trying to write to the root directory, though.

SGaist

Did you copy the whole qtbase source ?

mzimmers

@SGaist oops...I misread what you said above...sorry. I'm still getting this error, though:

/home/mzimmers/QtStuff/qtbase/mkspecs/features/qt_plugin.prf:62: 
error: Cannot touch /mkspecs/modules/qt_plugin_qsqlmysql.pri: Operation not permitted.

I can try this with root, too, but I'm pretty sure it will indeed write to a directory /mkspecs...it did before.

SGaist

The sources likely have kept their rights. You should call something like sudo chown user:group qtbase -R (replace user and group by your user name and main group).

mzimmers

User and group IDs are already mine. (They are in the original location as well.)

SGaist

Then are the files read-only ?

mzimmers

@SGaist No, not for me:

mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$ pwd
/home/mzimmers/QtStuff/qtbase/src/plugins/sqldrivers/mysql
mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$ ls -l
total 108
-rw-rw-r-- 1 mzimmers mzimmers  2619 Jan 18 09:20 main.cpp
-rw-r--r-- 1 mzimmers mzimmers  8229 Mar 15 20:04 Makefile
-rw-rw-r-- 1 mzimmers mzimmers    40 Jan 18 09:20 mysql.json
-rw-rw-r-- 1 mzimmers mzimmers   250 Mar 15 20:06 mysql.pro
-rw-r--r-- 1 mzimmers mzimmers 23807 Mar 16 17:11 mysql.pro.user
-rw-rw-r-- 1 mzimmers mzimmers 50811 Jan 18 09:20 qsql_mysql.cpp
-rw-rw-r-- 1 mzimmers mzimmers  3952 Jan 18 09:20 qsql_mysql_p.h
-rw-rw-r-- 1 mzimmers mzimmers   204 Jan 18 09:20 README
mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$

SGaist

I just realised there's something fishy with the error message: the path seems to start at the root of the filesystem and doesn't match anything I know from the sources.

Can you try a clean out of source build of the plugin from the console ?

mzimmers

@SGaist I deleted my Makefile and ran the following command:

mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$ /opt/Qt/5.8/gcc_64/bin/qmake "INCLUDEPATH+=/usr/local/include /usr/src/mysql/mysql-5.7.17/include" "LIBS+=-L/usr/lib -lmysqlclient_r" /home/mzimmers/QtStuff/qtbase/src/plugins/sqldrivers/mysql/mysql.pro

Question #1: what is the correct syntax for removing a compiler flag? I tried this:

QMAKE_CXXFLAGS -= "-std=c++1z"

but that didn't work.

I then went in and manually modified the Makefile, changing "-std=c++1z" to "-std=c++11", and ran make. I then encountered this error:

mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$ make
g++ -c -pipe -O2 -std=c++11 -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time -D_REENTRANT -fPIC -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/local/include -I/usr/src/mysql/mysql-5.7.17/include -I/opt/Qt/5.8/gcc_64/include/QtSql/5.8.0 -I/opt/Qt/5.8/gcc_64/include/QtSql/5.8.0/QtSql -I/opt/Qt/5.8/gcc_64/include/QtCore/5.8.0 -I/opt/Qt/5.8/gcc_64/include/QtCore/5.8.0/QtCore -I/opt/Qt/5.8/gcc_64/include -I/opt/Qt/5.8/gcc_64/include/QtSql -I/opt/Qt/5.8/gcc_64/include/QtCore -I.moc -I../../../../mkspecs/linux-g++ -o .obj/qsql_mysql.o qsql_mysql.cpp
In file included from qsql_mysql_p.h:60:0,
                 from qsql_mysql.cpp:40:
/usr/src/mysql/mysql-5.7.17/include/mysql.h:57:27: fatal error: mysql_version.h: No such file or directory
 #include "mysql_version.h"
                           ^
compilation terminated.
Makefile:834: recipe for target '.obj/qsql_mysql.o' failed
make: *** [.obj/qsql_mysql.o] Error 1
mzimmers@debian:~/QtStuff/qtbase/src/plugins/sqldrivers/mysql$

I don't have a file named mysql_version.h. I do have a file named mysql_version.h.in. I'm not familiar with .in files, but according to Wiki, it's input to a program called "autoconf." In reading the documentation, I wonder whether I somehow missed a step in the build that converts this .in file into a .h file. EDIT: I did find a cmake file with that name as well, though there's nothing in the documentation about running cmake manually.

Anyway, we do seem to be moving forward. I would like to resolve this problem with the compiler flag, though.

Thanks for all the help.