Hi Jurgen,
Reading between the lines, it sounds like you're trying to generate the
configure script using the autotools in LTIB?
If so, you can't reliably do this as the autotools is not portable
across versions. This means while you're developing a package, you must
use your own autotools to run autoconf and friends to generate configure
etc.
The reason ltib has this is to satisfy the dependency on one particular
target package (I can't recall the details right now).
So to be clear, when building an ltib .spec file, the configure script
should already be in the sources. This is normally how a package
maintainer would release a package. BTW: this is not a LTIB issues, any
other build system would need the same thing as you can never rely on
the same results from different versions of the autotools.
Regards, Stuart
On 26/10/11 08:09, Lambrecht Jürgen wrote:
Hello,
because I am adding an other echo canceler to linphone, I used the
automake and autoconf tools to update the makefiles.
But my PC's autoconf is version 2.67 and ltib one's is 2.57. And this
gave a nasty bug during ltib build.
My question is:
Why are those tools installed by ltib, and not set as host requirement
(why the remark "Not required we install: automake target package" on
http://ltib.org/documentation-LtibFaq) ?
(The same question in a different way: As workaround, I just deleted the
ltib automake/conf tools; are there side effects?)
Kind regards,
Jürgen
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
