Hi Paul,
On Sat, Nov 24, 2012 at 11:57 AM, Paul Eggert wrote:
> This often means that you haven't run autoheader,
> so you might try running that, or running autoreconf
> (which runs autoheader).
In my case, it was a compound problem with three factors:
1. I was using a bootstrap script with a
Hi Gary!
On 11/25/12 09:36, Gary V. Vaughan wrote:
> 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
I tend to use debug_cmd="PS4='>BS-\$FUNCNAME> ' ; set -x" bash bootstrap
On error e
Hi Bruce,
On 25 พ.ย. 2012, at 23:57, Bruce Korb wrote:
> On Sat, Nov 24, 2012 at 11:57 AM, Paul Eggert 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 Ga
On Sat, Nov 24, 2012 at 11:57 AM, Paul Eggert 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/auto
