trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] Howto handle differing versions of libtool in TDE builds

From: "David C. Rankin" <drankinatty@...>
Date: Tue, 20 Mar 2012 00:48:13 -0500
On 03/19/2012 09:14 PM, Darrell Anderson wrote:
> First thought is I am not an expert!
> 
> Second thought is according to the instructions at the wiki, the way to use libtools is to use the libtool.m4 and ltmain.sh installed on the system to regenerate the files and not the files provided in each module's sources. Therefore we don't really use libtools from any upstream sources. Are you doing that?
> 
> Third thought is although I appreciate your frustrations, seems to me the immediate focus for R14 should be the bug tracker and not bleeding edge I want-my-system-to-crash every-other-day distros. Perhaps roll back your system to a previous version and likely most or all of these problems disappear? Yes, we still need to address the problems --- down the road after R14, but bleeding edge rolling distros should not be dictating project focus. We can't keep pace now let alone with bleeding edge.
> 
> Darrell

I agree, with all points. Calvin has valid points as well. What I'm trying to
get my arms around is what needs to be fixed so TDE builds with current upstream
packages. Granted, this is a moving target, and I've considered moving to slack
or debian for R14 testing, but that would simply interject more delay. Bugs need
squashing, but it is very difficult to work bugs if there is nothing to test the
bugs against.

For the autotools packages, I follow the HowToBuild wiki to the tee and that has
exposed the problem with the current libtool.m4 not working the tde libtool
version. After copying the ltmain.sh and libtool.m4 files from the system to the
/admin dir, the libtool file generated by:

  make -f admin/Makefile.common

is simply broken and references undeclared variables preventing tdeutils (and
probably most other autotools packages from building at all) I've put this out
to the Arch developers and their input suggests the versions are simply
incompatible due to the difference in forks between the libtool versions being used.

The libtool version used by Arch is libtool 2.4.2, which according to
http://www.gnu.org/software/libtool/ is the latest 'stable' version. Not a git
or svn or other cvs version of libtool, but the stable version.

Yes, that is frustrating because it shows that the TDE autotool/libtool code is
no longer compatible with the current libtool/autofoo tools. That's just
something we have to overcome. I think cmake conversion would resolve this
issue, but I don't even know where to start. I've just skipped tdeutils for now,
but that will be a mandatory package to fix building on before R14 or building
will break for all distros when they update to the current stable libtool.


-- 
David C. Rankin, J.D.,P.E.