Re: commit script annoyance

[Gary V. Vaughan]

Bob Friesenhahn wrote:
> On Sun, 10 Oct 2004, Gary V. Vaughan wrote:
>
> > Bob Friesenhahn wrote:
> >
> > > Now that the libtool CVS commit script is configured, it can only be 
> > > used on the same host that libtool was bootstrapped on.  This is most 
> > > annoying.
> > >
> > > If I bootstrap under Solaris, when I run the commit script under 
> > > FreeBSD it simply returns without displaying an error message or 
> > > doing anything.
> >
> >
> > That's odd.  What does commit --debug give you?  I can only imagine that
> > the paths it chooses for sed, grep and the like work for one but not the
> > other.
>
>
> shaggy:src/gnu/libtool-branch-2-0% ./commit --debug
> commit: enabling shell trace mode
> + test 0 -gt 0
> + test -z
> + test -n
> + test -n
> shaggy:src/gnu/libtool-branch-2-0%

Presumably `echo $?' at this point is now 1?

If so, exit_cmd is being changed from the default (of `:') to `exit' 
somehow, so the script is bailing out just after the `Bail out if the 
options were screwed' comment.

That can only happen in func_missing_arg (which shouldn't be called in
you test case), or in one of the two integrity tests at the end of the
option checking loop.  Neither of which should be happening.  Maybe 
$ECHO is set badly for you?

Did you build commit with bootstrap? Or from Makefile.maint?  If the
latter, rerunning bootstrap should fix it.

If none of that helps, can you send me the output of `sh -vx ./commit' 
please?

Cheers,
        Gary.
--
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature