On 10/05/2012 12:14 PM, Cory Cline wrote:
[putolin]
>>> for package in $(grep -v '^#' ../proto-7.7.md5 | awk '{print $2}')
>>> do
>>> packagedir=${package%.tar.bz2}
>>> echo $packagedir $package
>>> #tar -xf $package
>>> #pushd $packagedir
>>> #./configure $XORG_CONFIG
>>> #$AS_ROOT make install
>>> #popd
>>> #rm -r $packagedir
[putolin]
>>>> Ok here goes:
>>>> $ tar -xf xineramaproto-1.2.1.tar.bz2
>>>> $ pushd xineramaproto-1.2.1.tar.bz2
Is the line above really
$ pushd xineramaproto-1.2.1.tar.bz2
or
$ pushd xineramaproto-1.2.1
What this is trying to do is to change directory to
xineramaproto-1.2.1.tar.bz2 which we should know ain't going to happen.
>>>> /sources/xc/proto/xineramaproto-1.2.1 /sources/sc/proto
>>>> $./configure $XORG_CONFIG
>>>> <CONFIG RUNS FINE>
>>>> $ popd
>>>> /sources/xc/proto
>>>> $ rm -r xineramaproto-1.2.1
>>>> <DIRECTORY REMOVES FINE>
>>>>
>>>> That seems to work just fine...
>>> Sorry for the double post, but I typed the loop into vim just to see
>>> if it shows any syntax errors, and in line 1 the $( and the matching )
>>> at the end are red backed.
>>>
>>> Also, in line 3 "%.tar.bz2" is red backed in the command
>>> packagedir=${package%.tar.bz2}
>>>
>>> Does that point to anything?
>> Well I ran the exact same script file this morning I had been all
>> along to recap on the errors and start fresh, and it worked. So thank
>> the gods, is there a way to mark this resolved? Thanks for your help
>> :)
> Well it only worked because I forgot to be in a bash -e
> shell.....might want to look into this further, When I realized that
> and ran it in the bash -e shell it has the same problem
>
OK so the shell exits on error, now we just need to find the command
returning the error
or returning something other than 0.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
