Skip to contentSkip to conversation

problems compiling current CVS

DISCUSSION Paul Davis 3 participants 6 messages Jun 2, 2003 – Jun 3, 2003 3 messages not in the archive

lore
Share & tools
lore

Paul Davis

author
#0 lore raw

this is with CVS as of this morning (US EST), trying to build alsa-driver outside a 2.4.20 kernel using:

        ./cvscompile --with-oss=yes --with-sequencer=yes --with-cards=rme9652,hd

sp,trident

[ ... ]

ake[2]: Entering directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e/ioctl32'
make[2]: Leaving directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e/ioctl32'
make -C oss fastdep
make[2]: Entering directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/aco re/oss'
/bin/sh: ${xtmp:0:5}: bad substitution
make[2]: *** [mixer_oss.c] Error 1
make[2]: Leaving directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e/oss'
make[1]: *** [_sfdep_oss] Error 2
make[1]: Leaving directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e'
make: *** [dep] Error 1

-------------------------------------------------------
This SF.net email is sponsored by: eBay Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

author
#2 lore raw
In reply to a message not in the archive
Quoted 8 lines

This bit:

       ${xtmp:0:5}

is a Bash-ism. Normal Bourne shells don't understand this. I'm guessing that your system's /bin/sh isn't Bash. You might be able to put a

SHELL=/bin/bash

paul[2846]>which sh
/bin/sh
paul[2847]>ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Aug 16 2000 /bin/sh -> bash
paul[2852]>bash -version
GNU bash, version 1.14.7(1)

-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

#6 lore raw
In reply to a message not in the archive

Hmph. My SMTP server is not an open relay or a spam source, even if it is in an ADSL dynamic IP address pool, thank you very much. <bleep>ing spammers.

Let's try sending this to alsa-devel again ...

Quoted 30 lines · I wrote:

lundi, le 2 juin, 2003, Paul Davis nous a dit ceci:

Quoted 8 lines

this is with CVS as of this morning (US EST), trying to build alsa-driver outside a 2.4.20 kernel using:

        ./cvscompile --with-oss=yes --with-sequencer=yes --with-cards=rme9652,hd

sp,trident

[ ... ]

Quoted 8 lines

ake[2]: Entering directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e/ioctl32'
make[2]: Leaving directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/acor e/ioctl32'
make -C oss fastdep
make[2]: Entering directory `/usr/local/music/src/alsa-cvs/newer/alsa-driver/aco re/oss'
/bin/sh: ${xtmp:0:5}: bad substitution

Hmph. This syntax is in configure now too.

This bit:

        ${xtmp:0:5}

is a Bash-ism. Normal Bourne shells don't understand this. I'm guessing that your system's /bin/sh isn't Bash. You might be able to put a

SHELL=/bin/bash

Quoted 12 lines

line into alsa-driver/acore/oss/Makefile right before the include of $(TOPDIR)/Rules.make. (I say "might" because I can't build ALSA right now due to a (real) kernel compiler / system compiler mismatch.)

Alternatively, if you have root, you could temporarily replace /bin/sh with a symlink to /bin/bash, build, then restore /bin/sh.

Matt.

Signature · 3 lines
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
				-- Richard P. Feynman

-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

#8 lore raw
In reply to a message not in the archive

lundi, le 2 juin, 2003, Paul Davis nous a dit ceci:

Quoted 7 lines
Quoted 7 lines

This bit:

       ${xtmp:0:5}

is a Bash-ism. Normal Bourne shells don't understand this. I'm guessing that your system's /bin/sh isn't Bash. You might be able to put a

Quoted 8 lines
Quoted 1 line

SHELL=/bin/bash

paul[2846]>which sh
/bin/sh
paul[2847]>ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Aug 16 2000 /bin/sh -> bash
paul[2852]>bash -version
GNU bash, version 1.14.7(1)

Looks like I guessed wrong. The only system I still have access to with Bash 1.x on it isn't accessible right now, and the newer ones I do have access to don't say when the ${foo:0:5} syntax was added.

Dunno why it's not working. You might try bash2, viz.:

------------------------------------------------------------------------------
21:34 [clamat@ds0:~] 168 > /bin/bash -version GNU bash, version 2.04.0(1)-release (i586-pc-linux-gnu) Copyright 1999 Free Software Foundation, Inc. 21:35 [clamat@ds0:~] 169 > /bin/bash bash-2.04$ x=testvalue
bash-2.04$ echo ${x:0:5}
testv
bash-2.04$ exit
21:35 [clamat@ds0:~] 170 >
------------------------------------------------------------------------------

Matt.

Signature · 9 lines
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
				-- Richard P. Feynman


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
#3 lore raw
In reply to Paul Davis

At Mon, 02 Jun 2003 23:54:09 -0400,

Quoted 8 lines · Paul Davis
Quoted 8 lines

This bit:

       ${xtmp:0:5}

is a Bash-ism. Normal Bourne shells don't understand this. I'm guessing that your system's /bin/sh isn't Bash. You might be able to put a

Quoted 8 lines
Quoted 1 line

SHELL=/bin/bash

paul[2846]>which sh
/bin/sh
paul[2847]>ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Aug 16 2000 /bin/sh -> bash
paul[2852]>bash -version
GNU bash, version 1.14.7(1)

i'm not sure, too, whether bash1 doesn't support the format above. anyway, please try the patch attached below. it replaces the function with sed & co.

(unfortunately, we cannot use $(subst acore,core,$(MODCURDIR)) because
the word "acore" might match inside the pathname.)

Takashi

#4 lore raw

At Tue, 03 Jun 2003 11:54:01 +0200,

Quoted 21 lines · 私 wrote:

[1 <text/plain; US-ASCII (7bit)>]
At Mon, 02 Jun 2003 23:54:09 -0400,

Quoted 8 lines · Paul Davis
Quoted 8 lines

This bit:

       ${xtmp:0:5}

is a Bash-ism. Normal Bourne shells don't understand this. I'm guessing that your system's /bin/sh isn't Bash. You might be able to put a

Quoted 8 lines
Quoted 1 line

SHELL=/bin/bash

paul[2846]>which sh
/bin/sh
paul[2847]>ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Aug 16 2000 /bin/sh -> bash
paul[2852]>bash -version
GNU bash, version 1.14.7(1)

Quoted 3 lines

i'm not sure, too, whether bash1 doesn't support the format above. anyway, please try the patch attached below. it replaces the function with sed & co.

btw, the patch was already checked in to cvs.

Takashi

-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5