Useradd

2006-11-28 Thread Geoffrey Thomas
After a few keyboard issues, I now have a LFS system that boots without problems. I can login as root and cruise through directories and use basic commands. When I add a user with useradd, all the info goes into the /etc/ password and /etc/shadow files When I try to login to the new user, I ge

libncurses.so.5: file too short

2006-11-28 Thread Colin Dean
Well, I thought I had everything up and working (it booted, woot). However, I noticed that the first program to actually use libncurses--the kernel's menuconfig--was greatly distorted. Then, while trying to do something else (I can't remember now), I got this error: /lib/libncursesw.so.5: f

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread Luca
Just a note: The "-Xlinker" etc... can be passed to gcc, cc etc... however, example, on my lfs, obviously output this: [EMAIL PROTECTED]:~# cc -Wl,--hash-style=both dummy.c /usr/bin/ld: unrecognized option '--hash-style=both' /usr/bin/ld: use the --help option for usage information collect2: ld re

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread Luca
Amadeus wrote: > Hi, sorry for the idiot question, but how to pass --hash-style=both? I > tried editing /usr/lib/gcc/i386-redhat-linux/4.1.1/specs but gcc > -dumpspecs still show's hash-style=gnu. > > I'll post back to the list when all is well. > > Thanks > > Amadeus > Sorry if I repost the mail,

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread [EMAIL PROTECTED]
Sorry for replying only now: On Fedora Core 6: Let's take the dummy.c from the Adjusting the Toolchain phase: echo 'main(){}' > dummy.c cc dummy.c [EMAIL PROTECTED] ~]# readelf -l a.out Elf file type is EXEC (Executable file) Entry point 0x8048280 There are 7 program headers, starting at offs

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread Amadeus
Ok my mistake, after lots of rebuilding I "saw" that the dejagnu "make check" uses g++, which is the host version at this stage as LFS gcc-pass 1 only compiles gcc not g++... To sum up: host gcc (FC6) passes --hash-style=gnu to ld. When building binutils-pass1 this is fine as the host gcc and l

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread Luca
Luca wrote: > Hello and sorry for auto-introducing me in the thread. > > In some new systems as Fedora Core 6 gcc passes --hash-style=gnu to the > linker, which indeed is called with an option like > "--enable-new-ldflags" (which enables new linker flags). > The result is a DSO with ".gnu.hash" onl

Re: ld built without --hash-style, Ch5, Fedora Core 6 -> glibc config failure

2006-11-28 Thread Luca
Hello and sorry for auto-introducing me in the thread. In some new systems as Fedora Core 6 gcc passes --hash-style=gnu to the linker, which indeed is called with an option like "--enable-new-ldflags" (which enables new linker flags). The result is a DSO with ".gnu.hash" only so not including the

Autoconf make failure (looks like perl defaults NG)

2006-11-28 Thread Bill
Using Lfslivecd 2.6.16.28 on an empty machine. LFS stable 6.2 book instructions. Going well. In Chapter 6. Instructions in 6.22 (Perl-5.8.8) say run interactive Configure. I did that. Per "... if the defaults it auto-detects are suitable ..." I accepted all defaults. I then ran the "configure