tde-devels

devels@trinitydesktop.org

2 participants
3755 discussions

libtqt-perl FTBFS - RENAMING ISSUE qt->tqt causes /usr/bin/ld: cannot find -lsmoketqt

by David C. Rankin

Tim, Darrell, libtqt-perl has a libtool issue where it fails to report its own libraries in the correct location due to what looks to be a qt/tqt renaming issue. Building in a chroot and using the recommended: perl Makefile.PL make make test make install The build fails at: Running Mkbootstrap for TQt () chmod 644 TQt.bs rm -f blib/arch/auto/TQt/TQt.so LD_RUN_PATH="/opt/tqt3/lib:/lib/../lib:/opt/trinity/lib" g++ -shared -Wl,-O1,--sort-common,--as-needed,-z,relro -L/usr/local/lib -fstack-protector TQt.o handlers.o -Wl,--rpath -Wl,/opt/trinity/lib -Wl,--rpath -Wl,/opt/tqt3/lib -o blib/arch/auto/TQt/TQt.so \ -L/opt/tqt3/lib -L/opt/trinity/lib -L/opt/trinity/lib -L/opt/trinity/lib/trinity -lcrypt -ltqt-mt -lpng -lz -lm -lXext -lX11 -lSM -lICE -lpthread -L/build/tde-libtqt-perl/src/libtqt-perl/smoke/qt/.libs -lsmoketqt \ /usr/bin/ld: cannot find -lsmoketqt Now NOTE it is reporting the -lsmoketqt location, but it is wrong due to libtool searching for the lib in smoke/qt/.libs when the directory is now smoke/tqt/.libs: -L/build/tde-libtqt-perl/src/libtqt-perl/smoke/qt/.libs The 'smoke/qt/.libs' should be 'smoke/tqt/.libs' david> l1 build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.* build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.la build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.lai build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.so build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.so.1 build/tde-libtqt-perl/src/libtqt-perl/smoke/tqt/.libs/libsmoketqt.so.1.2.1 I suspect there was an issue with a qt/tqt renaming of the source that is not picked up by autotools. How to fix? I've opened a bug... http://bugs.pearsoncomputing.net/show_bug.cgi?id=1875 -- David C. Rankin, J.D.,P.E.

11 years

tdmtheme FTBFS - tdmtheme.cpp:385:24: fatal error: tdmtheme.moc: No such file or directory

by David C. Rankin

All, The error is correct. There is no tdmtheme.moc anywhere to be found. What is supposed to create the .moc file? I tried every variation of "make" "qmake" etc.. The full error is: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -I/usr/include/tqt -I/usr/include/tqt/Qt -DQT_THREAD_SUPPORT -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c tdmtheme.cpp -fPIC -DPIC -o .libs/tdmtheme.o tdmtheme.cpp:385:24: fatal error: tdmtheme.moc: No such file or directory #include "tdmtheme.moc" -- David C. Rankin, J.D.,P.E.

11 years

Re: [trinity-devel] Difference between: gtk-qt-engine & gtk3-tqt-engine

by Darrell Anderson

> Anybody have both installed currently? Please share your configuration options in your gtk3-tqt-engine build script. I never have been able to build the package. The build always fails with this error: gcc: error: /tde: No such file or directory I believe the problem is in gtk3-tqt-engine/tdegtk/Makefile.am:1 INCLUDES= $(all_includes) $(KDE_INCLUDES)/tde I believe $(KDE_INCLUDES) is never defined. Darrell

11 years

does tderadio work? Strange warning at end of good build

by David C. Rankin

All, Building tderadio, I was surprised to see the following warning: *************** Important ************************* This module contains unreleased software. The software may compile and work, but it may just as well neither compile nor work. **************************************************** Which begs the question - does it work? If you have it installed, please provide your feedback. Thanks. -- David C. Rankin, J.D.,P.E.

11 years

Difference between: gtk-qt-engine & gtk3-tqt-engine

by David C. Rankin

Darrell, All, I have built both gtk-qt-engine & gtk3-tqt-engine packages. I am not sure what should dictate the use or installation of one, or the other, or both? I don't understand the difference. Both are designed to provide similar feel for gtk apps running in TDE, with the former updating gtk-2.0 configs, and I presume the latter does something similar for gtk-3.0 based apps. The confusion is why 2 applications? Why not just extend one, or the other, to cover both gtk-2.0 and gtk-3.0 apps? With 2 apps is there some logic that tells gtk-2 and 3 apps to use the different engines to create different configs on icon-set or widget-style changes? Are there now two configs in thelpcenter? Initially, my first concern was that the packages would conflict. But after building, it is apparent they will not: tde-gtk-qt-engine-14.0.0-1-x86_64.pkg.tar.xz: opt/trinity/share/applications/kcmgtk.desktop opt/trinity/share/locale/de/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/bg/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/fr/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/nn/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/tr/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/es/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/ru/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/sv/LC_MESSAGES/gtkqtengine.mo opt/trinity/share/locale/it/LC_MESSAGES/gtkqtengine.mo opt/trinity/lib/trinity/kcm_kcmgtk.la opt/trinity/lib/trinity/kcm_kcmgtk.so usr/share/themes/Qt/gtk-2.0/gtkrc usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so tde-gtk3-tqt-engine-14.0.0-1-x86_64.pkg.tar.xz: opt/trinity/lib/libtqtcairo.so.0 opt/trinity/lib/libtqtcairo.so.0.0.0 opt/trinity/lib/libtqtcairo.la opt/trinity/lib/libtqtcairo.so usr/share/themes/tdegtk/gtk-3.0/gtk.css usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so.0.0.0 usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so.0 usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.la Anybody have both installed currently? -- David C. Rankin, J.D.,P.E.

11 years

Re: [trinity-devel] adept configure, but make builds nothing, what to check?

by Darrell Anderson

> Building adept. the package builds without error, but results in >an empty package. I'm using a standard autotools build: I thought adept was Debian only. Darrell

11 years

k3b FTBFS - error: invalid use of incomplete type 'mpc_decoder {aka struct mpc_decoder_t}'

by David C. Rankin

All, k3b looks like it needs a lot of work. I vaguely recall fixing numerous out-of-scope issues when gcc 4.7 emerged, but have forgotten the details. Building k3d, the following are a number of errors resulting in the FTBFS. I have summarized the errors themselves below. From the summary it looks like the error: invalid use of incomplete type 'mpc_decoder {aka struct mpc_decoder_t}' at k3bmpcwrapper.cpp:77:28 starts the domino falling. If that could be fixed, then it may resolve a number of the remaining errors. So c++ gurus, "What is the proper way to do that?" Summary of the errors: k3bmpcwrapper.cpp:77:28: error: invalid use of incomplete type 'mpc_decoder /usr/include/mpc/mpcdec.h:55:16: error: forward declaration of 'mpc_decoder k3bmpcwrapper.cpp:88:10: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined k3bmpcwrapper.cpp:101:33: error: 'mpc_streaminfo_init' was not declared in this scope k3bmpcwrapper.cpp:102:47: error: 'mpc_streaminfo_read' was not declared in this scope k3bmpcwrapper.cpp:102:52: error: 'ERROR_CODE_OK' was not declared in this scope k3bmpcwrapper.cpp:107:46: error: 'mpc_decoder_setup' was not declared in this scope k3bmpcwrapper.cpp:108:54: error: 'mpc_decoder_initialize' was not declared in this scope k3bmpcwrapper.cpp:136:77: error: 'mpc_decoder_decode' was not declared in this scope k3bmpcwrapper.cpp:173:78: error: 'mpc_decoder_seek_seconds' was not declared in this scope Errors in context: k3bmpcwrapper.cpp:74:22: warning: invalid conversion from 'mpc_bool_t (*)(void*) {aka unsigned char (*)(void*)}' to 'mpc_bool_t (*)(mpc_reader*) {aka unsigned char (*)(mpc_reader_t*)}' [-fpermissive] m_reader->canseek = canseek_impl; ^ k3bmpcwrapper.cpp:77:28: error: invalid use of incomplete type 'mpc_decoder {aka struct mpc_decoder_t}' m_decoder = new mpc_decoder; ^ In file included from k3bmpcwrapper.h:27:0, from k3bmpcwrapper.cpp:16: /usr/include/mpc/mpcdec.h:55:16: error: forward declaration of 'mpc_decoder {aka struct mpc_decoder_t}' typedef struct mpc_decoder_t mpc_decoder; ^ k3bmpcwrapper.cpp: In destructor 'K3bMpcWrapper::~K3bMpcWrapper()': k3bmpcwrapper.cpp:88:10: warning: possible problem detected in invocation of delete operator: [enabled by default] delete m_decoder; ^ k3bmpcwrapper.cpp:88:10: warning: invalid use of incomplete type 'struct mpc_decoder_t' [enabled by default] In file included from k3bmpcwrapper.h:27:0, from k3bmpcwrapper.cpp:16: /usr/include/mpc/mpcdec.h:55:16: warning: forward declaration of 'struct mpc_decoder_t' [enabled by default] typedef struct mpc_decoder_t mpc_decoder; ^ k3bmpcwrapper.cpp:88:10: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined delete m_decoder; ^ k3bmpcwrapper.cpp: In member function 'bool K3bMpcWrapper::open(const TQString&)': k3bmpcwrapper.cpp:101:33: error: 'mpc_streaminfo_init' was not declared in this scope mpc_streaminfo_init( m_info ); ^ k3bmpcwrapper.cpp:102:47: error: 'mpc_streaminfo_read' was not declared in this scope if( mpc_streaminfo_read( m_info, m_reader ) != ERROR_CODE_OK ) { ^ k3bmpcwrapper.cpp:102:52: error: 'ERROR_CODE_OK' was not declared in this scope if( mpc_streaminfo_read( m_info, m_reader ) != ERROR_CODE_OK ) { ^ k3bmpcwrapper.cpp:107:46: error: 'mpc_decoder_setup' was not declared in this scope mpc_decoder_setup( m_decoder, m_reader ); ^ k3bmpcwrapper.cpp:108:54: error: 'mpc_decoder_initialize' was not declared in this scope if( !mpc_decoder_initialize( m_decoder, m_info ) ) { ^ k3bmpcwrapper.cpp: In member function 'int K3bMpcWrapper::decode(char*, int)': k3bmpcwrapper.cpp:136:77: error: 'mpc_decoder_decode' was not declared in this scope unsigned int samples = mpc_decoder_decode( m_decoder, sample_buffer, 0, 0 ); ^ k3bmpcwrapper.cpp: In member function 'bool K3bMpcWrapper::seek(const K3b::Msf&)': k3bmpcwrapper.cpp:173:78: error: 'mpc_decoder_seek_seconds' was not declared in this scope return mpc_decoder_seek_seconds( m_decoder, (double)msf.totalFrames()/75.0 ); ^ k3bmpcwrapper.cpp: In member function 'bool K3bMpcWrapper::open(const TQString&)': k3bmpcwrapper.cpp:122:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ k3bmpcwrapper.cpp: In member function 'bool K3bMpcWrapper::seek(const K3b::Msf&)': k3bmpcwrapper.cpp:174:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ Makefile:639: recipe for target 'k3bmpcwrapper.lo' failed make[4]: *** [k3bmpcwrapper.lo] Error 1 make[4]: Leaving directory '/build/tde-k3b/src/k3b/plugins/decoder/musepack' Makefile:542: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/build/tde-k3b/src/k3b/plugins/decoder' Makefile:536: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/build/tde-k3b/src/k3b/plugins' Makefile:594: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/build/tde-k3b/src/k3b' Makefile:511: recipe for target 'all' failed make: *** [all] Error 2 -- David C. Rankin, J.D.,P.E.

11 years

Calvin - Arch - need server space for R14 repo (300M per arch) for testing.

by David C. Rankin

Calvin, I need your help finding sever space to host TDE R14 packages for testng. The repos are about 300M per arch (i686/x86_64). I've posted to arch general, but no hits so far. I know you have many more contacts for this than I -- put them to work :-) -- David C. Rankin, J.D.,P.E.

11 years

kchmviewer - configure fails - conditional "include_x11" was never defined

by David C. Rankin

All, kchmviewer fails during configure. The error is a strange conditional definition error in the configure file that I haven't run across before. The error is: chmlib to link : system checking if lib should be compiled... yes checking if po should be compiled... yes checking if src should be compiled... yes checking that generated files are newer than configure... done configure: error: conditional "include_x11" was never defined. Usually this means the macro was only invoked conditionally. From the error it looks like the "include_x11" was used in a conditional but not previously defined (or something like that). If you are familiar with 'configure' define statements, or this error, then please let me know your thoughts on fixing it. I'll begin picking through it in the mean time. -- David C. Rankin, J.D.,P.E.

11 years

adept configure, but make builds nothing, what to check?

by David C. Rankin

All, Building adept. the package builds without error, but results in an empty package. I'm using a standard autotools build: cd ${srcdir} ## Set up environment msg "Setting PATH, Trinity Environment variables" # Source the QT and TDE profile [ "$QTDIR" = "" ] && . /etc/profile.d/tqt3.sh # or qt3.sh [ "$TDEDIR" = "" ] && . /etc/profile.d/trinity.sh # or tde.sh ## Generate config files and update with autoreconf cd "${srcdir}/${pkgname#*-}" msg "Copying system libtool files...." cp /usr/share/aclocal/libtool.m4 ./admin/libtool.m4.in cp /usr/share/libtool/config/ltmain.sh ./admin msg "Running make -f admin/Makefile.common ...." make -f admin/Makefile.common ## configure msg "Configuring - ${pkgname}..." ./configure \ --prefix=${TDEDIR} \ --with-qt-dir=${QTDIR} \ --with-qt-includes=${QTDIR}/include \ --with-qt-libraries=${QTDIR}/lib \ --with-extra-includes="/usr/include/tqt:/usr/include/tqt/Qt" \ --with-extra-libs=${TDEDIR}/lib/trinity \ --sysconfdir=${TDEDIR}/etc \ --localstatedir=/var msg "Building - ${pkgname}..." make $NUMJOBS Then calling: msg "Packaging - $pkgname-$pkgver" cd "${srcdir}/${pkgname#*-}" make -j1 DESTDIR="$pkgdir" install I get no errors, but it is apparent nothing is being compiled after ./configure is done. What should I look for and in what files? The Makefile (or .in or .am.in or in the autom4te.cache files??) Here is the end of ./configure and the build: <snip> config.status: executing depfiles commands config.status: executing libtool commands Good - your configure finished. Start make now ==> Building - tde-adept... make all-recursive make[1]: Entering directory '/build/tde-adept/src/adept' make[2]: Entering directory '/build/tde-adept/src/adept' make[2]: Leaving directory '/build/tde-adept/src/adept' make[1]: Leaving directory '/build/tde-adept/src/adept' ==> Entering fakeroot environment... ==> Starting package()... ==> Packaging - tde-adept-14.0.0 make[1]: Entering directory '/build/tde-adept/src/adept' make[2]: Entering directory '/build/tde-adept/src/adept' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Leaving directory '/build/tde-adept/src/adept' make[1]: Leaving directory '/build/tde-adept/src/adept' Note the dearth of build output.. What to check?? -- David C. Rankin, J.D.,P.E.

11 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels