Re: [LTP] Apparent trouble with HEAD of LTP

Re: [LTP] Apparent trouble with HEAD of LTP

[Joseph Beckenbach]

Hi, Cyril!

Ah, then autotools must be my issue.
I've got "autotools-dev-20120608.1" package installed, per dpkg-query on those boxes.
Must be something stuck in our local package-repo mirroring process;  maybe it's manual-only.

If we can figure out which version of autotools is fine, I suggest we document that in INSTALL
alongside putting the patch back in.

Thanks!

Joseph
Joseph Beckenbach, senior QA engineer : Automation  -- 470-299-7166
Lancope, Inc. -- makers of StealthWatch

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] Apparent trouble with HEAD of LTP

[chrubis]

Hi!
> Ah, then autotools must be my issue.
> I've got "autotools-dev-20120608.1" package installed, per dpkg-query on those boxes.
> Must be something stuck in our local package-repo mirroring process;  maybe it's manual-only.
> 
> If we can figure out which version of autotools is fine, I suggest we document that in INSTALL
> alongside putting the patch back in.

LTP must be backward compatible so I've readded the -I m4 back.

So currently we have both -I m4 and AC_CONFIG_MACRO_DIR() which works
fine with both older and newer autotools and also fixes autoreconf on
newer autotools. So only thing that may get documented is that
autoreconf needs newer autoconf.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] Apparent trouble with HEAD of LTP

[Joseph Beckenbach]

Greetings, Cyril, all!

Merely adding libtool (2.4.2) onto the system still leaves me with the munged ./configure script.

To correct this issue I did:

1:  added back '-I m4' to include/mk/automake.mk

2:  `make distclean ; rm -f configure`

3:  restarted my work at the `make autotools` step

I see no odd output or bad warnings from compilations.
`make install` is also clean, and invoking `/path/to/runltp -h` gives help output as expected.

Thanks!

Joseph
Joseph Beckenbach, senior QA engineer : Automation
x97166
M 678-602-3192


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] Apparent trouble with HEAD of LTP

[chrubis]

Hi!
> Merely adding libtool (2.4.2) onto the system still leaves me with the munged ./configure script.
> 
> To correct this issue I did:
> 
> 1:  added back '-I m4' to include/mk/automake.mk
> 
> 2:  `make distclean ; rm -f configure`
> 
> 3:  restarted my work at the `make autotools` step
> 
> I see no odd output or bad warnings from compilations.
> `make install` is also clean, and invoking `/path/to/runltp -h` gives help output as expected.


You are not the only one with this problem, I will fix this ASAP.

With the last commit I've added AC_CONFIG_MACRO_DIR(m4) which should add
the path to m4 directory instead of the -I m4 (which works for me
apparently because I have recent enough autotools). According to the GNU
mailing list the macro was not working until recently, see:

http://lists.gnu.org/archive/html/autoconf/2013-08/msg00013.html

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

[LTP] Apparent trouble with HEAD of LTP

[Joseph Beckenbach]

Greetings, Cyril, all!

I just pulled down LTP source (source-forge link to ltp-master.zip) and unpacked to start some testing.
However, I cannot get past ./configure ... since crafting ./configure failed to expand LTP_CHECK_FORTIFY_SOURCE (and all the LTP_CHECK_*)
which appear in m4/ltp-*.m4 files.  Compilations fail because this then provokes lots of '@foo@' expansions to not occur in include/mk/config.mk and include/mk/features.mk.

The most recent commit was "configure.ac: Add AC_CONFIG_MACRO_DIR" which I think is causing my trouble.

This is on (several instances of) a Debian 7.6 system.  All tools cited in ./INSTALL are present and at least as recent as called out in that documentation.
Googling provides a year-old thread on autoconf / autoconfigure.ac mentioning AC_CONFIG_MACRO_DIR [0]
which suggests libtool needs to figure in somehow -- and libtool package / executable libtoolize are *not* present on this system.
Given it appears this project's configuration sequence runs through ./aclocal.m4,
recent autoconf documentation [1] suggests to me that this macro does not justify dropping "-I m4"
(given we have no top-level Makefile.am involved).

And indeed, manually backing out just the include/mk/automake.mk one-line change done by commit "edbae29d774e30967bee74463ad505ff9a81f87d" unblocks me.

Am I missing something?  Is the documentation missing something?  Is the `make autotools` step missing something?
Color me "confused but able to progress".
Thanks!

Joseph
Joseph Beckenbach, senior QA engineer : Automation

[0] https://bbs.archlinux.org/viewtopic.php?pid=1258673 

[1] https://www.gnu.org/software/autoconf/manual/autoconf-2.65/html_node/Input.html


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list