On 07/29/2010 09:33 PM, Drew Ames wrote: > Timothy Rice wrote: > >> > Hi Drew, >> > >> >>> >> I had a problem right at the end when trying to install the >>> >> locales I got this error: >>> >> >>> >> /usr/bin/bash: /usr/bin/localedef: No such file or directory >>> >> > >> > I seem to recall running into similar problems. If I recall correctly, you >> > might be able to fix the problem by making /usr/bin/localedef an install >> > directory: >> > >> > chgrp install /usr/bin/localedef&& chmod 1775 /usr/bin/localedef >> >> >> Thanks for the tip! I'm going to start over this weekend (sort of, I >> saved my /tools, so I'd like to salvage what I have before I really >> start over). I'll post my results here along with some more detailed >> information. >> >> How do you like using package users? Have you built anything beyond >> LFS with package users? >> Drew, welcome to the world of torn hair, kicked cats and alienated wives [girlfriends]. The "More Control and Package Users" scheme can be totally--I mean totally--frustrating. But once you're used to it, it's pretty good. You really know, or can find out quickly, what's happening in the deep, dark recesses of your machine. I have built six basic LFS systems with it--including a CLFS one--and three desktop equipped systems complete with all the "bells and whistles." Although I'm getting advanced in years and my memory might be failing, I think it's safe to say that once you've build a basic, bootable LFS system, you've encountered all the "speed bumps" package users with throw your way. It's just a matter of experience and learning.
LFS has really changed since that hint was last updated, but if you can use the "core" of the system, you can adapt to all the changes. There is one that I must mention right off the bat. In the first paragraph of Section 6, "Pre-Chroot Phase (Chapter 5), it says to run the command cp src/su /tools/bin because Coreutils doesn't install su if you're installing as an unprivileged user. It also discusses "setuid." In the LFS book now, it tells you to install 'su' as 'su-tools.' I did that and ran into trouble with the wrapper scripts. So I created a symlink 'su' pointing at su-tools. The purpose was to satisfy the book and the hint without changing anythin in either. Now to your current situation. Unless you're having more troubles with your build than you have indicated, starting over in this case might be a little drastic. Of course, it's up to you. I recommend that you "comb" through you install log for glibc and see if you really can find the source of the error. I have a hunch, but "I ain't tellin'" If I'm right I'll let you know, but I want YOU to find it. Please re-read Sections 4, 5.2 and the glibc discussion in Section 6. The key of the latter discussion is: *find the first error.* In my experience, the most common cause of failed builds in package users is "install directories." Here's another hint: it may not be the directory you can't write to. I do like package users. I don't want anything more in package management than it provides. Plus it gives me info on everything I've installed. Need to tell the complete story here. Currently I got frustrated with the testing errors generated in glibc and used jhalfs to to my basic build. I'm moving on with package users. My install of glibc went well, I thought. I'd never, never,never had any unexpected testing failures in the toolchain before. Now that you've mentioned a problem, maybe I gave up too soon. Maybe, I should just try again and resolve it. Thanks for the insight. Please post the results of your research. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
