Bug#382240: ksh: FTBFS: bashisms ?

2006-08-10 Thread Oliver Kiddle
--- Julien Danjou [EMAIL PROTECTED] wrote:

 ksh fails to build, however I guess this is caused by /bin/sh linked
 to /bin/dash.
 
 If you really need bash and don't use only POSIX compliant syntax,
 please call /bin/bash instead of sh.

Actually, more likely this is dash failing to be POSIX compliant.

dash is pdksh based right? Those ksh build scripts are fairly
complicated and they work with ksh88/ksh93/bash/zsh(with sh emulation)
and the /bin/sh on various Unix systems but not with pdksh. I even had
to apply a fix for it to work with bash 3.1.

It would be useful if you could attempt to track down which part of the
build script is not running correctly under dash. The alternative might
be detecting /bin/sh being dash and trying zsh/bash whatever instead.

Oliver





___ 
All new Yahoo! Mail The new Interface is stunning in its simplicity and ease 
of use. - PC Magazine 
http://uk.docs.yahoo.com/nowyoucan.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#382240: ksh: FTBFS: bashisms ?

2006-08-10 Thread Julien Danjou
On Thu, Aug 10, 2006 at 08:45:02AM +0100, Oliver Kiddle wrote:
 Actually, more likely this is dash failing to be POSIX compliant.

You're probably better than me on the subject ;)

 dash is pdksh based right? Those ksh build scripts are fairly
 complicated and they work with ksh88/ksh93/bash/zsh(with sh emulation)
 and the /bin/sh on various Unix systems but not with pdksh. I even had
 to apply a fix for it to work with bash 3.1.
 
 It would be useful if you could attempt to track down which part of the
 build script is not running correctly under dash. The alternative might
 be detecting /bin/sh being dash and trying zsh/bash whatever instead.

Since bash is essential and is installed you could simply use it
explicitely (SHELL=/bin/bash), no?.

I'll try to take a look on what fails. I can send you the full buildd
log if it helps.

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature


Bug#382240: ksh: FTBFS: bashisms ?

2006-08-09 Thread Julien Danjou
Package: ksh
Version: 93r-1
Severity: important

Hello,

There was a problem while autobuilding your package:

 Automatic build of ksh_93r-1 on avidan by sbuild/i386 0.49
 Build started at 20060809-1834
 **
...
  debian/rules build
 bin/package make strip=0
 package: update /build/buildd/ksh-93r/bin/execrate
 package: warning: yacc: not found -- some make actions may fail
 package: warning: bison: not found -- some make actions may fail
 package: initialize the /build/buildd/ksh-93r/arch/linux.i386 view
 package: update /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/make/probe
 package: update /build/buildd/ksh-93r/arch/linux.i386/bin/proto
 package: update /build/buildd/ksh-93r/arch/linux.i386/bin/mamake
 package: update /build/buildd/ksh-93r/arch/linux.i386/bin/ratz
 package: update /build/buildd/ksh-93r/arch/linux.i386/bin/release
 package: make output captured in 
 /build/buildd/ksh-93r/arch/linux.i386/lib/package/gen/make.out
 package: make start at Wed Aug  9 16:35:27 UTC 2006 in 
 /build/buildd/ksh-93r/arch/linux.i386
 + mamake -r */* -k install ksh93 strip=0
 + mamake -C cmd/INIT -k strip=0 install
 /bin/sh: Can't open mamprobe
 mamake [cmd/INIT]: /build/buildd/ksh-93r/src/cmd/INIT/Mamfile: 8: 
 /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/mam/NGGBOHJL: cannot 
 generate probe info
 mamake: *** exit code 1 making cmd/INIT
 + mamake -C lib/libast -k strip=0 install
 /bin/sh: Can't open mamprobe
 mamake [lib/libast]: /build/buildd/ksh-93r/src/lib/libast/Mamfile: 8: 
 /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/mam/NGGBOHJL: cannot 
 generate probe info
 mamake: *** exit code 1 making lib/libast
 + mamake -C lib/libdll -k strip=0 install
 /bin/sh: Can't open mamprobe
 mamake [lib/libdll]: /build/buildd/ksh-93r/src/lib/libdll/Mamfile: 10: 
 /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/mam/NGGBOHJL: cannot 
 generate probe info
 mamake: *** exit code 1 making lib/libdll
 + mamake -C lib/libcmd -k strip=0 install
 /bin/sh: Can't open mamprobe
 mamake [lib/libcmd]: /build/buildd/ksh-93r/src/lib/libcmd/Mamfile: 10: 
 /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/mam/NGGBOHJL: cannot 
 generate probe info
 mamake: *** exit code 1 making lib/libcmd
 + mamake -C cmd/ksh93 -k strip=0 install
 /bin/sh: Can't open mamprobe
 mamake [cmd/ksh93]: /build/buildd/ksh-93r/src/cmd/ksh93/Mamfile: 10: 
 /build/buildd/ksh-93r/arch/linux.i386/lib/probe/C/mam/NGGBOHJL: cannot 
 generate probe info
 mamake: *** exit code 1 making cmd/ksh93
 package: make: errors making /build/buildd/ksh-93r/arch/linux.i386/bin/ksh
 package: make done  at Wed Aug  9 16:35:27 UTC 2006 in 
 /build/buildd/ksh-93r/arch/linux.i386
 make: *** [build-stamp] Error 1
 **
 Build finished at 20060809-1835
 FAILED [dpkg-buildpackage died]
 --

ksh fails to build, however I guess this is caused by /bin/sh linked to
/bin/dash.

If you really need bash and don't use only POSIX compliant syntax,
please call /bin/bash instead of sh.

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature