Hello,

On Tue, Sep 25, 2012 at 02:31:40AM +0100, Ken Moffat wrote:
>  I'm reworking my own buildscripts to get better logging of what was
> installed.  For some time, my attempts to use 'find ... -newer' have
> been giving me dubious results : not only omitting files,
> particularly headers, which were installed with old dates, but also
> repeating files from the previous package.  At one time I altered my
> scripts to cope with what was being recorded in error (sleep after
> touching hte marker), but although that seemed to work for a little
> while, the problem soon resurfaced and it looks as if that approach
> is a loser's game.
> 
>  So, I decided to try DESTDIR and friends.  I've added su-tools from
> old coreutils to the end of chapter 5. In chapter 6 I'm building as
> root and then doing a DESTDIR install as someone else (lfs) to ensure
> that DESTDIR will be respected), but keep hitting EPERM problems.
> Should I just build as a regular user, then chown the tree to root
> before installing (i.e. deviate even further from the BOOK) ?
> 
>  My current feeling is that trying to log what gets installed might
> not be worth the effort.  For the moment, I've given up on
> install_root in chapter 6 glibc - worked fine in chapter 5, but
> fails in chapter 6 with
> ../o-iterator.mk:9: *** empty variable name.  Stop.
> make[1]: *** [locale/subdir_lib] Error 2
> make: *** [install] Error 2
> 
>  Might be me, or might be a bad patchset for bash, or a glibc
> problem - I've given up on that part for the moment so that I can
> see what else breaks, and I'm now at the "well pissed off" stage.
> 
>  Anyone got any words of encouragement, or should I just write this
> off ?  At least in BLFS the packages are, in the book, built as a
> user, even though some don't respect DESTDIR and at least one still
> needs root permissions during a DESTDIR install for chown or similar.
> 
> ĸen

The approach I took was to install into DESTDIR (and etc) and then use
dpkg to keep track of things.  However, I differ from your approach, in
that I do that as root.  Not as safe, perhaps, but I've not run into the
errors you have mentioned when working as root.

Keep at it, I think you'll find a solution. :)

Andrew

-- 
My Blog: http://elian001.wordpress.com
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to