On 10/26/2011 09:52 AM, Stuart Hughes wrote:
Hi Jurgen,
Reading between the lines, it sounds like you're trying to generate the
configure script using the autotools in LTIB?
No, the configure script was already there in the released package, and
then I updated that configure script myself (with my autoconf v2.67)(to
add an extra libary).
Then I got this error:
Making all in mediastreamer2
make[2]: Entering directory
`/usr/src/cross/Ltib-svn/rpm/BUILD/linphone-3.4.3/mediastreamer2'
(CDPATH="${ZSH_VERSION+.}:"&& cd .&& /bin/bash
/usr/src/cross/Ltib-svn/rpm/BUILD/linphone-3.4.3/mediastreamer2/missing
--run autoheader)
Can't locate object method "path" via package "Autom4te::Request" at
//opt/ltib/usr/bin/autom4te line 81.
autoheader: //opt/ltib/usr/bin/autom4te failed with exit status: 1
make[2]: *** [mediastreamer-config.h.in] Error 1
make[2]: Leaving directory
`/usr/src/cross/Ltib-svn/rpm/BUILD/linphone-3.4.3/mediastreamer2'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/usr/src/cross/Ltib-svn/rpm/BUILD/linphone-3.4.3'
make: *** [all] Error 2
error: Bad exit status from /usr/src/cross/Ltib-svn/tmp/rpm-tmp.58855
(%build)
Here a link how to solve
it:http://www.linuxquestions.org/questions/linux-software-2/autoheader-errors-177352/.
After doing "rm -r autom4te.cache/", I got again a build error, but with
a clear error messages (I didn't save the exact message):
aclocal.m4: Warning: generated by autoconf 2.67
/opt/ltib/usr/bin/autom4te failed
And then I deleted the autoconf tools in /opt/ltib/usr/bin/, and
compilation went on.
(I will update the configure script again with the ltib auto tools when
I am finished, so my collegues do not need to change their ltib
installation)
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.
ok
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.
thanks for the clarification,
Jürgen
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