7 Dec
2014
7 Dec
'14
12:56 a.m.
High,
now I'm trying to build R13.2 on Slackware 14.1, trying to follow the
instructions found at
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
This doc leaves several questions open:
1. It doesn't say which release this is about. In the "Suggested
Build Order" section it talks about tqt3, so I guess it's about R14
already, though R14 isn't (actually) released yet. And what if any-
one is forced (or just likes) to install R13.2 or even older release
anyway?
2. It isn't clear about the build tool to use for the different
packages. When talking about the autoconf -> cmake migration, there
should be some details of which package in which release is to be
done with which build tool, or each package should have a quick note
about this in the README or whatever...
I think qt3 itself is neither, but I'm not sure. It has no 'admin' and
no 'cmake' subdirectory, but if this is an acceptable exception for me.
It should be mentioned anyway, maybe for others, or maybe merely for
the sake of being documented (or is it documented elsewhere already?).
3. Problems compiling tqtinterface:
I manually ran ./configure on qt3 and it installed in almost no time,
or rather, with almost no fiddling. But now I'm stuck for hours with
the second step, tqtinterface. It has both a 'cmake' and an 'admin'
subdirectory, but since the page mentioned above lists it in section
"Building Packages with cmake", I first tried cmake, indeed.
But with the instructions listed under "Performing a cmake Build" it
just didn't work. It stopped after failing to run a cmTryCompileExec
step, in which the compiler is called with
/usr/bin/c++ -I/opt/trinity-3.5.13.2/qt3/include -DHAVE_USABLE_QT3
CMakeFiles/cmTryCompileExec737936600.dir/src.cxx.o -o cmTryCompileExec737936600 -rdynamic
-L/opt/trinity-3.5.13.2/qt3/lib -lqt-mt
This version is already altered from the "default"... I have put in
the include path option, without which even the compilation failed,
of course.
But even then this step failed, due to countless undefined references,
because the command line issued tells the linker to only drag in qt-mt,
but none of X11, Xext, dl, z, jpeg, png, mng, and I don't know how many
else. I have put in those mentioned here manually in a step-by-step,
incremental, very tedious build/less $erroroutput/edit $buildscript
process. Shouldn't the script, that tries to compile the program, know
which libraries it needs and instruct the linker to drag them in? What
am I doing wrong?
Of course, maybe the "ready for cmake" list is indeed for R14, and as
such doesn't match my sources. Buuuuuut... trying with autoconf also
fails, because there isn't even a configure script.
Oh, wait, I didn't _re_generate autoconf/automake files yet, as it has
been suggested. But then, trying it yields nothing productive anyway:
Copying the mentioned files from
/usr/share/aclocal/libtool.m4
/usr/share/libtool/config/ltmain.sh
(maybe they're wrong?), then running
$ make -f admin/Makefile.common
*** automake (GNU automake) 1.11.5 found.
*** Creating acinclude.m4
make[1]: Entering directory
`/home/jagged/src/trinity-build/tqtinterface-trinity-3.5.13.2'
make[1]: *** No rule to make target `libltdl/ltdl.m4', needed by `acinclude.m4'.
Stop.
make[1]: Leaving directory
`/home/jagged/src/trinity-build/tqtinterface-trinity-3.5.13.2'
make: *** [cvs] Error 1
Well, I'm completely clueless... :-/
Just in case it matters:
Slackware 14.1, kernel 3.10.17
gcc version 4.8.2
ld 2.23.52.0.1.20130226
No idea if I should attach the error output from a cmake approach.
4. Some other points that I find a bit confusing
- In the "configure and build" code boxes, you use /opt/trinity/lib/qt3*
for QTDIR, but /opt/trinity/qt3* in PATH and PKG_CONFIG_PATH.
Is this correct? (It could be that some later step establishes some
/opt/trinity/lib/qt3* dir, but after configuring qt3 with
-prefix=/opt/trinity/qt3, and installing the result, there is no
such directory (yet).)
- Introducing a parameter named $CPUOPT ist just... well... confusing.
So much for now. Thanks in advance for any suggestion.
Regards,
Jagged
PS: Since it is a wiki, I guess I could help improving it, if desired
(it's not that I'm an observing but otherwise passive nagger), just at
the moment I think my experience is close to zero...
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
7 Dec
7 Dec
12:31 p.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On Sun, 7 Dec 2014 01:56:59 +0100
Jagged O'Neill <jagged_4tr(a)jagged.tk> wrote:
High,
now I'm trying to build R13.2 on Slackware 14.1, trying to follow the
instructions found at
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
This doc leaves several questions open:
1. It doesn't say which release this is about. In the "Suggested
Build Order" section it talks about tqt3, so I guess it's about R14
already, though R14 isn't (actually) released yet. And what if any-
one is forced (or just likes) to install R13.2 or even older release
anyway?
It was ported from the old wiki, so unless someone's changed it
recently, it's for 13.X.
2. It isn't clear about the build tool to use for
the different
packages. When talking about the autoconf -> cmake migration, there
should be some details of which package in which release is to be
done with which build tool, or each package should have a quick note
about this in the README or whatever...
"List of Packages Building with cmake" says " Build everything not in the
list above with autotools." autoconf is part of autotools.
If you think that's unclear, can you suggest a better way to word it?
(That's a sincere question, not an attempt to needle you. The more people
understand the wiki, the more of them will have a good experience with
Trinity.)
No idea if I should attach the error output from a
cmake approach.
Do, please, since that's the expected build system for tqtinterface.
E. Liddell
1:18 p.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On Sun, Dec 07, 2014 at 07:31:24AM -0500, E. Liddell wrote:
On Sun, 7 Dec 2014 01:56:59 +0100
No, sorry, I wasn't unclear about that I meant this in conjunction
with point 1.; an Idea would be to make one list for any "initial"
release, and for each subsequent release another list that says
which packages have been migrated to cmake meanwhile.
(One point why I thought this is all about R14 is that the package
names are given as tdelibs, tdebase, etc., while the package files
I downloaded (from
http://copernicus.mirrorservice.org/sites/trinitydesktop.org/trinity/releas…)
are still named kdelibs, kdebase, etc.)
Another idea, IMHO even better would be a table, one row per package,
one column per Trinity release, stating the respective build tool to
use as (a)utoconf, (c)make or (m)anual --- just an idea.
1. It doesn't say which release this is about. [...]
It was ported from the old wiki, so unless someone's changed it
recently, it's for 13.X.
2. It isn't clear about the build tool to use
for the different
packages. When talking about the autoconf -> cmake migration, there
should be some details of which package in which release is to be
done with which build tool, or each package should have a quick note
about this in the README or whatever...
"List of Packages Building with cmake" says " Build everything not in the
list above with autotools." autoconf is part of autotools.
If you think that's unclear, can you suggest a better way to word it? (That's a sincere question, not an attempt to
needle you. The more people
understand the wiki, the more of them will have a good experience with
Trinity.)
Okay, the logs are from a run in which I passed "-ldl -lpthread -lX11
-lXext -lz -ljpeg -lmng -lpng" already. There's not a lot missing,
but this makes the error log quite some bytes shorter.
Thanks a lot!
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
No idea if I should attach the error output from
a cmake approach.
Do, please, since that's the expected build system for tqtinterface. 
8 Dec
8 Dec
4:02 a.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On 12/07/2014 10:18 PM, Jagged O'Neill wrote:
On Sun, Dec 07, 2014 at 07:31:24AM -0500, E. Liddell
wrote:
Hi,
I do not use Slackware, but at this link you should be able to find additional building
instruction for TDE on Slackware.
http://www.giustetti.net/wiki/index.php?title=En/trinity_desktop_environment
Cheers
Michele
On Sun, 7 Dec 2014 01:56:59 +0100
No, sorry, I wasn't unclear about that I meant this in conjunction
with point 1.; an Idea would be to make one list for any "initial"
release, and for each subsequent release another list that says
which packages have been migrated to cmake meanwhile.
(One point why I thought this is all about R14 is that the package
names are given as tdelibs, tdebase, etc., while the package files
I downloaded (from
http://copernicus.mirrorservice.org/sites/trinitydesktop.org/trinity/releas…)
are still named kdelibs, kdebase, etc.)
Another idea, IMHO even better would be a table, one row per package,
one column per Trinity release, stating the respective build tool to
use as (a)utoconf, (c)make or (m)anual --- just an idea.
1. It doesn't say which release this is about. [...]
It was ported from the old wiki, so unless someone's changed it
recently, it's for 13.X.
2. It isn't clear about the build tool to use
for the different
packages. When talking about the autoconf -> cmake migration, there
should be some details of which package in which release is to be
done with which build tool, or each package should have a quick note
about this in the README or whatever...
"List of Packages Building with cmake" says " Build everything not in the
list above with autotools." autoconf is part of autotools.
If you think that's unclear, can you suggest a better way to word it? (That's a sincere question, not an attempt to
needle you. The more people
understand the wiki, the more of them will have a good experience with
Trinity.)
Okay, the logs are from a run in which I passed "-ldl -lpthread -lX11
-lXext -lz -ljpeg -lmng -lpng" already. There's not a lot missing,
but this makes the error log quite some bytes shorter.
Thanks a lot!
Jagged
No idea if I should attach the error output from
a cmake approach.
Do, please, since that's the expected build system for tqtinterface.
5:30 p.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On Mon, Dec 08, 2014 at 01:02:47PM +0900, Michele Calgaro wrote:
>No, sorry, I wasn't unclear about that I meant
this in conjunction
Sorry for ^^^^ this ^^^^ faux pas :-/ of course, I wasn't clear.
Hi,
I do not use Slackware, but at this link you should be able to find additional building
instruction for TDE on Slackware.
http://www.giustetti.net/wiki/index.php?title=En/trinity_desktop_environment
Well, yes, though it is about Slack 14.0, and I'm fiddling with 14.1,
but am actually waiting for the next release, it may hold some valuable
information.
But just before going: it talks about HAL, but I think I have read in
some posts here in the list that HAL is supported but not a dependency
--- so is it okay to just omit it?
The site also lists tqt3 as well as qt3 and tqtinterface, but in the
page about tqt3 contains the statement
"Reading the docs and guides I got the impression that tqt3 is the
Qt3 toolkit merged with the tqt-interface library.",
but furthermore saying
"In the end tqt3 cannot be used as a basis for a TDE full build for
Slackware."
--- does this mean I should just skip it? (There's no tqt3 package in
the collection I downloaded anyway.)
Also missing (according to the list of packages in section
"Suggested Build Order" on
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules)
from my collection of packages are tqca-tls, sip4-tqt, python-tqt,
and tqscintilla. I forgot to mention this in my original question.
How about these? (That's also a reason why I thought this doc was
about R14 already.)
Regards,
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
9 Dec
9 Dec
2:57 a.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On 12/09/2014 02:30 AM, Jagged O'Neill wrote:
On Mon, Dec 08, 2014 at 01:02:47PM +0900, Michele
Calgaro wrote:
Hi,
1)v3.5.13.2 uses the k* packages (kdelibs, kdebase, ....) and requires HAL.
2)v14.0.0 uses the t* packages (tdelibs, tdebase, ....) and does not require HAL on Linux
systems. If you are using a
*bsd system, you still need HAL, that's why v14.0.0 is compatible with HAL.
3) v14.0.0 is usually built on top of tqt3.
4) I usually build sip4-tqt, tqscintilla and python-tqt just before python-trinity. I
build tqca-tls just after dbus-1-tqt.
Hope this make things a little more clear :-)
Cheers
Michele
> No, sorry, I wasn't unclear about that I
meant this in conjunction
Sorry for ^^^^ this ^^^^ faux pas :-/ of course, I wasn't clear.
Hi,
I do not use Slackware, but at this link you should be able to find additional building
instruction for TDE on Slackware.
http://www.giustetti.net/wiki/index.php?title=En/trinity_desktop_environment
Well, yes, though it is about Slack 14.0, and I'm fiddling with 14.1,
but am actually waiting for the next release, it may hold some valuable
information.
But just before going: it talks about HAL, but I think I have read in
some posts here in the list that HAL is supported but not a dependency
--- so is it okay to just omit it?
The site also lists tqt3 as well as qt3 and tqtinterface, but in the
page about tqt3 contains the statement
"Reading the docs and guides I got the impression that tqt3 is the
Qt3 toolkit merged with the tqt-interface library.",
but furthermore saying
"In the end tqt3 cannot be used as a basis for a TDE full build for
Slackware."
--- does this mean I should just skip it? (There's no tqt3 package in
the collection I downloaded anyway.)
Also missing (according to the list of packages in section
"Suggested Build Order" on
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules)
from my collection of packages are tqca-tls, sip4-tqt, python-tqt,
and tqscintilla. I forgot to mention this in my original question.
How about these? (That's also a reason why I thought this doc was
about R14 already.)
Regards,
Jagged
9:16 p.m.
New subject: [trinity-users] Confusion about building from sources (R13.2 on Slack 14.1)
On Tue, Dec 09, 2014 at 11:57:54AM +0900, Michele Calgaro wrote:
1) [...]
Hope this make things a little more clear :-)
Yes, it certainly does :-) Thanks a lot!
But now, and since I'm always a bit short of time, I reconsider
just waiting for the final R14, so that I can definitely get
around custom-installation of HAL on Slackware. It's only a few
days left since then, if there's not a delay due to severe pro-
blems, right? Maybe I can get some other stuff to run until on
Slack until then.
Thanks again, and best regards,
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
3666
days inactive
3668
days old
6 comments
3 participants
participants (3)
-
E. Liddell -
Jagged O'Neill -
Michele Calgaro