On Thu, Oct 4, 2012 at 9:41 PM, Bruce Dubbs <[email protected]> wrote: > Cory Cline wrote: > >>> Then test out the compound command with: >>> >>> 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 >>> done >>> >>> Work through it line by line to see where the problem is. > >> The error seems to be caused by the pushd $packagedir. Any ideas on >> what would be causing this? > > You don't say what the value of $packagedir is that fails. When you > extract the tarball with tar, the directory is created. > > You are using bash, right? > > -- Bruce > > --
I am indeed using bash. When is have the pushd commented out it outputs the names of all the directories that were untarred. I did verify that they are there and indeed expanded properly. However, here is an example error with pushd uncommented: "tar: xineramaproto-1.2.1.tar.bz2: cannot open: No such file or directory. tar: Error is not recoverable: exiting now. line 6: pushd: xineramaproto-1.2.1: No such file or directory > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
