Message: previous - next
Month: March 2011

Re: [trinity-devel] Tim Need help with 3.5.12 automake files

From: Darrell Anderson <humanreadable@...>
Date: Sun, 27 Mar 2011 22:33:34 -0700 (PDT)
Yay for me.

FYI to anyone else challenged with building packages.

I discovered that digikam and gwenview would not build because I needed to rebuild libkdcraw, libkexiv2, libkipi, and kipi-plugins to link to the new /opt/trinity/lib locations. Although all of those dependency packages were installed, they were linked to /usr/lib.

I found the culprits by running:

grep -r '' /usr/lib
grep -r '' /usr/lib

The only 3.5.12 package I can't build to /opt/trinity is pykde3.


--- On Sun, 3/20/11, Darrell Anderson <humanreadable@...> wrote:

> From: Darrell Anderson <humanreadable@...>
> Subject: [trinity-devel] Tin Need help with 3.5.12 automake files
> To: trinity-devel@...
> Date: Sunday, March 20, 2011, 11:37 PM
> Tim,
> I am able to build all of the same 3.5.12 packages I built
> last autumn except PyKDE3, Digikam, and Gwenview. I already
> submitted a post about PyKDE3 (help is appreciated!).
> The primary difference this time that the builds are
> failing is I am trying to install the Trinity/KDE packages
> into /opt/trinity rather than /usr. Some library and support
> packages, such as sip, PyQT3, PyKDE3, libical, libcaldav,
> etc., I am still installing in /usr and /usr/lib.
> Digikam FTBFS with this error:
> ====================
> grep: /usr/lib/ No such file or directory
> /usr/bin/sed: can't read /usr/lib/ No such
> file or directory
> libtool: link: `/usr/lib/' is not a valid
> libtool archive
> ====================
> Gwenview FTBFS with this error:
> ====================
> grep: /usr/lib/ No such file or directory
> /usr/bin/sed: can't read /usr/lib/ No such file
> or directory
> libtool: link: `/usr/lib/' is not a valid libtool
> archive
> ====================
> Notice the builds are trying to find those files in
> /usr/lib rather than /opt/trinity/lib. Something in the
> configuration files is hard-coded to /usr/lib.
> I realize 3.5.12 is more or less etched in stone, but the
> cmake conversion will take time. All I need is a patch that
> I can merge on-the-fly in my build scripts to ensure
> automake looks in the correct location. Besides, neither of
> these packages have been converted to cmake yet and probably
> won't be for some time.
> Maybe the problem is an environment variable, although all
> of the other packages compiled fine.
> I want to get all of these 3.5.12 packages to build in
> Slackware 12.2 with /opt/trinity. Once proven they will
> build, install, and run there I then will start the testing
> the build process with the next Slackware release, which are
> required to get installed in a location other than /usr.
> This is very much proof of concept before moving to the next
> step. Not to mention that in the next step I need to build
> qt3 too.
> Should anyone start quashing bugs with the core or main
> suite packages I can rebuild Trinity packages in 12.2 and
> test those patches immediately. I also should be able to
> install Trinity 3.5.12 alongside KDE 3.5.10 in 12.2, which
> will help all of us with troubleshooting and comparisons to
> KDE3.
> Thanks much!
> Darrell
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messsages on the Web archive:
> Please remember not to top-post: