Re: [lfs-support] glibc compilation error -- make[1]: *** [csu/subdir_lib] Error 2

2012-12-17 Thread JIA Pei
Thank you all.
After I reconfigure */bin/sh*, I now successfully built *glibc* .

sudo dpkg-reconfigure dash



Thank you all

Pei



On Sun, Dec 16, 2012 at 11:13 PM, Simon Geard delga...@ihug.co.nz wrote:

 On Sun, 2012-12-16 at 13:19 -0800, JIA Pei wrote:
 
  Hi, Michael:
 
 
  Thank you very much for your detailed reply, so clear !!
  My Host System Requirements gives me the following result:

 Note - that script isn't something you just run. It's something you have
 to actually read the output of, and see if everything is present and
 meets the requirements listed.

 In your case, it all looks good, with the exception of sh being a link
 to dash. The very first item on the requirements list has something to
 say about this...

 Simon.


 --
 http://linuxfromscratch.org/mailman/listinfo/lfs-support
 FAQ: http://www.linuxfromscratch.org/lfs/faq.html
 Unsubscribe: See the above information page




-- 

Pei JIA

Email: jp4w...@gmail.com
cell:+1 604-362-5816

Welcome to Vision Open
http://www.visionopen.com
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] LFS and updates

2012-12-17 Thread Simon Geard
On Sun, 2012-12-16 at 13:36 +0100, Jean-Philippe MENGUAL wrote:
 Hi,
 
 Yes, the book explains that for any major update of toolchain, all the
 system should be rebuilt. However, I would like your opinion for those
 who use lfs everyday.
 
 My plan is as follows: building lfs on sda1, then blfs on sda2, mounted
 in /usr/local.

Be careful with that. Just because you've built everything with
--prefix=/usr/local, doesn't mean everything ended up there. In
particular, watch for stuff ending up in /etc and /var, as many packages
assume those locations are valid unless explicitly overridden with
--sysconfdir and --localstatedir...


 I can't believe everyone on lfs rebuild all his system at each update.
 Rebuilding some part, yes; but all the blfs system...

Living with LFS is a great way to learn advanced shell scripting... :)

Simon.


signature.asc
Description: This is a digitally signed message part
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] keyboard-1.15.3 errors on backspace with uk keymap

2012-12-17 Thread Richard Melville
 On Sat, Dec 15, 2012 at 01:00:38PM +, Richard Melville wrote:
 When I use backspace in the terminal/console and then re-type I get white
 blocking.  I'm fairly sure that I installed the patches when I built the
 keyboard package.  Any advice?  It's really annoying.

 Richard

 I suppose white blocks might be a result of a console font which
 cannot display the glyph it was asked for.  In a unicode font, that
 situation ought to show an inverse question mark (black-on-white for
 normally white-on-black text), but many fonts cannot do that.

 However, that doesn't explain why the backspace isn't effective.
 The backspace patch only changes this for a few keymaps which still
 gave Backspace instead of Delete - the last time I looked (some
 time before 1.15.3, so something might have slipped in), all of
 the other keymaps shipped in the package already did this.

 What do you have in /etc/sysconfig/console ?

 ?en

Ken -- thanks for the reply.  I changed the font setting over the weekend
and now it seems to be OK.  The problem was the following: typing worked
OK, and if I made a typo and wanted to delete with the backspace key,
deletion worked OK, however, when I began to type again that's when I saw
the white blocking.

I know very little about fonts, keymaps, unicode, etc.  What I would like
to do is set up a unicode environment but I'm not sure how to go about it,
although I'll probably only be using an accented e, an umlaut/diaeresis,
and a euro symbol in addition to a uk keymap.  The following are the
console parameters of /etc/sysconfig/rc.site (I'm not using
/etc/sysconfig/console) and I've left my original font setting in, but
commented out:-

# Console parameters
UNICODE=0
KEYMAP=uk
#KEYMAP_CORRECTIONS=euro2
#FONT=default8x16
FONT=lat1-16 -m 8859-1
#LEGACY_CHARSET=

Thanks for your help.

Richard
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


[lfs-support] Is it a must to separate Binutils and GCC into Pass 1 and Pass 2?

2012-12-17 Thread JIA Pei
Hi, all;

Sorry to bug all of you again.
I've successfully built
Binutils  2.23.1
GCC   4.7,2
Linux-kernel   3.6.10
Glib   2.16.0

However, is it a must for me to proceed to the pass 2 of binutils and gcc?

I'm now following Pass 2 of Binutils 
http://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass2.html

the following step
*CC=$LFS_TGT-gcc\*
*AR=$LFS_TGT-ar \*
*RANLIB=$LFS_TGT-ranlib \*
*../binutils-2.22/configure \*
*--prefix=/tools\*
*--disable-nls  \*
*--with-lib-path=/tools/lib*

brings me error messages:

*lfs@peijia-GA-870A-UD3:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc
 \*
* AR=$LFS_TGT-ar \*
* RANLIB=$LFS_TGT-ranlib \*
* ../binutils-2.23.1/configure \*
* --prefix=/tools\*
* --disable-nls  \*
* --with-lib-path=/tools/lib*
*checking build system type... i686-pc-linux-gnu*
*checking host system type... i686-pc-linux-gnu*
*checking target system type... i686-pc-linux-gnu*
*checking for a BSD-compatible install... /usr/bin/install -c*
*checking whether ln works... yes*
*checking whether ln -s works... yes*
*checking for a sed that does not truncate output... /bin/sed*
*checking for gawk... gawk*
*checking for gcc... i686-lfs-linux-gnu-gcc*
*checking for C compiler default output file name... a.out*
*checking whether the C compiler works... configure: error: in
`/mnt/lfs/sources/binutils-build':*
*configure: error: cannot run C compiled programs.*
*If you meant to cross compile, use `--host'.*
*See `config.log' for more details.*


So, my question now is: is Pass 2 of binutils a must??



Cheers
Pei


-- 

Pei JIA

Email: jp4w...@gmail.com
cell:+1 604-362-5816

Welcome to Vision Open
http://www.visionopen.com
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Is it a must to separate Binutils and GCC into Pass 1 and Pass 2?

2012-12-17 Thread Chris Staub
On 12/17/2012 06:00 AM, JIA Pei wrote:

 Hi, all;

 Sorry to bug all of you again.
 I've successfully built
 Binutils  2.23.1
 GCC   4.7,2
 Linux-kernel   3.6.10
 Glib   2.16.0

 However, is it a must for me to proceed to the pass 2 of binutils and gcc?

Whatever is in the book is there for a reason.

 I'm now following Pass 2 of Binutils 
 http://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass2.html

 the following step
 /CC=$LFS_TGT-gcc\/
 /AR=$LFS_TGT-ar \/
 /RANLIB=$LFS_TGT-ranlib \/
 /../binutils-2.22/configure \/
 /--prefix=/tools\/
 /--disable-nls  \/
 /--with-lib-path=/tools/lib/

 brings me error messages:

 /lfs@peijia-GA-870A-UD3:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc
 \/
 / AR=$LFS_TGT-ar \/
 / RANLIB=$LFS_TGT-ranlib \/
 / ../binutils-2.23.1/configure \/
 / --prefix=/tools\/
 / --disable-nls  \/
 / --with-lib-path=/tools/lib/
 /checking build system type... i686-pc-linux-gnu/
 /checking host system type... i686-pc-linux-gnu/
 /checking target system type... i686-pc-linux-gnu/
 /checking for a BSD-compatible install... /usr/bin/install -c/
 /checking whether ln works... yes/
 /checking whether ln -s works... yes/
 /checking for a sed that does not truncate output... /bin/sed/
 /checking for gawk... gawk/
 /checking for gcc... i686-lfs-linux-gnu-gcc/
 /checking for C compiler default output file name... a.out/
 /*checking whether the C compiler works... configure: error: in
 `/mnt/lfs/sources/binutils-build':*/
 /*configure: error: cannot run C compiled programs.*/
 /If you meant to cross compile, use `--host'./
 /See `config.log' for more details./


 So, my question now is: is Pass 2 of binutils a must??

You are clearly having great difficulty. For one thing, you claim you 
are following the stable book but you are using versions from the latest 
development, and obviously that is not working well, and of course that 
doesn't take into account whatever other deviations from the book that 
you might be doing that you haven't mentioned. Solution: rm -rf 
$LFS/tools, go back to page 1, actually *read* every word in each page 
of the book, not just the commands (as most of your questions so far 
have in fact been answered right in the book itself), and do exactly as 
instructed, including the correct package versions.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] keyboard-1.15.3 errors on backspace with uk keymap

2012-12-17 Thread Ken Moffat
On Mon, Dec 17, 2012 at 10:56:28AM +, Richard Melville wrote:
 
 Ken -- thanks for the reply.  I changed the font setting over the weekend
 and now it seems to be OK.  The problem was the following: typing worked
 OK, and if I made a typo and wanted to delete with the backspace key,
 deletion worked OK, however, when I began to type again that's when I saw
 the white blocking.
 
 I know very little about fonts, keymaps, unicode, etc.

 These days, few people know much about screen fonts and keymaps.

  What I would like
 to do is set up a unicode environment but I'm not sure how to go about it,
 although I'll probably only be using an accented e, an umlaut/diaeresis,
 and a euro symbol in addition to a uk keymap.  The following are the
 console parameters of /etc/sysconfig/rc.site (I'm not using
 /etc/sysconfig/console) and I've left my original font setting in, but
 commented out:-
 
 # Console parameters
 UNICODE=0

 You seem to have have turned unicode off.  I can't really comment
on how the other settings play in a legacy environment.  When you set
it to '1' you might need to alter your profile to ensure you are
using a UTF-8 version of LC_ALL or whatever (en_GB.UTF-8 for most
people in the UK).

 KEYMAP=uk

 I used to use that - worked ok, but I wanted more :)

 #KEYMAP_CORRECTIONS=euro2
 #FONT=default8x16
 FONT=lat1-16 -m 8859-1

 Those are both 256 character fonts, I would say that the coverage
of lat1-16 is slightly better (in a unicode environment).  If you
don't need the bright colours, you might prefer a 512 character
font.

 I've got a few files at http://www.linuxfromscratch.org/~ken/
in the keyboard-items and fonts directories - note that
LatGrkCyr-8x16 is a 512-ish character font and ships in kbd.  It
comes from the sigma fonts there which are very much roll your
own but do allow a 256 character font if that is what you need.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Is it a must to separate Binutils and GCC into Pass 1 and Pass 2?

2012-12-17 Thread JIA Pei
Hi, Thanks Chris:

Thank you for your prompt reply.

Unfortunately, the reason why I'm using the latest version of Binutils is
deu to the current wget-list:
http://www.linuxfromscratch.org/lfs/view/development/wget-list
On this list, binutils-2.23.1 is used
http://ftp.gnu.org/gnu/binutils/binutils-2.23.1.tar.bz2
instead of binutils-2.22 .

However, on the book, it's still using binutils-2.22
http://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass1.html


I did notice for binutils-2.22 pass 1, there is a patch before everything
starts compiling.

patch -Np1 -i ../binutils-2.22-build_fix-1.patch


However, I've got no idea whether this patch for binutils-2.22 is also
working for binutils-2.23.1 ?


Anyway, now, my question is:   *is the patch a must?*
Why didn't I meet any error message even without patching binutils during
binutils Pass 1?


Thanks again. I do need your detailed explanation. Thank you very much
again.


Cheers
Pei




On Mon, Dec 17, 2012 at 3:15 AM, Chris Staub ch...@beaker67.com wrote:

 On 12/17/2012 06:00 AM, JIA Pei wrote:
 
  Hi, all;
 
  Sorry to bug all of you again.
  I've successfully built
  Binutils  2.23.1
  GCC   4.7,2
  Linux-kernel   3.6.10
  Glib   2.16.0
 
  However, is it a must for me to proceed to the pass 2 of binutils and
 gcc?

 Whatever is in the book is there for a reason.
 
  I'm now following Pass 2 of Binutils 
 
 http://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass2.html
 
  the following step
  /CC=$LFS_TGT-gcc\/
  /AR=$LFS_TGT-ar \/
  /RANLIB=$LFS_TGT-ranlib \/
  /../binutils-2.22/configure \/
  /--prefix=/tools\/
  /--disable-nls  \/
  /--with-lib-path=/tools/lib/
 
  brings me error messages:
 
  /lfs@peijia-GA-870A-UD3:/mnt/lfs/sources/binutils-build$ CC=$LFS_TGT-gcc
  \/
  / AR=$LFS_TGT-ar \/
  / RANLIB=$LFS_TGT-ranlib \/
  / ../binutils-2.23.1/configure \/
  / --prefix=/tools\/
  / --disable-nls  \/
  / --with-lib-path=/tools/lib/
  /checking build system type... i686-pc-linux-gnu/
  /checking host system type... i686-pc-linux-gnu/
  /checking target system type... i686-pc-linux-gnu/
  /checking for a BSD-compatible install... /usr/bin/install -c/
  /checking whether ln works... yes/
  /checking whether ln -s works... yes/
  /checking for a sed that does not truncate output... /bin/sed/
  /checking for gawk... gawk/
  /checking for gcc... i686-lfs-linux-gnu-gcc/
  /checking for C compiler default output file name... a.out/
  /*checking whether the C compiler works... configure: error: in
  `/mnt/lfs/sources/binutils-build':*/
  /*configure: error: cannot run C compiled programs.*/
  /If you meant to cross compile, use `--host'./
  /See `config.log' for more details./
 
 
  So, my question now is: is Pass 2 of binutils a must??

 You are clearly having great difficulty. For one thing, you claim you
 are following the stable book but you are using versions from the latest
 development, and obviously that is not working well, and of course that
 doesn't take into account whatever other deviations from the book that
 you might be doing that you haven't mentioned. Solution: rm -rf
 $LFS/tools, go back to page 1, actually *read* every word in each page
 of the book, not just the commands (as most of your questions so far
 have in fact been answered right in the book itself), and do exactly as
 instructed, including the correct package versions.
 --
 http://linuxfromscratch.org/mailman/listinfo/lfs-support
 FAQ: http://www.linuxfromscratch.org/lfs/faq.html
 Unsubscribe: See the above information page




-- 

Pei JIA

Email: jp4w...@gmail.com
cell:+1 604-362-5816

Welcome to Vision Open
http://www.visionopen.com
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


[lfs-support] Booting LFS Error Kernel Panic

2012-12-17 Thread Alexander Spitzer
Hello all,

I am having a hard time booting my LFS system, which is on a USB drive. I
installed grub on /dev/sdc (the usb relative to the host) and the bios
successfully finds GRUB. After around 2.3 seconds, the boot process hangs
after printing what I believe to be a trace call. Interestingly, one time
when I booted the trace call was short enough for me to write down the
error which I can't normally see due to the length of the trace prints.
Here is the error:

Kernel panic-not syncing: VFS: Unable to mount root fs on unknown block(0,0)

What exactly does unknown block(0,0) mean?

The problem appears to be that the kernel can't find the root file system.
How can that be a problem, if the kernel, which is ON the root file system,
was found and ran?
Here is the grub.cfg file:
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5

insmod ext2
set root=(hd0,1)

menuentry GNU/Linux, Linux 3.7-lfs-SVN-20121212 {
linux   /boot/vmlinuz-3.7-lfs-SVN-20121212 root=/dev/sda1 ro
}

I believe the USB is always sda because to boot I do a manual boot override
and select USB from the BIOS menu. The grub command line also confirms this.

Searching online, there were some suggestions that the kernel was compiled
without support for necessary file systems and hardware. I check my config
file for the kernel and found all the important options to be set to yes
(USB_mass_storage, ext3 filesystem, USB UHCI, USB OHCI, and several scsi
ones). There are however many USB options that are not set. Are there any
specific ones that should be set for the kernel to load the root filesystem?

Also, I've tried unsuccessfully to read more of the boot output by two
methods: increasing the resolution and scrolling back. The scroll back
buffer is set to yes in the kernel config yet shift page down and shift
page up do nothing. Also, vga=791 is deprecated and I haven't been able to
get any effect by using set vgxpayload=1024x728.
How can I read the boot print outputs without a high speed camera?

Thanks,
Alex
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Booting LFS Error Kernel Panic

2012-12-17 Thread Alexander Spitzer
I got it to work! Turns out that the root file system changes to /dev/sdc1
after all the harddisks are found so changing the line root=/dev/sda1 to
root=/dev/sdc1 and adding a rootdelay successfully booted the system!

Now it would be nice for it to work using UUIDs so the booting can
be independent of host system.
Also, the scrollback buffer does work just not when the kernel has crashed.

I am sorry for the long kind of useless post but if anyone has anything to
add please feel free.

On Mon, Dec 17, 2012 at 5:24 PM, Alexander Spitzer aes...@cornell.eduwrote:

 Hello all,

 I am having a hard time booting my LFS system, which is on a USB drive. I
 installed grub on /dev/sdc (the usb relative to the host) and the bios
 successfully finds GRUB. After around 2.3 seconds, the boot process hangs
 after printing what I believe to be a trace call. Interestingly, one time
 when I booted the trace call was short enough for me to write down the
 error which I can't normally see due to the length of the trace prints.
 Here is the error:

 Kernel panic-not syncing: VFS: Unable to mount root fs on unknown
 block(0,0)

 What exactly does unknown block(0,0) mean?

 The problem appears to be that the kernel can't find the root file system.
 How can that be a problem, if the kernel, which is ON the root file system,
 was found and ran?
 Here is the grub.cfg file:
 # Begin /boot/grub/grub.cfg
 set default=0
 set timeout=5

 insmod ext2
 set root=(hd0,1)

 menuentry GNU/Linux, Linux 3.7-lfs-SVN-20121212 {
 linux   /boot/vmlinuz-3.7-lfs-SVN-20121212 root=/dev/sda1 ro
 }

 I believe the USB is always sda because to boot I do a manual boot
 override and select USB from the BIOS menu. The grub command line also
 confirms this.

 Searching online, there were some suggestions that the kernel was compiled
 without support for necessary file systems and hardware. I check my config
 file for the kernel and found all the important options to be set to yes
 (USB_mass_storage, ext3 filesystem, USB UHCI, USB OHCI, and several scsi
 ones). There are however many USB options that are not set. Are there any
 specific ones that should be set for the kernel to load the root filesystem?

 Also, I've tried unsuccessfully to read more of the boot output by two
 methods: increasing the resolution and scrolling back. The scroll back
 buffer is set to yes in the kernel config yet shift page down and shift
 page up do nothing. Also, vga=791 is deprecated and I haven't been able to
 get any effect by using set vgxpayload=1024x728.
 How can I read the boot print outputs without a high speed camera?

 Thanks,
 Alex

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Booting LFS Error Kernel Panic

2012-12-17 Thread Bruce Dubbs
Alexander Spitzer wrote:
 I got it to work! Turns out that the root file system changes to /dev/sdc1
 after all the harddisks are found so changing the line root=/dev/sda1 to
 root=/dev/sdc1 and adding a rootdelay successfully booted the system!

 Now it would be nice for it to work using UUIDs so the booting can
 be independent of host system.

You need to use an initrd of that.  See BLFS.

   -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page