4 Dec
2012
4 Dec
'12
9:10 p.m.
As Slávek said this package is still built with the
autotools.
However when I run the configure script it runs through the script
until it stops when it tries to find tde-config. If I change it to
kde-config (in the configure script which I know should not be
needed)
it tells me that it cannot find the qt-mt library.
Starting with R14, kde-config is renamed to tde-config. All
previous Trinity releases still use kde-config. The trick then is
to ensure your build environment is correct. If you are building
3.5.13.x then you use the 3.5.13.x tarballs. If you are building
R14, then use the GIT tree as sources rather than tarballs.
R14 is expected to be built against TQt3, which will install a tqt-
mt pkgconfig file. If you build with Qt3, as is the case prior to
R14, then a qt-mt pkgconfig file is installed.
If you are running 3.5.13.x as your production environment, you can
still build R14. Use a second computer, use a virtual machine, use
a chroot environment, reboot to a different partition set, etc.
Slavek and Francois build and support both environments. They would
be the best people to ask for advice how they manage both
environments.
Darrell
4 Dec
4 Dec
9:16 p.m.
New subject: [trinity-devel] Trying to fix bug #1170 (Kima FTBFS)
On Tue, Dec 4, 2012 at 4:10 PM, Darrell Anderson <darrella(a)hushmail.com> wrote:
I am trying to build it within a chroot, but unless I am doing that
wrong I do not know what I need to do. :( I am also not opposed to
uninstalling my current version of trinity and working from a
different environment, whatever is the best way to do it. I can use
qemu or virtualbox. It does not matter to me. if there is a specific
way that one would suggest building them please let me know what it
is, even if it a little unorthodox.
Sincerely,
Pauline
As Slávek said
this package is still built with the autotools.
However when I run the configure script it runs through the script
until it stops when it tries to find tde-config. If I change it to
kde-config (in the configure script which I know should not be
needed)
it tells me that it cannot find the qt-mt library.
Starting with R14, kde-config is renamed to tde-config. All
previous Trinity releases still use kde-config. The trick then is
to ensure your build environment is correct. If you are building
3.5.13.x then you use the 3.5.13.x tarballs. If you are building
R14, then use the GIT tree as sources rather than tarballs.
R14 is expected to be built against TQt3, which will install a tqt-
mt pkgconfig file. If you build with Qt3, as is the case prior to
R14, then a qt-mt pkgconfig file is installed.
If you are running 3.5.13.x as your production environment, you can
still build R14. Use a second computer, use a virtual machine, use
a chroot environment, reboot to a different partition set, etc.
Slavek and Francois build and support both environments. They would
be the best people to ask for advice how they manage both
environments.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
4173
days inactive
4173
days old
1 comments
2 participants
participants (2)
-
Darrell Anderson -
pauline martin