18 Dec
2011
18 Dec
'11
2 p.m.
I am starting to do the development/testing needed to add Trinity to
Linux From Scratch, replacing KDE3. Right now I have a couple of issues
I'd like to get clarified.
First, I notice in the dependencies directory, there are several packages:
dependencies/arts
dependencies/avahi-tqt
dependencies/dbus-1-tqt
dependencies/dbus-tqt
dependencies/tqtinterface
I have no problems with arts or tqtinterface but I don't see the other
three mentioned anywhere. Are these packages required for Trinity? If
so, at what point are they required? We do have instructions already in
LFS for D-Bus and avahi libraries.
Second, I have had some problems building kdelibs. There were no
problems following the instructions for qt3, tqtinterface, or arts, but
there were many places in building kdelibs where I had to edit a
link.txt file and add -lX11. I am fairly new at using cmake so I'd like
to know if there is a way to add this automatically.
My installation of xorg is a little non-standard because the files are
in /opt/xorg, but there are appropriate symlinks at /usr/X11R6 and
/usr/include/X11. I didn't seem to have a problem with include files.
It would also be useful to know how to set -L/opt/xorg/lib, but that is
not critical because I can do essentially the same thing by export(ing)
LIBRARY_PATH.
I'll note that LFS has a policy of not using development versions of
packages, so for now we need to be able to work with trinity-3.5.13.
Thanks for your help.
-- Bruce Dubbs
18 Dec
18 Dec
2:57 p.m.
New subject: [trinity-devel] Adding Trinity to Linux From Scratch
I am starting to do the development/testing needed to
add Trinity to
Linux From Scratch, replacing KDE3. Right now I have a couple of issues
I'd like to get clarified.
First, I notice in the dependencies directory, there are several packages:
dependencies/arts
dependencies/avahi-tqt
dependencies/dbus-1-tqt
dependencies/dbus-tqt
dependencies/tqtinterface
I have no problems with arts or tqtinterface but I don't see the other
three mentioned anywhere. Are these packages required for Trinity? If
so, at what point are they required? We do have instructions already in
LFS for D-Bus and avahi libraries.
The others are required for specific TDE modules/applications only--for
example, there is avahi support in kdebase, and knetworkmanager needs dbus
bindings. So while modules other than tqtinterface and arts are
technically dependencies for certain modules, they are not global
dependencies required for *all* TDE modules.
Second, I have had some problems building kdelibs. There were no
problems following the instructions for qt3, tqtinterface, or arts, but
there were many places in building kdelibs where I had to edit a
link.txt file and add -lX11. I am fairly new at using cmake so I'd like
to know if there is a way to add this automatically.
In the CMakeLists.txt file (usually found in the source directory of the
failing library/application) look for the lines that start with LINK.
Tack " X11" (without the quotes) onto the end of those lines and you
should be set. Also, please be sure to let us know which files needed
this treatment in a bug report!
My installation of xorg is a little non-standard
because the files are
in /opt/xorg, but there are appropriate symlinks at /usr/X11R6 and
/usr/include/X11. I didn't seem to have a problem with include files.
It would also be useful to know how to set -L/opt/xorg/lib, but that is
not critical because I can do essentially the same thing by export(ing)
LIBRARY_PATH.
AFAIK this is the correct solution for handling non-standard system
library locations.
Tim
19 Dec
19 Dec
4:52 a.m.
New subject: [trinity-devel] Adding Trinity to Linux From Scratch
Timothy Pearson wrote:
OK, thanks.
Actually I think the problem is on the HowToBuild wikit page. You have:
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig
(split only for email readability)
however, I think it should be:
export PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig:
$PKG_CONFIG_PATH
As I already had PKG_CONFIG_PATH set with /opt/xorg/lib/pkgconfig, it
made a difference, and the -lX11 flags now appear correctly.
-- Bruce
I am starting
to do the development/testing needed to add Trinity to
Linux From Scratch, replacing KDE3. Right now I have a couple of issues
I'd like to get clarified.
First, I notice in the dependencies directory, there are several packages:
dependencies/arts
dependencies/avahi-tqt
dependencies/dbus-1-tqt
dependencies/dbus-tqt
dependencies/tqtinterface
I have no problems with arts or tqtinterface but I don't see the other
three mentioned anywhere. Are these packages required for Trinity? If
so, at what point are they required? We do have instructions already in
LFS for D-Bus and avahi libraries.
The others are required for specific TDE modules/applications only--for
example, there is avahi support in kdebase, and knetworkmanager needs dbus
bindings. So while modules other than tqtinterface and arts are
technically dependencies for certain modules, they are not global
dependencies required for *all* TDE modules. Second, I have
had some problems building kdelibs. There were no
problems following the instructions for qt3, tqtinterface, or arts, but
there were many places in building kdelibs where I had to edit a
link.txt file and add -lX11. I am fairly new at using cmake so I'd like
to know if there is a way to add this automatically.
In the CMakeLists.txt file (usually found in the source directory of the
failing library/application) look for the lines that start with LINK.
Tack " X11" (without the quotes) onto the end of those lines and you
should be set. Also, please be sure to let us know which files needed
this treatment in a bug report!
4:54 a.m.
New subject: [trinity-devel] Adding Trinity to Linux From Scratch
<snip>
Actually I think the problem is on the HowToBuild
wikit page. You have:
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig
(split only for email readability)
however, I think it should be:
export PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig:
$PKG_CONFIG_PATH
As I already had PKG_CONFIG_PATH set with /opt/xorg/lib/pkgconfig, it
made a difference, and the -lX11 flags now appear correctly.
Looks reasonable; Wiki has been updated.
Thanks!
Tim
6:27 a.m.
New subject: [trinity-devel] Adding Trinity to Linux From Scratch
Timothy Pearson wrote:
<snip>
Well that fix wasn't enough. For kdebase, I needed to do:
find -name link.txt -exec sed -i -e 's/-lz/& -lX11/' {} \;
after the cmake command. If I do this, I might as well pass the
-L/opt/xorg/lib here too. Hopefully when -14 is released, all these
build issues will be solved.
There is also a problem when building kio_nfs.so in that the most recent
glibc libraries dropped nfs/nis. For our system, I needed to add
/lib/libtirpc.so.1.0.10
I'll have to do some more checking as I see my tirpc.pc file is wrong,
but there will need to be some changes in this area.
The good news is that I was able to install and run trinity (through
base). It came up cleanly and looks nice. My remaining issues will be
to get the instructions right for BLFS.
-- Bruce
Actually I think the problem is on the HowToBuild
wiki page. You have:
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig
(split only for email readability)
however, I think it should be:
export PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:
/opt/qt/lib/pkgconfig:
$PKG_CONFIG_PATH
As I already had PKG_CONFIG_PATH set with /opt/xorg/lib/pkgconfig, it
made a difference, and the -lX11 flags now appear correctly.
Looks reasonable; Wiki has been updated. 
18 Dec
18 Dec
2:58 p.m.
New subject: [trinity-devel] Adding Trinity to Linux From Scratch
On Dec 18, 2011, at 2:00, Bruce Dubbs <bruce.dubbs(a)gmail.com> wrote:
I am starting to do the development/testing needed to
add Trinity to Linux From Scratch, replacing KDE3. Right now I have a couple of issues
I'd like to get clarified.
First, I notice in the dependencies directory, there are several packages:
dependencies/arts
dependencies/avahi-tqt
For any app that needs avahi
dependencies/dbus-1-tqt
Substitute the Qt4
backport bus bindings with these for any app that needs it
dependencies/dbus-tqt
Original dbus qt3 bindings
ported to tqt
dependencies/tqtinterface
I have no problems with arts or tqtinterface but I don't see the other three
mentioned anywhere. Are these packages required for Trinity? If so, at what point are
they required? We do have instructions already in LFS for D-Bus and avahi libraries.
Basically, if a kde3 package needed the qt3 one, they now need the tqt one.
Second, I have had some problems building kdelibs. There were no problems following the
instructions for qt3, tqtinterface, or arts, but there were many places in building
kdelibs where I had to edit a link.txt file and add -lX11. I am fairly new at using cmake
so I'd like to know if there is a way to add this automatically.
My installation of xorg is a little non-standard because the files are in /opt/xorg, but
there are appropriate symlinks at /usr/X11R6 and /usr/include/X11. I didn't seem to
have a problem with include files.
It would also be useful to know how to set -L/opt/xorg/lib, but that is not critical
because I can do essentially the same thing by export(ing) LIBRARY_PATH.
I'll note that LFS has a policy of not using development versions of packages, so for
now we need to be able to work with trinity-3.5.13.
There's also R14 coming out in 4 more months :P
I remember that I wanted to do BLFS for 3.5.12 (and bringing it up),
but the lower autoconf version seemed to be a problem. You'll realized
that we haven't fully converted to cmake :-/
Thanks for your help.
-- Bruce Dubbs
4793
days inactive
4793
days old
5 comments
3 participants
participants (3)
-
Bruce Dubbs -
Robert Xu -
Timothy Pearson