Re: Help compiling Gcc (chap. 5.5)

2010-02-13 Thread Trent Shea
Hi, On Saturday 13 February 2010 22:06:20 Timothy Legg wrote: >tar -jxf ../mpfr-2.4.1.tar.bz2 > > I was never told which directory I was supposed to be in when I executed > this, but it might have been incorrect. > There's a note about this in: /lfs-6.5-book/chapter05/generalinstructions.

Help compiling Gcc (chap. 5.5)

2010-02-13 Thread Timothy Legg
Hello, First, thanks for creating this project. I have been looking for something like this for some time now. I am eager to show people this project once I get this to work for myself. * I am using version 6.5 of the book * All the software packages used are exact MD5SUM matches as in the boo

Re: /usr/lib/libstdc++.so: could not read symbols: File in wrong format

2010-02-13 Thread Simon Geard
On Sat, 2010-02-13 at 17:32 -0500, Baho Utot wrote: > Sorry for sending this here but I can not find the clfs support mailing > list, > Could someone point me to the correct place? Under "Mailing Lists", off the CLFS front page. http://trac.cross-lfs.org/wiki/lists Simon. signature.asc Descri

Re: Booting problems again

2010-02-13 Thread Simon Geard
On Sat, 2010-02-13 at 14:04 -0600, Mike McCarty wrote: > partitions. Like, /var, /tmp, /usr/local, /home are all > good candidates for being separate partitions. I like > for /tmp to be in a separate partition from /home, so > a user program which fills up /home/some-user/... doesn't > make /tmp al

/usr/lib/libstdc++.so: could not read symbols: File in wrong format

2010-02-13 Thread Baho Utot
From Book version 1.1.0-x86_64-multilib Section 6.4 GCC-4.2.4 Slackware 12.2 as the build system. I am getting this error on compiling x86_64-unknown-linux-gnu-c++ -shared -nostdlib /tools/lib/../lib64/crti.o /cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4/crtbeginS.o .libs/bitmap_al

Re: Booting problems again

2010-02-13 Thread Mike McCarty
Jan-Christoph Bornschlegel wrote: > Mike McCarty schrieb: > [...] >> I have studied the recommended layout (I can't recall what it's >> called, now) > > Maybe FHS? > http://www.pathname.com/fhs/ Yes, that's it! Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} Oppose gl

Re: Booting problems again

2010-02-13 Thread Jan-Christoph Bornschlegel
Mike McCarty schrieb: [...] > I have studied the recommended layout (I can't recall what it's > called, now) Maybe FHS? http://www.pathname.com/fhs/ Cheers, Jan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the abov

Re: Booting problems again

2010-02-13 Thread Mike McCarty
stosss wrote: > On Sat, Feb 13, 2010 at 2:21 PM, Mike McCarty > wrote: [...] >> I think that a general maintenace helper guide, or even a >> section in the book relating to that, giving considerations >> which enter into philosophy of maintenance and how to go >> about keeping a (B)LFS system up

Re: Booting problems again

2010-02-13 Thread stosss
On Sat, Feb 13, 2010 at 2:21 PM, Mike McCarty wrote: > Bruce Dubbs wrote: > > [...] > >> IMO, 750G is way too big for an LFS partition.  I store my BLFS sources >> on /usr/src which is a separate partition (50G, 50% full) and of course >> /home and /boot (100M) are separate so I can share them acr

Re: Booting problems again

2010-02-13 Thread Mike McCarty
Bruce Dubbs wrote: [...] > IMO, 750G is way too big for an LFS partition. I store my BLFS sources > on /usr/src which is a separate partition (50G, 50% full) and of course > /home and /boot (100M) are separate so I can share them across multiple > builds. Some people have /tmp and /opt as se

Re: lose data on shutdown?

2010-02-13 Thread Mike McCarty
Aleksandar Kuktin wrote: [...] > But make sure you do it properly - if your script is like this: > > # Begin my_script.sh > export LFS=/mnt/lfs > export FOO="blabla" > > Then simle `bash my_script.sh' won't help becouse the bash you just > ordered will fork a totally new process which will run

Re:

2010-02-13 Thread Jan-Christoph Bornschlegel
Mike McCarty schrieb: [...] > is used to encode the 8 bit character with hex code xx. > Since 0x3D is the code for "=", then "=3D" is the code > for "=". These substitutions are sometimes made by mailers > or even by machines in between. ... which teaches us: "don't copy/paste code snippets from e