From: chrubis@suse.cz
To: Joseph Beckenbach <jbeckenbach@lancope.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Apparent trouble with HEAD of LTP
Date: Mon, 21 Jul 2014 17:48:38 +0200 [thread overview]
Message-ID: <20140721154838.GA30527@rei> (raw)
In-Reply-To: <4506ACC2AE90484D87F9A883BA36C21C2ADF0458@LCHQEX03.lancope.local>
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
next prev parent reply other threads:[~2014-07-21 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 14:00 [LTP] Apparent trouble with HEAD of LTP Joseph Beckenbach
2014-07-21 15:48 ` chrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 18:27 Joseph Beckenbach
2014-07-21 7:13 ` chrubis
2014-07-17 17:26 Joseph Beckenbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140721154838.GA30527@rei \
--to=chrubis@suse.cz \
--cc=jbeckenbach@lancope.com \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox