On 10/05/2012 12:59 PM, Bruce Dubbs wrote:
> Cory Cline wrote:
>
>>> 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
> Try to trim your posts so only relevant info is included.
>
> Are you sure you didn't do 'bash -r'? The r is right next to the e on
> the keyboard and changing directories is not permitted in a restricted
> shell.
>
> Using bash -e works fine. At least no one else has had an issue and the
> construct has been there for quite some time.
>
> -- Bruce
>
>
>
I have just run this script, and it works.
But I must confess that I changed one line see below
for package in $(grep -v '^#' ../proto-7.7.md5 | awk '{print $2}')
do
packagedir=${package%.tar.bz2}
tar -xf $package
pushd $packagedir
./configure $XORG_CONFIG
make # changed this line to just make so I wouldn't corrupt my system
under build.
popd
rm -r $packagedir
done
I looks to me that his script may be baling on the make install?
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
