I've been struggling a bit with building kdeadmin-3.5.13.
First the instructions on the HowToBuild page are a bit confusing:
1. Regenerate Autoconf/Automake files cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh make -f admin/Makefile.common
Why the -R in the cp command? -R, -r, --recursive all mean the same thing, but are not really meaningful if the source is a file and not a directory. I'm not sure the permissions are meaningful either. I'd just use --verbose.
2. Configure and Build
./configure --prefix=${PREFIX} --sysconfdir=${SYSCONFDIR} \ --libdir=${LIBDIR} make
This is where I get into problems. I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
-- Bruce
On Wed, 21 Dec 2011 22:51:28 -0600 Bruce Dubbs bruce.dubbs@gmail.com wrote:
I've been struggling a bit with building kdeadmin-3.5.13.
First the instructions on the HowToBuild page are a bit confusing:
- Regenerate Autoconf/Automake files
cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh make -f admin/Makefile.common
Why the -R in the cp command? -R, -r, --recursive all mean the same thing, but are not really meaningful if the source is a file and not a directory. I'm not sure the permissions are meaningful either. I'd just use --verbose.
- Configure and Build
./configure --prefix=${PREFIX} --sysconfdir=${SYSCONFDIR} \ --libdir=${LIBDIR} make
This is where I get into problems. I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
Yes, you forgot the --enable-closure option of ./configure that is mentioned as "undocumented but necessary" at http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild . Without it kdeadmin-3.5.10 doesn't build on Trinity without the same hacks as yours either.
-- Bruce
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
/dev/ammo42 wrote:
On Wed, 21 Dec 2011 22:51:28 -0600 Bruce Dubbs bruce.dubbs@gmail.com wrote:
I've been struggling a bit with building kdeadmin-3.5.13.
I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
Yes, you forgot the --enable-closure option of ./configure that is mentioned as "undocumented but necessary" at http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild . Without it kdeadmin-3.5.10 doesn't build on Trinity without the same hacks as yours either.
When I do:
./configure --prefix=/opt/trinity --enable-closure
I get: ... Detected TQt4... ... configure: error: Qt (>= Qt 4.3 and < 5.0) (headers and libraries) not found. Please check your installation!
--enable-closure adjusts KDE_USE_CLOSURE_TRUE, KDE_USE_CLOSURE_FALSE and KDE_NO_UNDEFINED. The first two are not used in kdeadmin. The third sets the linker to "-Wl,--no-undefined -Wl,--allow-shlib-undefined". That fixes the need to use LDFLAGS, but it doesn't help detect dcopidl2cpp and dcopidl2cpp.
So:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity --enable-closure make TQTDCOPIDL=dcopidl2cpp TQTDCOPIDL2CPP=dcopidl2cpp
now works. I suppose I could use: export CPLUS_INCLUDE_PATH='/opt/trinity/include/tqt' ./configure --prefix=/opt/trinity --enable-closure as an alternative to CPPFLAGS.
And yes, the instructions for 3.5.10 worked fine without hacks:
http://www.linuxfromscratch.org/blfs/view/svn/kde/kdeadmin.html
-- Bruce
Sorry for top posting. This is where I get stuck: you need a lower autoconf version :( (<2.64)
On Dec 22, 2011, at 1:44, Bruce Dubbs bruce.dubbs@gmail.com wrote:
/dev/ammo42 wrote:
On Wed, 21 Dec 2011 22:51:28 -0600 Bruce Dubbs bruce.dubbs@gmail.com wrote:
I've been struggling a bit with building kdeadmin-3.5.13.
I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
Yes, you forgot the --enable-closure option of ./configure that is mentioned as "undocumented but necessary" at http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild . Without it kdeadmin-3.5.10 doesn't build on Trinity without the same hacks as yours either.
When I do:
./configure --prefix=/opt/trinity --enable-closure
I get: ... Detected TQt4... ... configure: error: Qt (>= Qt 4.3 and < 5.0) (headers and libraries) not found. Please check your installation!
--enable-closure adjusts KDE_USE_CLOSURE_TRUE, KDE_USE_CLOSURE_FALSE and KDE_NO_UNDEFINED. The first two are not used in kdeadmin. The third sets the linker to "-Wl,--no-undefined -Wl,--allow-shlib-undefined". That fixes the need to use LDFLAGS, but it doesn't help detect dcopidl2cpp and dcopidl2cpp.
So:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity --enable-closure make TQTDCOPIDL=dcopidl2cpp TQTDCOPIDL2CPP=dcopidl2cpp
now works. I suppose I could use: export CPLUS_INCLUDE_PATH='/opt/trinity/include/tqt' ./configure --prefix=/opt/trinity --enable-closure as an alternative to CPPFLAGS.
And yes, the instructions for 3.5.10 worked fine without hacks:
http://www.linuxfromscratch.org/blfs/view/svn/kde/kdeadmin.html
-- Bruce
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
2011/12/22 Robert Xu robxu9@gmail.com:
Sorry for top posting. This is where I get stuck: you need a lower autoconf version :( (<2.64)
Had the same error. Resolved like this: This gets defined in admin/cvs.sh You need to add your current autoconf version to the autoconf version detection line (line 35) it's a normal bash case statement so it shouldnt be pretty hard. Changing it to
Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* | autoconf*2.7* ) : ;;
Should work
Same goes with autoheader if you need to (line 50).
Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* | autoheader*2.7* ) : ;;
On Thu, Dec 22, 2011 at 07:04, L0ner sh4dou sh4dou@gmail.com wrote:
2011/12/22 Robert Xu robxu9@gmail.com:
Sorry for top posting. This is where I get stuck: you need a lower autoconf version :( (<2.64)
Had the same error. Resolved like this: This gets defined in admin/cvs.sh You need to add your current autoconf version to the autoconf version detection line (line 35) it's a normal bash case statement so it shouldnt be pretty hard. Changing it to
Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* | autoconf*2.7* ) : ;;
Should work
Same goes with autoheader if you need to (line 50).
Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* | autoheader*2.7* ) : ;;
Wasn't this tried before and it failed? I thought this was one reason we moved to cmake... (/me doesn't remember)
2011/12/22 Robert Xu robxu9@gmail.com:
On Thu, Dec 22, 2011 at 07:04, L0ner sh4dou sh4dou@gmail.com wrote:
2011/12/22 Robert Xu robxu9@gmail.com:
Sorry for top posting. This is where I get stuck: you need a lower autoconf version :( (<2.64)
Had the same error. Resolved like this: This gets defined in admin/cvs.sh You need to add your current autoconf version to the autoconf version detection line (line 35) it's a normal bash case statement so it shouldnt be pretty hard. Changing it to
Autoconf*2.5* | autoconf*2.5* | autoconf*2.6* | autoconf*2.7* ) : ;;
Should work
Same goes with autoheader if you need to (line 50).
Autoconf*2.5* | autoheader*2.5* | autoheader*2.6* | autoheader*2.7* ) : ;;
Wasn't this tried before and it failed? I thought this was one reason we moved to cmake... (/me doesn't remember)
Well, for me it worked without any problems. And I understood we move to cmake because autotools beisde being quirky, have a really complicated configuration structure...
-- later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu
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
On Thursday 22 December 2011 01:44:03 am Bruce Dubbs wrote:
/dev/ammo42 wrote:
On Wed, 21 Dec 2011 22:51:28 -0600
Bruce Dubbs bruce.dubbs@gmail.com wrote:
I've been struggling a bit with building kdeadmin-3.5.13.
I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
Yes, you forgot the --enable-closure option of ./configure that is mentioned as "undocumented but necessary" at http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild . Without it kdeadmin-3.5.10 doesn't build on Trinity without the same hacks as yours either.
When I do:
./configure --prefix=/opt/trinity --enable-closure
I get: ... Detected TQt4... ... configure: error: Qt (>= Qt 4.3 and < 5.0) (headers and libraries) not found. Please check your installation!
--enable-closure adjusts KDE_USE_CLOSURE_TRUE, KDE_USE_CLOSURE_FALSE and KDE_NO_UNDEFINED. The first two are not used in kdeadmin. The third sets the linker to "-Wl,--no-undefined -Wl,--allow-shlib-undefined". That fixes the need to use LDFLAGS, but it doesn't help detect dcopidl2cpp and dcopidl2cpp.
So:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity --enable-closure make TQTDCOPIDL=dcopidl2cpp TQTDCOPIDL2CPP=dcopidl2cpp
now works. I suppose I could use: export CPLUS_INCLUDE_PATH='/opt/trinity/include/tqt' ./configure --prefix=/opt/trinity --enable-closure as an alternative to CPPFLAGS.
And yes, the instructions for 3.5.10 worked fine without hacks:
http://www.linuxfromscratch.org/blfs/view/svn/kde/kdeadmin.html
-- Bruce
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
This works for me if I have qt3 installed as in BLFS. When I move qt3 to /usr/local I get the same trouble as you do. I hope you can find a solution to this. I heave been struggling with to autotool builds as well.
cp -f "/usr/share/aclocal/libtool.m4" "admin/libtool.m4.in" cp -f "/usr/share/libtool/config/ltmain.sh" "admin/ltmain.sh" make -f "Makefile.cvs" ./configure prefix=${_prefix} \ --sysconfdir=/etc \ --libdir=${_libdir} \ --mandir=${_mandir} \ --docdir=${_docdir} \ --with-qt-dir=${QTDIR} \ --with-qt-includes=${QTDIR}/include \ --with-qt-libraries=${QTDIR}/lib \ --disable-dependency-tracking \ --enable-closure \ --disable-rpath make
2011/12/22 Bruce Dubbs bruce.dubbs@gmail.com:
/dev/ammo42 wrote:
On Wed, 21 Dec 2011 22:51:28 -0600 Bruce Dubbs bruce.dubbs@gmail.com wrote:
I've been struggling a bit with building kdeadmin-3.5.13.
I have qt in /opt/qt and Trinity base in /opt/trinity. Configure fails to find tqt and then thinks it's version 4. It doesn't find qt and fails. This can be overcome with:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity ...
The --with-qt-includes option does not solve the problem, but the CPPFLAGS can be either before or after ./configure.
Environment variables are:
PATH=/opt/trinity/bin:/usr/local/bin:/bin:/usr/bin:\ /opt/texlive/2011/bin/x86_64-linux:\ /opt/llvm/bin:/opt/qt/bin:/opt/xorg/bin:/sbin:/usr/sbin
PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:\ /usr/local/lib/pkgconfig:\ /opt/qt/lib/pkgconfig:\ /opt/xorg/lib/pkgconfig:\ /opt/xorg/share/pkgconfig
QTDIR=/opt/qt
Then the make fails in several places. What I finally found that works is:
make LDFLAGS='-lqt -lkdecore' \ TQTDCOPIDL=dcopidl2cpp \ TQTDCOPIDL2CPP=dcopidl2cpp
This again tells me that configure didn't do it's job. In the Makefile, both TQTDCOPIDL and TQTDCOPIDL2CPP are blank. The LIB_KDECORE variable is set correctly but is not used. LIBTQT_LDFLAGS is set to -ltqt, but that doesn't do the job.
There are two programs in /opt/trinity/bin: dcopidl2cpp-tqt and dcopidl-tqt, but they do not work with the input in the Makefile.
I did not have any of these problems in KDE3. Is there something I'm missing here?
Yes, you forgot the --enable-closure option of ./configure that is mentioned as "undocumented but necessary" at http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild . Without it kdeadmin-3.5.10 doesn't build on Trinity without the same hacks as yours either.
When I do:
./configure --prefix=/opt/trinity --enable-closure
I get: ... Detected TQt4... ... configure: error: Qt (>= Qt 4.3 and < 5.0) (headers and libraries) not found. Please check your installation!
--enable-closure adjusts KDE_USE_CLOSURE_TRUE, KDE_USE_CLOSURE_FALSE and KDE_NO_UNDEFINED. The first two are not used in kdeadmin. The third sets the linker to "-Wl,--no-undefined -Wl,--allow-shlib-undefined". That fixes the need to use LDFLAGS, but it doesn't help detect dcopidl2cpp and dcopidl2cpp.
So:
CPPFLAGS='-I/opt/trinity/include/tqt' \ ./configure --prefix=/opt/trinity --enable-closure make TQTDCOPIDL=dcopidl2cpp TQTDCOPIDL2CPP=dcopidl2cpp
now works. I suppose I could use: export CPLUS_INCLUDE_PATH='/opt/trinity/include/tqt' ./configure --prefix=/opt/trinity --enable-closure as an alternative to CPPFLAGS.
And yes, the instructions for 3.5.10 worked fine without hacks:
http://www.linuxfromscratch.org/blfs/view/svn/kde/kdeadmin.html
1) Did you install TQtinterface in /usr? I had the same error, and apparentely autotools will refuse to detect it correctly if it's not installed in /usr. 2) Try specifying manually paths to Qt3 in your ./configure (--with-qt-dir= option if I remember correctly).
For building trinity, check out arch PKGBUILDs in our git tree. They are pretty much bash scripts with some variables used by pacman to create binary packages. What you need to look at is the build() function.
L0ner sh4dou wrote:
- Did you install TQtinterface in /usr?
No, in /opt/trinity.
I had the same error, and apparently autotools will refuse to detect it correctly if it's not installed in /usr.
- Try specifying manually paths to Qt3 in your ./configure
(--with-qt-dir= option if I remember correctly).
I already tried that. It does not work for me.
For building trinity, check out arch PKGBUILDs in our git tree. They are pretty much bash scripts with some variables used by pacman to create binary packages. What you need to look at is the build() function.
Is there a way to browse the git tree via a web interface?
After some more research, the following works for me:
--------- TRINITY_PREFIX=/opt/trinity
cp -v /usr/share/aclocal/libtool.m4 admin/libtool.m4.in cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \ admin/acinclude.m4.in
make -f admin/Makefile.common
./configure --prefix=$TRINITY_PREFIX \ --enable-closure \ --sysconfdir=/etc \ --localstatedir=/var \ --with-extra-libs=$TRINITY_PREFIX/lib
make ---------
admin/acinclude.m4.in hard codes /usr/include/tqt instead of getting it from tqt.pc, which is set up correctly on my system. It also does not set up the Trinity libraries correctly, even though it could be determined from either the PATH or --prefix.
Note that I could not detect any effect for --sysconfdir or --localstatedir for kdeadmin.
-- Bruce
2011/12/22 Bruce Dubbs bruce.dubbs@gmail.com:
L0ner sh4dou wrote:
- Did you install TQtinterface in /usr?
No, in /opt/trinity.
It's wrote in the wiki you that you need to install it in the /usr. It helped me to bulit things with autotools on arch.
I had the same error, and apparently autotools will refuse to detect it correctly if it's not installed in /usr.
- Try specifying manually paths to Qt3 in your ./configure
(--with-qt-dir= option if I remember correctly).
I already tried that. It does not work for me.
For building trinity, check out arch PKGBUILDs in our git tree. They are pretty much bash scripts with some variables used by pacman to create binary packages. What you need to look at is the build() function.
Is there a way to browse the git tree via a web interface?
Yes. http://git.trinitydesktop.org/cgit/tde/tree/
After some more research, the following works for me:
TRINITY_PREFIX=/opt/trinity
cp -v /usr/share/aclocal/libtool.m4 admin/libtool.m4.in cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \ admin/acinclude.m4.in
make -f admin/Makefile.common
./configure --prefix=$TRINITY_PREFIX \ --enable-closure \ --sysconfdir=/etc \ --localstatedir=/var \ --with-extra-libs=$TRINITY_PREFIX/lib
make
admin/acinclude.m4.in hard codes /usr/include/tqt instead of getting it from tqt.pc, which is set up correctly on my system. It also does not set up the Trinity libraries correctly, even though it could be determined from either the PATH or --prefix.
Note that I could not detect any effect for --sysconfdir or --localstatedir for kdeadmin.
Resolved?
-- Bruce
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
L0ner sh4dou wrote:
2011/12/22 Bruce Dubbs bruce.dubbs@gmail.com:
L0ner sh4dou wrote:
- Did you install TQtinterface in /usr?
No, in /opt/trinity.
It's wrote in the wiki you that you need to install it in the /usr. It helped me to bulit things with autotools on arch.
I think it's a mistake to force the location of a package. The issues are really the path for programs, headers, and libraries. The pkg-config files are designed to help with that along with a few environment variables: PATH, LD_LIBRARY_PATH (or ld.so.conf), and PKG_CONFIG_PATH.
Other variables that really shouldn't be necessary are LIBRARY_PATH, C_INCLUDE_PATH, and CPLUS_INCLUDE_PATH that are explicitly for gcc. I don't recall ever having to use these before I started looking at Trinity.
Perhaps the biggest problem I have is that I do not have Xorg in /usr (although there is a symlink form /usr/X11R6 to /opt/xorg). I build it in /opt for the same reason you build Trinity in /opt, but there doesn't seem to be an easy way to account for that.
For building trinity, check out arch PKGBUILDs in our git tree. They are pretty much bash scripts with some variables used by pacman to create binary packages. What you need to look at is the build() function.
Is there a way to browse the git tree via a web interface?
It took me a while to find the PKGBUILD files. It's interesting how close they are to what I came up with on my own, but they are very helpful.
One of the problems I have is the prerequsites for many packages. You interface with some of the older libraries. For example, we just removed xmms from BLFS because it only supports GTK1 and we decided that two versions (gtk2 and gtk3) were enough for us. The most recent commit to gtk1 is 2003.
After some more research, the following works for me:
TRINITY_PREFIX=/opt/trinity
cp -v /usr/share/aclocal/libtool.m4 admin/libtool.m4.in cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \ admin/acinclude.m4.in
make -f admin/Makefile.common
./configure --prefix=$TRINITY_PREFIX \ --enable-closure \ --sysconfdir=/etc \ --localstatedir=/var \ --with-extra-libs=$TRINITY_PREFIX/lib
make
admin/acinclude.m4.in hard codes /usr/include/tqt instead of getting it from tqt.pc, which is set up correctly on my system. It also does not set up the Trinity libraries correctly, even though it could be determined from either the PATH or --prefix.
Note that I could not detect any effect for --sysconfdir or --localstatedir for kdeadmin.
Resolved?
The fix to admin/acinclude.m4 is the sed above.
I don't think the comment about --sysconfdir and --localstatedir for kdeadmin is an issue, I just don't think they are used in that package, and indeed, they are not set in the kdeadmin PKGBUILD file.
-- Bruce
2011/12/23 Bruce Dubbs bruce.dubbs@gmail.com:
L0ner sh4dou wrote:
2011/12/22 Bruce Dubbs bruce.dubbs@gmail.com:
L0ner sh4dou wrote:
- Did you install TQtinterface in /usr?
No, in /opt/trinity.
It's wrote in the wiki you that you need to install it in the /usr. It helped me to bulit things with autotools on arch.
I think it's a mistake to force the location of a package. The issues are really the path for programs, headers, and libraries. The pkg-config files are designed to help with that along with a few environment variables: PATH, LD_LIBRARY_PATH (or ld.so.conf), and PKG_CONFIG_PATH.
I think so too, but we needed to do this because of autotools. If you'd go through autotools config files and fix the hardcoded paths there and send a patch to bugzilla you'd help a lot. Besides we wont force anything when the port to cmake is finished.
Other variables that really shouldn't be necessary are LIBRARY_PATH, C_INCLUDE_PATH, and CPLUS_INCLUDE_PATH that are explicitly for gcc. I don't recall ever having to use these before I started looking at Trinity.
Perhaps the biggest problem I have is that I do not have Xorg in /usr (although there is a symlink form /usr/X11R6 to /opt/xorg). I build it in /opt for the same reason you build Trinity in /opt, but there doesn't seem to be an easy way to account for that.
For building trinity, check out arch PKGBUILDs in our git tree. They are pretty much bash scripts with some variables used by pacman to create binary packages. What you need to look at is the build() function.
Is there a way to browse the git tree via a web interface?
It took me a while to find the PKGBUILD files. It's interesting how close they are to what I came up with on my own, but they are very helpful.
One of the problems I have is the prerequsites for many packages. You interface with some of the older libraries. For example, we just removed xmms from BLFS because it only supports GTK1 and we decided that two versions (gtk2 and gtk3) were enough for us. The most recent commit to gtk1 is 2003.
Well, those are mainly for building binaries that will be provided through kdemod3 repo. We decided to build them with everything. We provide those PKGBUILDs for those who want to cusiomize. Our dependencies are based on what is availble for arch, both in binary repo and in aur.
After some more research, the following works for me:
TRINITY_PREFIX=/opt/trinity
cp -v /usr/share/aclocal/libtool.m4 admin/libtool.m4.in cp -v /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \ admin/acinclude.m4.in
make -f admin/Makefile.common
./configure --prefix=$TRINITY_PREFIX \ --enable-closure \ --sysconfdir=/etc \ --localstatedir=/var \ --with-extra-libs=$TRINITY_PREFIX/lib
make
admin/acinclude.m4.in hard codes /usr/include/tqt instead of getting it from tqt.pc, which is set up correctly on my system. It also does not set up the Trinity libraries correctly, even though it could be determined from either the PATH or --prefix.
Note that I could not detect any effect for --sysconfdir or --localstatedir for kdeadmin.
Resolved?
The fix to admin/acinclude.m4 is the sed above.
Send patch to bugzilla, when git move will be it will be applied to the git tree.
I don't think the comment about --sysconfdir and --localstatedir for kdeadmin is an issue, I just don't think they are used in that package, and indeed, they are not set in the kdeadmin PKGBUILD file.
--sysconfdir (for what I understood) is to specify where is your /etc dir in case you have it somewhere else. I remember that there was project kde4win, maybe it was for it?
-- Bruce
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
L0ner sh4dou wrote:
2011/12/23 Bruce Dubbs bruce.dubbs@gmail.com:
One of the problems I have is the prerequsites for many packages. You interface with some of the older libraries. For example, we just removed xmms from BLFS because it only supports GTK1 and we decided that two versions (gtk2 and gtk3) were enough for us. The most recent commit to gtk1 is 2003.
Well, those are mainly for building binaries that will be provided through kdemod3 repo. We decided to build them with everything. We provide those PKGBUILDs for those who want to cusiomize. Our dependencies are based on what is availble for arch, both in binary repo and in aur.
I'm sorry if I implied that you should change anything here. Prerequisites are MY problem, not yours. I was just mentioning it.
sed -i -e "s@/usr/include/tqt@$TRINITY_PREFIX/include/tqt@" \ admin/acinclude.m4.in
Resolved?
The fix to admin/acinclude.m4 is the sed above.
Send patch to bugzilla, when git move will be it will be applied to the git tree.
I don't use git very much. It's on my TODO list, but a little down the list. I'm not sure my fix would be appropriate for you as $TRINITY_PREFIX is our construct. I think what really needs to happen is to get the tqt library info from tqt.pc. Additionally my understanding is that acinclude.m4.in will be overcome by events when you convert to cmake.
On the matter of bugzilla, may I suggest you take a look at Trac (http://trac.edgewall.org/). It has some very nice project tracking features and now integrates with github. I've found it much more powerful than bugzilla and it can import bugzilla data. That way you could try it out before making a final decision.
-- Bruce
-
/dev/ammo42 -
Baho Utot -
Bruce Dubbs -
L0ner sh4dou -
Robert Xu