Errors in glibc testsuite in section 6.9

2007-03-01 Thread Thomas Tutone
I get errors running the glibc-2.3.6 testsuite in section 6.9 of Version 6.2 of the LFS book: # grep Error glibc-check-log make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) make[2]: *** [/sources/glibc-build/nptl/tst-cancel17.out] Error 1 make[2]: *** [/sources/glibc-build/nptl/t

Re: 6.2 Boot Failure: Populating /dev with device nodes

2007-03-01 Thread Colin Kemp
On Mar 1, 2007, at 6:58 PM, David A. Gershman wrote: > (also posted on LinuxQuestions.org in LFS Forum) > > Hello, this is a continuation from a thread on the Linux Kernel forum. > > I've got my drive being recognized by the kernel, but the system still > won't boot. It results in an error statin

6.2 Boot Failure: Populating /dev with device nodes

2007-03-01 Thread David A. Gershman
(also posted on LinuxQuestions.org in LFS Forum) Hello, this is a continuation from a thread on the Linux Kernel forum. I've got my drive being recognized by the kernel, but the system still won't boot. It results in an error stating: Checking file systems /dev/hda3: Superblock could not be read

Re: DVD Playback problems

2007-03-01 Thread Nik Davis
You can always see whether this key is available by just querying: > > $ sysctl dev.rtc.max-user-freq > dev.rtc.max-user-freq = 1024 > > -- > Dan that gives me the same message: error: "dev.rtc.max-user-freq" is an unknown key or :P cat /proc/driver/rtc should give you something like... r

Re: Retrieving Packages from LiveCD after chroot

2007-03-01 Thread Dan Nicholson
On 3/1/07, Colin Kemp <[EMAIL PROTECTED]> wrote: > > On Mar 1, 2007, at 3:46 PM, John Rodenbiker wrote: > > > I'm building LFS 6.2-3 from the Live CD to an i686-compatible > > platform. > > > > Throughout section 5 I was copying tarballs and patches to $LFS/ > > sources > > as needed. > > > next ti

Re: Retrieving Packages from LiveCD after chroot

2007-03-01 Thread Colin Kemp
On Mar 1, 2007, at 3:46 PM, John Rodenbiker wrote: > I'm building LFS 6.2-3 from the Live CD to an i686-compatible > platform. > > Throughout section 5 I was copying tarballs and patches to $LFS/ > sources > as needed. > next time remember that it did say to put all the sources in the source

Building software as an unprivileged user

2007-03-01 Thread Brian
Please could someone spell out the reason for building software as an unprivileged user? This is recommended in the BLFS book and elsewhere (though not in LFS), but I can't find a full explanation. If running 'make' as root could (accidentally? maliciously?) trash my system, doesn't the same

Re: chroot.libgcc

2007-03-01 Thread gerhardRamsebner
Ken Moffat: On Tue, Feb 27, 2007 at 10:06:27PM +0100, Ramsebner Gerhard wrote: Hi, Hi, any chance you can fix your mailer? (You claim to be <[EMAIL PROTECTED]>). I got stuck with glibc in chapter 6 of LFS6.2. I'm running a copy of LFS6.1 from another machine with an default.config kernel

Re: Where to unpack for section 6

2007-03-01 Thread John Rodenbiker
On Mar 1, 2007, at 2:25 PM, Alan Lord wrote: > John Rodenbiker wrote: >> I'm about the wade into Section 6 of LFS 6.2-3 but have a question: >> Where should I put and unpack the tarballs and patches? > > Once you have "chrooted" $LFS/sources will be /sources :-) > > Al Thank you. I realized this

Retrieving Packages from LiveCD after chroot

2007-03-01 Thread John Rodenbiker
I'm building LFS 6.2-3 from the Live CD to an i686-compatible platform. Throughout section 5 I was copying tarballs and patches to $LFS/sources as needed. I naively expected to do the same for section 6, but after mounting the CD under the chroot it looks like the sources are trapped in a file

Re: Where to unpack for section 6

2007-03-01 Thread Alan Lord
John Rodenbiker wrote: > I'm about the wade into Section 6 of LFS 6.2-3 but have a question: > Where should I put and unpack the tarballs and patches? > > In section 5 it was $LFS/sources. But having just reread section 6 I > don't see any suggestions for where to do this after the chroot. > > I

Re: Where to unpack for section 6

2007-03-01 Thread Ken Moffat
On Thu, Mar 01, 2007 at 02:18:08PM -0600, John Rodenbiker wrote: > I'm about the wade into Section 6 of LFS 6.2-3 but have a question: > Where should I put and unpack the tarballs and patches? > > In section 5 it was $LFS/sources. But having just reread section 6 I > don't see any suggestions for

Re: Where to unpack for section 6

2007-03-01 Thread veritosproject
On 3/1/07, John Rodenbiker <[EMAIL PROTECTED]> wrote: > I'm about the wade into Section 6 of LFS 6.2-3 but have a question: > Where should I put and unpack the tarballs and patches? $LFS/sources works just fine still. And once everything is installed, it's a good idea to leave them in /usr/src. --

Where to unpack for section 6

2007-03-01 Thread John Rodenbiker
I'm about the wade into Section 6 of LFS 6.2-3 but have a question: Where should I put and unpack the tarballs and patches? In section 5 it was $LFS/sources. But having just reread section 6 I don't see any suggestions for where to do this after the chroot. I'm working off the LiveCD onto an i68

Re: Keyboard stops working

2007-03-01 Thread Dan Nicholson
On 3/1/07, Tijnema ! <[EMAIL PROTECTED]> wrote: > On 2/28/07, Barius Drubeck <[EMAIL PROTECTED]> wrote: > > > Second thing: > > 1927 ?00:00:00 smbd > > 1932 ?00:00:00 smbd > > 1919 ?00:00:00 winbindd > > 1928 ?00:00:00 winbindd > > > > You seem to be running multiple

Re: ch6.9 glibc-2.5 configure error

2007-03-01 Thread William Harrington
On Mar 1, 2007, at 7:17 AM, nick bowes wrote: > > Thanks for the quick reply > I'm not sure but I think I ran gcc pass2 from the pass1 gcc-build > directory. > Could this be the cause of my problem? As for dummy.c, if I type > gcc -v > dummy.c in the gcc-build directory then I get a no such

Re: ch6.9 glibc-2.5 configure error

2007-03-01 Thread nick bowes
>> Hi there, >> running the configure command for glibc-2.5 ch 6.9 throws up the >> following error: >> >> - checking for C cleanup handling... no >> - configure: error: the compiler must support C cleanup handling >> >> It said I should checkout the "config.log" in the build dir in >> order to est