All,
After what appeared to be a successful build and install of kdelibs, I moved on to configure kdebindings (I remembered --enable-closure). During the configure with:
trinity_prefix="/opt/trinity" ./configure --prefix=${trinity_prefix} \ --includedir=${trinity_prefix}/include/kde \ --mandir=${trinity_prefix}/share/man \ --infodir=${trinity_prefix}/share/info \ --with-extra-libs=${trinity_prefix}/lib \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=${trinity_prefix}/lib/kdebase-kde3 \ --disable-rpath \ --enable-closure
I received the following error:
<snip> checking for rpath... no checking for KDE... libraries /opt/trinity/lib, headers /opt/trinity/include checking if UIC has KDE plugins available... no configure: error: you need to install kdelibs first.
If you did install kdelibs, then the Qt version that is picked up by this configure is not the same version you used to compile kdelibs. The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the _same Qt version_, compiled with the _same compiler_ and the same Qt configuration settings.
Aborting...
Huh? I did install kdelibs, and I didn't do anything (that I know of) to have it use some other Qt, so I'm a bit stumped. I did install kdelibs as trinity-kdelibs (if that matters - I'll check the provides() line), but the package is installed:
00:33 archangel:/dat_e/david/bld/trinity/kdelibs/pkg> pacman -Q trinity-kdelibs trinity-kdelibs 1218332-1.0
The full file list for the package is here:
http://www.3111skyline.com/dl/dt/trinity/filelists/kdelibs-filelist.txt
Any idea of what file isn't being located when UIC is checking for KDE plugins? At least that way I can look and see if I have what it needs. Thanks.
On Feb 2, 2011, at 1:47, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
All,
After what appeared to be a successful build and install of kdelibs, I moved on to configure kdebindings (I remembered --enable-closure). During the configure with:
trinity_prefix="/opt/trinity" ./configure --prefix=${trinity_prefix} \ --includedir=${trinity_prefix}/include/kde \ --mandir=${trinity_prefix}/share/man \ --infodir=${trinity_prefix}/share/info \ --with-extra-libs=${trinity_prefix}/lib \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=${trinity_prefix}/lib/kdebase-kde3 \ --disable-rpath \ --enable-closure
I received the following error:
<snip> checking for rpath... no checking for KDE... libraries /opt/trinity/lib, headers /opt/trinity/include checking if UIC has KDE plugins available... no configure: error: you need to install kdelibs first.
If you did install kdelibs, then the Qt version that is picked up by this configure is not the same version you used to compile kdelibs. The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the _same Qt version_, compiled with the _same compiler_ and the same Qt configuration settings.
Aborting...
Huh? I did install kdelibs, and I didn't do anything (that I know of) to have it use some other Qt, so I'm a bit stumped. I did install kdelibs as trinity-kdelibs (if that matters - I'll check the provides() line), but the package is installed:
00:33 archangel:/dat_e/david/bld/trinity/kdelibs/pkg> pacman -Q trinity-kdelibs trinity-kdelibs 1218332-1.0
The full file list for the package is here:
http://www.3111skyline.com/dl/dt/trinity/filelists/kdelibs-filelist.txt
Any idea of what file isn't being located when UIC is checking for KDE plugins? At least that way I can look and see if I have what it needs. Thanks.
If I recall correctly (which i usually don't ;P), kdebindings is no longer required.
This error usually pops up when you don't have autoconf <= 2.63 anyway. Idk if there are cmake scripts for it, I'll have to check svn.
On 02/02/2011 01:07 AM, Robert Xu wrote:
If I recall correctly (which i usually don't ;P), kdebindings is no longer required.
This error usually pops up when you don't have autoconf <= 2.63 anyway. Idk if there are cmake scripts for it, I'll have to check svn.
I read that it might not be required in the README, but according to http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild, it was the next in the build order. There is a cmake directory in kdebindings, but no CMakeLists.txt. So I'm not sure what state it is in. Let me know if we can just skip it and I'll drop a note on the wiki.
On Wednesday 02 February 2011 17:06:35 David C. Rankin wrote:
On 02/02/2011 01:07 AM, Robert Xu wrote:
If I recall correctly (which i usually don't ;P), kdebindings is no longer required.
This error usually pops up when you don't have autoconf <= 2.63 anyway. Idk if there are cmake scripts for it, I'll have to check svn.
I read that it might not be required in the README, but according to http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild, it was the next in the build order. There is a cmake directory in kdebindings, but no CMakeLists.txt. So I'm not sure what state it is in. Let me know if we can just skip it and I'll drop a note on the wiki.
There is no cmake port for kdebindings, yet. kdebindings is not required for a functional Trinity environment.
On 02/02/2011 09:11 AM, Serghei Amelian wrote:
There is no cmake port for kdebindings, yet. kdebindings is not required for a functional Trinity environment.
Thank you Serghei :)
I tried to update the HowToBuild wiki to drop the note but I'm "Access Denied". I sent Tim an email regarding the same.
On 02/02/2011 01:07 AM, Robert Xu wrote:
If I recall correctly (which i usually don't ;P), kdebindings is no longer required.
This error usually pops up when you don't have autoconf <= 2.63 anyway. Idk if there are cmake scripts for it, I'll have to check svn.
Robert,
Here is the part of my configure script that is failing. "kde_cv_tqt=no" is set causing the ./configure to fail. I've looked at ac_fn_cxx_try_link(), but it is pretty much Greek to me :( The configure script that was generated is available here if you want to look:
http://www.3111skyline.com/dl/dt/trinity/errors/configure-kdebindings.bz2
The details of where the error is generated is here:
_ACEOF if ac_fn_cxx_try_link "$LINENO"; then : eval "kde_cv_tqt=no" else eval "kde_cv_tqt=yes" fi rm -f core conftest.err conftest.$ac_objext \ conftest$ac_exeext conftest.$ac_ext fi LIBS="$ac_save_LIBS" CXXFLAGS="$ac_save_CXXFLAGS" ac_ext=c ac_cpp='$CPP $CPPFLAGS' ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' ac_compiler_gnu=$ac_cv_c_compiler_gnu
fi
if eval "test ! "`echo $kde_cv_tqt`" = no"; then { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 $as_echo "no" >&6; } { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!" >&5 $as_echo "$as_me: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again!" >&2;} TQTMOC="$PATH=$PATH:$(srcdir)/ moc-tqt" LIBTQT_LDFLAGS="-ltqt"
qtlib="$qtlib $LIBTQT_LDFLAGS" else
Thanks.
-
David C. Rankin -
Robert Xu -
Serghei Amelian