> From: Patrick Kennedy <[email protected]> > Date: Fri, 1 Aug 2014 14:50:18 +0800 > To: LFS Support List <[email protected]> > Subject: Re: [lfs-support] Please, teach me how to fix problems. > > > > > On Fri, Aug 1, 2014 at 2:34 PM, akhiezer <[email protected]> wrote: > > > > > > From: Michael Havens <[email protected]> > > > > Date: Thu, 31 Jul 2014 22:49:00 -0700 > > > > To: LFS Support List <[email protected]> > > > > Subject: Re: [lfs-support] Please, teach me how to fix problems. > > > > > > > > > > > > > > > > okay..... I tried scripting my compile with the following results: > > > > > > > > root:/sources# cat >6.9glibc <<"eof" > > > > > #6.9 glibc compile instructions > > > > > > > > > > sed -i 's/\\$$(pwd)/`pwd`/' timezone/Makefile > > > > > patch -Np1 -i ../glibc-2.19-fhs-1.patch > > > > > mkdir -v ../glibc-build > > > > > cd ../glibc-build > > > > > ../glibc-2.19/configure \ > > > > > --prefix=/usr \ > > > > > --disable-profile \ > > > > > --enable-kernel=2.6.32 \ > > > > > --enable-obsolete-rpc > > > > > make > > > > > make -k check 2>&1 | tee glibc-check-log > > > > > grep Error glibc-check-log > > > > > eof > > > > root:/sources# ./6.9glibc > > > > bash: ./6.9glibc: Permission denied > > > > root:/sources# > > > > > > > > Pray tell.... why is root getting a 'permission denied'? To tell you the > > > > truth I did this originally in gedit and then scp the file to /sources > > > but > > > > the resulting error was the same. > > > > > > > > > > > > > 'Pray tell': didst thou: > > > > > > chmod +x ./6.9glibc > > > > > > ? > > > > > > > > > But really, it's a good general rule of thumb that: don't try to script > > > your > > > build until you have built strictly by-the-book and strictly manually at > > > least once or a few times. (Likewise for any deviating from the book.) > > > > > > > > > IOW: don't try to run before you can walk. > > > > > > > > > At the risk of sounding blunt: if you're not recovering from the above > > > 'Permission denied' &c stuff by yourself, then you're maybe not quite at > > > the stage of scripting the build? > > > > > > > > > Really, building manually and by-the-book, _is_ good and useful > > > experience. > > > > > Each build is a stage. As test and verify live time what it works, > script-ify it in an editor. Then progressively, you'll have all your > stages validated and ready to go later. >
Yep, or even/additionally (just one of many approaches, of course: -- * 'set history=10000' (or whatever) in the respective environments (chroot/su/lfs/&c); * be disciplined about what tty/&c you're issuing commands in (to help ensure that the relevant history is getting everything you want); * periodically do e.g. 'history > "/tmp/hist.$(date '+%Y%m%d%H%M%S')" ' ; * be aware that of the saved history-lists will be in chroot, some not, some for user lfs, some for user root ; * be sure to periodically or at least at end, collect the saved history-lists into a single place. * use the history-lists as basis for scripts. -- akh p.s. BTW, is this 'STH' PK ? -- -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
