glibc doesn't like @ in current directory name

[Daniel Kegel <dank at kegel dot com>]

Hey, kids, guess what happens if you try to build glibc
in a directory whose name contains '@'?  Let's watch:

sed -n 's@^/home/dkegel/queue/jobdir.foo@bar/crosstool-0.32/build/x86_64-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/build-glibc/\([^(]*\)(\([^)]*\.os\)) *.*$@\1 \2@p' \
...
sed: -e expression #1, char 156: unknown option to `s'
...
rtld-Rules:34: *** missing separatormake[3]: Leaving directory `/hda3/dkegel/queue/jobdir.foo@bar/crosstool-0.32/build/x86_64-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/glibc-2.3.3/elf'
.  Stop.
make[2]: *** [/home/dkegel/queue/jobdir.foo@bar/crosstool-0.32/build/x86_64-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/build-glibc/elf/rtld-libc.a] Error 2
make[2]: Leaving directory `/hda3/dkegel/queue/jobdir.foo@bar/crosstool-0.32/build/x86_64-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/glibc-2.3.3/elf'
make[1]: *** [elf/subdir_lib] Error 2
make[1]: Leaving directory `/hda3/dkegel/queue/jobdir.foo@bar/crosstool-0.32/build/x86_64-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.3/glibc-2.3.3'
make: *** [all] Error 2

("man ascii" shows char 156 is 'n', which isn't very helpful; maybe
 that char is in the \1 backreference?!
I wonder if sed could give a better diagnostic, like
 "too many separators: @ appears four times in -e expression #1")

I kind of feel like submitting a patch to glibc to
get it to abort early if the build directory name
would violate assumptions like this.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com