Re: In rcs 5.9.1 build-aux/extract-help is bash-specific
Dagobert Michelsen <[email protected]> Sun, 20 Oct 2013 15:20:54 +0200
| Newsgroups | gmane.comp.version-control.rcs.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hi Thien, Am 20.10.2013 um 13:51 schrieb Thien-Thi Nguyen: > () Dagobert Michelsen <[email protected]> > () Sat, 19 Oct 2013 12:55:00 +0200 > > in rcs 5.9.1 build-aux/extract-help uses a bash-specific construct, > but has a sh hashbang. The grep command may return 1 which aborts > the execution of the script in sh, but not bash. Forcing the > returncode to true fixes the issue as in this patch: [...] > > The issue occurred when compiling on Solaris 10 Sparc with Sun Studio 12. > > Thanks for reporting this. Is this behavior w/ Solaris /bin/sh > controlled by the "set -e" at the beginning of the script? That is, > does simply removing the "set -e" achieve the same effect as adding > "; true" to the inside-backtick command? Indeed, taking out "set -e" also makes the script not bail out, but now I get /opt/SUNWspro/bin/cc -D_STDC_C99= -D_STDC_C99= -m32 -xarch=sparc -m32 -xarch=sparc -L/opt/csw/lib -o rcs rcs.o ci.o co.o rcsclean.o rcsdiff.o rcsmerge.o rlog.o super.o libparts.a -L../lib -lgnu Undefined first referenced symbol in file ya_ci super.o ld: fatal: symbol referencing errors. No output written to rcs Best regards -- Dago