Re: glibc doesn't like @ in current directory name

["Arno Schuring" <aelschuring at hotmail dot com>]

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

Show us! Show us! ;)

> 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'
> ...
[...]

Oooh...

> ("man ascii" shows char 156 is 'n', which isn't very helpful; maybe
>  that char is in the \1 backreference?!

wouldn't char 156: refer to the character at position 156 in the command 
line?

Then we have multiple options as to where the count starts...

- I would expect it to start at 's/[...]', but since that command is exactly 
155 characters long, the question is why sed points to the end of the 
command
- The \1 is exactly at position 156 if you start counting at "sed -n [...]"


> 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.

:D please do... I'm curious as to how they would react...

But seriously though, it's a good catch. They should've used a sed script to 
escape all the @'s in the substitution path :)


Arno

 np: Alan Parsons Project - Where Do We Go From Here 

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