Am Samstag, 4. Januar 2014, 10:12:57 schrieb Bruce Dubbs: > Ken Moffat wrote: > > On Sat, Jan 04, 2014 at 12:46:56PM +0100, Thomas Trepl wrote: > >> Note that some BLFS instructions in the book needs some tweaks in order > >> to > >> work proper when installing via DESTDIR. Some packages do not take care > >> about DESTDIR but uses INSTALL_ROOT or even do not care about DESTDIR at > >> all. I needed only for 5 of over 400 packages a patch (rcs, unzip, zip, > >> xinetd and cdparanoia). For some other packages its a valid approach to > >> specify the destdir in the prefix-argument. That occurse mostly on > >> packages without a configure script where the install command looks like > >> "make prefix=/usr install". > >> > > For INSTALL_ROOT, or no available DESTDIR-style install, I've noted > > > > that in the wiki for some packages. > > > > In particular, anything using QT will probably need I_R instead of > > > > DESTDIR. NB - I only use the DESTDIR approach when looking at a new > > package, or when editing the book. There are also several packages > > which appear to respect DESTDIR but which do things requiring root > > privileges - only noticeable because if DESTDIR install fails, there > > are probably others where a DESTDIR install doesn't do everything > > but nevertheless ends successfully. > > I don't know what I_R is, but my approach is similar to Ken's, I only > use DESTDIR when checking things for the book. I almost always script > packages and do note issues. In some cases I find I need to create some > directories, e.g. $DESTDIR/lib, when the instructions call for moving > files around. Generally, the reason that packages need to be installed > in DESTDIR as root is because the Makefile wants to chown files during > install. > > -- Bruce
I think Ken did an abbreviation for INSTALL_ROOT. I did the DESTDIR stuff because I have severl machines which have different CPU power but same architecture. So I can compile the packages on the fastest of them and install the packages on every other without the need for recompiling. Thats simply what a distro basically does. Interesting enough which challanges came across on the way from the early packages like 'which' upto 'xorg', QT and KDE. Requiring root for 'make install' is an issue but it's seems to be very seldom. I think xorg-server was one of them. The build scripts needs to be extended with an sudo or something - thats the way I'll cover that. It's just fun to see something growing which has a little touch of an distro. But I know there are many challanges still ahead - dependency checking on the machine where the binaries got (un)installed is one example. Cool would be to have a cross-compiler installed on a fast 64bit box which then could create binaries for i686... -- Thomas -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
