Slackware 13.1
Previously built kdebindings without this error. I don't know what is different this time around.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdebindings-3.5.13-i486-...
The log also says the following:
Detected TQt3... ... checking if TQt is available... no configure: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!
tqtinterface is installed.
I don't know what this error messages keys on, but the phrase "Please install libtqtinterface-dev and try again!" seems Debian specific.
Need help. :)
Darrell
Le Fri, 11 Nov 2011 14:39:26 -0800 (PST), Darrell Anderson humanreadable@yahoo.com a écrit :
Slackware 13.1
Previously built kdebindings without this error. I don't know what is different this time around.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdebindings-3.5.13-i486-...
autotools forgot to use the tqt include path.
The log also says the following:
Detected TQt3... ... checking if TQt is available... no configure: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!
I already had the same configure messages when tried to build Trinity packages with autotools… IIRC it means that even if configure works the Makefile will forget the tqt include dir and every library need to link the executables. You could always find the "-l..." flags yourself but you will probably have to find the libraries associated to missing symbols with a big grep hammer in /usr/lib; also the produced executables and libraries will probably have unneeded library dependencies, and if you use -Wl,--as-needed to circumvent this it is likely to break libraries in some nasty ways.
tqtinterface is installed.
I don't know what this error messages keys on, but the phrase "Please install libtqtinterface-dev and try again!" seems Debian specific.
Need help. :)
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Slackware 13.1
Previously built kdebindings without this error. I
don't know what is
different this time around.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdebindings-3.5.13-i486-...
autotools forgot to use the tqt include path.
The log also says the following:
Detected TQt3... ... checking if TQt is available... no configure: WARNING: You are attempting to compile
Trinity without the
Trinity Qt Interface installed. Please install
libtqtinterface-dev
and try again!
I already had the same configure messages when tried to build Trinity packages with autotools… IIRC it means that even if configure works the Makefile will forget the tqt include dir and every library need to link the executables. You could always find the "-l..." flags yourself but you will probably have to find the libraries associated to missing symbols with a big grep hammer in /usr/lib; also the produced executables and libraries will probably have unneeded library dependencies, and if you use -Wl,--as-needed to circumvent this it is likely to break libraries in some nasty ways.
I don't know whether this error message is related to the embedviewimp.h error. Somebody else will have to respond. All I know is I am, stuck right now building kdebindings. I don't know why this is now happening and previously did not.
tqtinterface is installed.
I don't know what this error messages keys on, but the
phrase "Please
install libtqtinterface-dev and try again!" seems
Debian specific.
Need help. :)
Darrell
Slackware 13.1
Previously built kdebindings without this error. I don't know what is different this time around.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdebindings-3.5.13-i486-...
The log also says the following:
Detected TQt3... ... checking if TQt is available... no configure: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!
tqtinterface is installed.
I don't know what this error messages keys on, but the phrase "Please install libtqtinterface-dev and try again!" seems Debian specific.
Need help. :)
I don't know what's happening, but I discovered when I build and install tqtinterface to my normal $PREFIX of /opt/trinity that kdebindings will fail to build. When I build and install tqtinterface to /usr then kdebindings builds without the aforementioned failure.
Thus the "configure: WARNING" might be a valid error. Is there something in tqtinterface that requires installing to /usr or something in kdebindings that is hard-coded only to look for something tqt related in /usr?
Tim?
Darrell
Slackware 13.1
Previously built kdebindings without this error. I don't know what is different this time around.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdebindings-3.5.13-i486-...
The log also says the following:
Detected TQt3... ... checking if TQt is available... no configure: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!
tqtinterface is installed.
I don't know what this error messages keys on, but the phrase "Please install libtqtinterface-dev and try again!" seems Debian specific.
Need help. :)
I don't know what's happening, but I discovered when I build and install tqtinterface to my normal $PREFIX of /opt/trinity that kdebindings will fail to build. When I build and install tqtinterface to /usr then kdebindings builds without the aforementioned failure.
Thus the "configure: WARNING" might be a valid error. Is there something in tqtinterface that requires installing to /usr or something in kdebindings that is hard-coded only to look for something tqt related in /usr?
Tim?
Yes there is, as a bit of a hack all TDE Autotools-based packages include /usr/include/tqt in their include search paths.
Yes, this should be revamped. Having someone help create a patch would be a way to make sure it gets in to our next release. ;-)
Tim
I don't know what's happening, but I discovered when I
build and install
tqtinterface to my normal $PREFIX of /opt/trinity that
kdebindings will
fail to build. When I build and install tqtinterface
to /usr then
kdebindings builds without the aforementioned
failure.
Thus the "configure: WARNING" might be a valid error.
Is there something
in tqtinterface that requires installing to /usr or
something in
kdebindings that is hard-coded only to look for
something tqt related in
/usr?
Tim?
Yes there is, as a bit of a hack all TDE Autotools-based packages include /usr/include/tqt in their include search paths.
Yes, this should be revamped. Having someone help create a patch would be a way to make sure it gets in to our next release. ;-)
OK, so tqtinterface 3.5.13 must be installed to /usr. That's important. :)
Should the wiki reflect that? If yes then I'll do so --- if my login info still works.
Darrell
-
/dev/ammo42 -
Darrell Anderson -
Timothy Pearson