Hi Bruce,
On 25 พ.ย. 2012, at 23:57, Bruce Korb <bruce.k...@gmail.com> wrote:
> On Sat, Nov 24, 2012 at 11:57 AM, Paul Eggert <egg...@cs.ucla.edu> wrote:
>> This often means that you haven't run autoheader,
>> so you might try running that, or running autoreconf
>> (which runs autoheader).
>
> Or is supposed to? Below is an xtrace of Gary's "bootstrap" script that
> ultimately arrives at: /usr/bin/autoreconf --install
> but that invocation chokes. I'll see what I can do to get autoreconf to
> run autoheader.
[[snip]]
You can always get a function call trace from any of my (recent) shell scripts
like this:
debug_cmd='eval echo "${FUNCNAME[0]} $*" >&2' bash bootstrap
Autoreconf doesn't always run libtoolize (among others) at the correct time, so
the bootstrap invocation of autoreconf is a little tricky... You also need to
be careful AUTOHEADER is not set in the environment (in the calling shell or
your bootstrap.conf, for example).
What revision of bootstrap are you running? (./bootstrap --version) There might
be a newer one in libtool's git master branch on savannah, in case you have an
old one without recent fixes in it:
http://git.savannah.gnu.org/cgit/libtool.git/plain/bootstrap
Do you have a repo or tarball of your source package I can look at to try and
reproduce?
Cheers,
--
Gary V. Vaughan (gary AT gnu DOT org)
