Re: [Ltib] Problem trhing to add ATF package to LTIB

[Stuart Hughes]

Hi Peter,

You've hit upon one of the open-source worlds nastiest dependency loops.
 You need a newer package X, you get that and then Y needs a newer
package and so on.  autoconf/make are "problematic" as they seem to be
very version sensitive.

If you upgrade these, you'd probably find a bunch of the current
packages fail.  What this means is that to move forward to a later
vintage, a number of package would need to be moved forward at the same
time (quite a lot of work).

In terms of the automake/autoconf build ordering in LTIB (for host
packages) the order is controlled by config/userspace/pkg_map and from
what I see autoconf is built before automake, so I don't understand
quite what the issue is that you're seeing (the order seems to be what
you want?)

To me it sounds like the ATF package is not quite right.  I would not
expect to have to run autoconf/automake unless I'm a developer of the
package (this is normal due to the horrible version dependencies of
those).  That being the case, one solution may be to ask the developer
to include a pre-made configure (and other outputs of autoconf/automake)
in his releases (snapshots) and to try those in LTIB (e.g. don't run
autoconf/automake, just run ./configure).

Regards, Stuart


Peter Barada wrote:
> Stuart,
> 
> I'm trying to add the ATF package (from
> http://www.netbsd.org/~jmmv/atf/), and I'm running int problems as ATF
> wants autoconf-2.60 or newer
> 
> I upgrade autoconf to version 2.65 (and are wondering what packages am I
> going to break in the process), but when I did that then expanded the
> ATF package to update its configure (since I need to fix it for
> cross-compliation to add in either a cross-compliation clause, or add in
> "--with" processing to allow the spec file to specify target
> capabilities, the process:
> 
> $ ./ltib -p atf -m prep
> $ ./ltib -m shell
> LTIB> cd rpm/BUILD/atf-0.7
> LTIB> aclocal -I ./m4
> LTIB> autoconf
> LTIB> automake
> 
> 
> It complains with:
> 
> configure.ac: required file `admin/mkinstalldirs' not found
> configure.ac:49: require Automake 1.9, but have 1.7.6
> 
> I tried to update automake to 1.11.1, but part of automake's configure
> is to test for autoconf, and that's problematic since the preconfig
> build of automake occurs *before* autoconf is installed into
> /opt/ltib/usr/bin - the build errors out.  Is there anyway to break up
> the LTIBS contruction process to deploy the autoconf package *before*
> prep/build of automake to work around this?
> 
> I tried hacking automake to include a "SKIP_AUTOCONF_TESTS=y" to short
> out the autoconf tests (and supply my own answers), but this failed as
> well since other voodoo in automake needs some side-effects of the
> automake configure process that was skipped testing for autoconf's
> existance.
> 
> Worse, I tried to back up to the LTIB-supplied versions of
> autoconf/automak, and use external tools to do the autoconf/automake in
> atf, but that fails since atf's created configure needs to see those
> other tools to build.
> 
> Before I dig into this rathole much deeper, I'm wondering if anyone has
> run into problems trying to add a package that requires newer versions
> of autoconf/automake and how they solved it.
> 
> Thanks in advance!
> 
> 
> -- 
> Peter Barada <address@hidden <mailto:address@hidden>>
> Logic Product Development, Inc.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib