Skip to contentSkip to conversation

: LTP Build failure on 2.6.24 kernel

LTP Mike Frysinger 2 participants 7 messages Jan 28, 2008 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28 UTC
2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.
-mike

#2 lore raw
Quoted 17 lines · Mike Frysinger
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28 UTC
2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

Quoted 8 lines

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

Or instead of working on making your script using only the stuff specified in IEEE 1003.1-2004 you could simply replace the #!/bin/sh at the top with a #!/bin/bash and everbody will be happy.

Quoted 1 line

-mike

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#3 lore raw
Quoted 27 lines · Adrian Bunk
Quoted 17 lines · Mike Frysinger
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28 UTC
2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

Quoted 8 lines

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

Quoted 3 lines

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

yes, local is a bsd extension not in POSIX. it has been implemented by every shell so far though. as soon as someone complains, i'll be more than happy to fix it.

Quoted 3 lines

Or instead of working on making your script using only the stuff specified in IEEE 1003.1-2004 you could simply replace the #!/bin/sh at the top with a #!/bin/bash and everbody will be happy.

no
-mike

#4 lore raw
Quoted 28 lines · Mike Frysinger
Quoted 27 lines · Adrian Bunk
Quoted 25 lines · Mike Frysinger
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28 UTC
2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

Quoted 7 lines
Quoted 3 lines

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

yes, local is a bsd extension not in POSIX. it has been implemented by every shell so far though. as soon as someone complains, i'll be more than happy to fix it.

David Korn's ksh93 (e.g. shipped in the Debian "ksh" package) disproves your claim "it has been implemented by every shell so far".

Quoted 6 lines
Quoted 3 lines

Or instead of working on making your script using only the stuff specified in IEEE 1003.1-2004 you could simply replace the #!/bin/sh at the top with a #!/bin/bash and everbody will be happy.

no
-mike

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#5 lore raw
Quoted 35 lines · Adrian Bunk
Quoted 34 lines · Mike Frysinger
Quoted 32 lines · Adrian Bunk
Quoted 17 lines · Mike Frysinger
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28
UTC 2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

Quoted 9 lines

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

Quoted 6 lines
Quoted 3 lines

yes, local is a bsd extension not in POSIX. it has been implemented by every shell so far though. as soon as someone complains, i'll be more than happy to fix it.

David Korn's ksh93 (e.g. shipped in the Debian "ksh" package) disproves your claim "it has been implemented by every shell so far".

sorry, i left out the operative word "relevant". i dont care what random shell fails unless people are actually utilizing it as their /bin/sh in any sort of useful context. as soon as someone complains for real and not just to be annoying, i'll address their complaint then.

the issue that spawned this thread has been fixed in latest dash git tree, but no new release has been cut. Debian has grabbed said fixes, so go bug Ubuntu if they havent as well.
-mike

#6 lore raw
Quoted 40 lines · Mike Frysinger
Quoted 39 lines · Adrian Bunk
Quoted 37 lines · Mike Frysinger
Quoted 28 lines · Adrian Bunk
Quoted 17 lines · Mike Frysinger
Quoted 7 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28 06:47:28
UTC 2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

Quoted 9 lines

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

Quoted 4 lines

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

yes, local is a bsd extension not in POSIX. it has been implemented by every shell so far though. as soon as someone complains, i'll be more than happy to fix it.

Quoted 8 lines
Quoted 2 lines

David Korn's ksh93 (e.g. shipped in the Debian "ksh" package) disproves your claim "it has been implemented by every shell so far".

sorry, i left out the operative word "relevant". i dont care what random shell fails unless people are actually utilizing it as their /bin/sh in any sort of useful context. as soon as someone complains for real and not just to be annoying, i'll address their complaint then.
...

You started with claiming "LTP scripts are written to be POSIX complaint" and now that I've shown you a not that uncommon IEEE POSIX 1003.2 compliant shell that can't cope with your non-POSIX script you suddenly introduce the word "relevant".

But when you care only about "relevant" shells you could simply implementing my suggestion of placing a #!/bin/bash at the top of your scripts instead of defining your own POSIX superset that you require from a /bin/sh for allowing a user to execute your script...

Quoted 1 line

-mike

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#7 lore raw
Quoted 51 lines · Adrian Bunk
Quoted 41 lines · Mike Frysinger
Quoted 40 lines · Adrian Bunk
Quoted 38 lines · Mike Frysinger
Quoted 29 lines · Adrian Bunk
Quoted 18 lines · Mike Frysinger
Quoted 8 lines · Rishikesh K. Rajak

Here i am getting failure on the x86_64 machine with new kernel.

Here is the uname for that machine:

rishi@:~/ltp-full-20071231# uname -a
Linux rishi.in.ibm.com 2.6.24 #1 SMP PREEMPT Mon Jan 28
06:47:28 UTC 2008 x86_64 GNU/Linux

i'm guessing you're using ubuntu and thus dash is your /bin/sh ... shouldnt be a 2.6.24 issue

Quoted 4 lines

make[4]: Entering directory `/root/ltp-full-20071231/testcases/network/tcp_cmds/ftp' ../../generate.sh
../../generate.sh: 60: arith: syntax error: "cnt=cnt-1"

Quoted 9 lines

sadly, this is becoming a FAQ. ubuntu ships a broken /bin/sh (dash) and thus some LTP scripts fall apart. i would prefer to not change the scripts as the message is simple in LTP: fix your shell, dont add hacks to LTP. otherwise we slowly back ourselves into this corner with the shell scripts where we try to support every craptastic shell out there and we're afraid to make any changes because we dont know what crappy shell is going to drop a brick. LTP scripts are written to be POSIX complaint and only POSIX complaint shells should be provided by /bin/sh.

Quoted 4 lines

You better fulfil your claim "LTP scripts are written to be POSIX complaint" before complaining about shells being unhappy with your script. E.g. where in IEEE 1003.1-2004 is the "local" you use specified?

yes, local is a bsd extension not in POSIX. it has been implemented by every shell so far though. as soon as someone complains, i'll be more than happy to fix it.

Quoted 8 lines
Quoted 2 lines

David Korn's ksh93 (e.g. shipped in the Debian "ksh" package) disproves your claim "it has been implemented by every shell so far".

sorry, i left out the operative word "relevant". i dont care what random shell fails unless people are actually utilizing it as their /bin/sh in any sort of useful context. as soon as someone complains for real and not just to be annoying, i'll address their complaint then.
...

Quoted 4 lines

You started with claiming "LTP scripts are written to be POSIX complaint" and now that I've shown you a not that uncommon IEEE POSIX 1003.2 compliant shell that can't cope with your non-POSIX script you suddenly introduce the word "relevant".

what's your point ? LTP scripts are POSIX compliant with a little extra that so far has worked fine for everyone actually running LTP. as soon as the little extra realistically becomes a problem, i'll rework things. you havent shown a realistic system. i'm willing to tweak things for real LTP users, not people being tools.

Quoted 4 lines

But when you care only about "relevant" shells you could simply implementing my suggestion of placing a #!/bin/bash at the top of your scripts instead of defining your own POSIX superset that you require from a /bin/sh for allowing a user to execute your script...

no. people run LTP on embedded systems w/out bash. -mike