Re: Slightly OT: Building with a VM

2011-05-02 Thread Mike McCarty
me,apporc wrote:
 Hi
 Is there a book or someting like which i can refer to for these knowledge
 about disks , images files and partitions .

I use the man pages a lot.

 I don't know how to mount a partition in a image file with offset .I want to
 know detailed knowledge about this . I hope you can give me an advice.

Mike
-- 
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Brett
Hi

I am trying to build LFS SVN-20110427 on an AMD64 system

I get a consistent failure when running the checks for Binutils in 
chapter 6. This is the output where the error occurs:


Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-elf/shared.exp 
...
ERROR: /usr/src/binutils/binutils-2.21/ld/testsuite/ld-elf/new.cc: 
compilation failed
FAIL: Build libdnew1a.so with --Bsymbolic-functions 
--dynamic-list-cpp-new
ERROR: /usr/src/binutils/binutils-2.21/ld/testsuite/ld-elf/new.cc: 
compilation failed
FAIL: Build libdnew1b.so with --dynamic-list-data --dynamic-list-cpp-new
FAIL: Run with libnew1a.so
FAIL: Run with libnew1b.so
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-elf/tls_common.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-elf/wrap.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-elfcomm/elfcomm.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-elfvers/vers.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-elfvsb/elfvsb.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-elfweak/elfweak.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-fastcall/fastcall.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-frv/fdpic.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-frv/frv-elf.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-frv/tls.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-gc/gc.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-h8300/h8300.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-i386/i386.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-ia64/ia64.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-ia64/line.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-ifunc/binutils.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-ifunc/ifunc.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-libs/libs.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-linkonce/linkonce.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-m68hc11/m68hc11.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-m68k/m68k-got.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-m68k/m68k.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-mep/mep.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-mips-elf/mips-elf-flags.e
xp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-mips-elf/mips-elf.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-mmix/mmix.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-mn10300/mn10300.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-pe/pe-compile.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-pe/pe-run.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-pe/pe-run2.exp 
...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-pe/pe.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-pie/pie.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-plugin/plugin.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-powerpc/aix52.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-powerpc/powerpc.exp ...
Running /usr/src/binutils/binutils-2.21/ld/testsuite/ld-s390/s390.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/align.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/alignof.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/assert.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/crossref.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/data.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/default-script.ex
p ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/defined.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/dynamic-sections.
exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/empty-address.exp
 ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/empty-aligned.exp
 ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/empty-orphan.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/expr.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/extern.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/include.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/map-address.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/overlay-size.exp 
...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/phdrs.exp ...
Running 
/usr/src/binutils/binutils-2.21/ld/testsuite/ld-scripts/phdrs2.exp ...
Running 

Re: Error compiling Expect 5.45

2011-05-02 Thread DJ Lucas
On 05/01/2011 09:14 PM, Graham Beck wrote:


 /mnt/lfs/sources/expect5.45/libexpect5.45.so: undefined reference to
 `openpty@GLIBC_2.0'
 collect2: ld returned 1 exit status
 make: *** [expect] Error 1


Unfortunately, you've given just enough information for someone to 
determine that the linker exited with a generic error, and that it is 
fussing about libutil. The line immediately above the three you've sent, 
begins with 'gcc' (it should take up about 6 lines on an 80 column 
terminal), and immediately above that is a line that contains 'rm -f 
libexpect5.45.so'. You will need to send all 5 of those lines for 
somebody to make more than a guess about the cause of the issue.

-- DJ Lucas

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


Re: Error compiling Expect 5.45

2011-05-02 Thread Graham Beck
Oh, sorry - still finding my way here. Here is a fuller output:

i686-lfs-linux-gnu-gcc -B/tools/lib/ \
 -pipe -O2 -fomit-frame-pointer -Wall -fPIC  \
 -Wl,--export-dynamic  \
-o expect exp_main_exp.o \
-L/mnt/lfs/sources/expect5.45 -lexpect5.45 \
-L/tools/lib -ltcl8.5 \
-ldl  -lieee -lm \
-Wl,-rpath,/tools/lib \
-Wl,-rpath,/tools/lib/expect5.45
/mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.5.2/../../../../i686-lfs-linux-gnu/bin/ld:
warning: libutil.so.1, needed by
/mnt/lfs/sources/expect5.45/libexpect5.45.so, not found (try using
-rpath or -rpath-link)
/mnt/lfs/sources/expect5.45/libexpect5.45.so: undefined reference to
`openpty@GLIBC_2.0'
collect2: ld returned 1 exit status
make: *** [expect] Error 1


On Mon, May 2, 2011 at 10:28 AM, DJ Lucas d...@linuxfromscratch.org wrote:
 On 05/01/2011 09:14 PM, Graham Beck wrote:


 /mnt/lfs/sources/expect5.45/libexpect5.45.so: undefined reference to
 `openpty@GLIBC_2.0'
 collect2: ld returned 1 exit status
 make: *** [expect] Error 1


 Unfortunately, you've given just enough information for someone to
 determine that the linker exited with a generic error, and that it is
 fussing about libutil. The line immediately above the three you've sent,
 begins with 'gcc' (it should take up about 6 lines on an 80 column
 terminal), and immediately above that is a line that contains 'rm -f
 libexpect5.45.so'. You will need to send all 5 of those lines for
 somebody to make more than a guess about the cause of the issue.

 -- DJ Lucas

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

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


Re: Error compiling Expect 5.45

2011-05-02 Thread Graham Beck
... and I've just found the 'rm -f libexpect5.45.so' line above that
DJ Lucas mentioned was needed. So here's the necessary output:

rm -f libexpect5.45.so
i686-lfs-linux-gnu-gcc -B/tools/lib/ -shared -pipe -O2
-fomit-frame-pointer -Wall -fPIC  -Wl,--export-dynamic  -o
libexpect5.45.so exp_command.o expect.o exp_inter.o exp_regexp.o
exp_tty.o exp_log.o exp_main_sub.o exp_pty.o exp_trap.o exp_strf.o
exp_console.o exp_glob.o exp_win.o exp_clib.o exp_closetcl.o
exp_memmove.o exp_tty_comm.o exp_chan.o Dbg.o pty_termios.o
exp_select.o exp_event.o -lutil -lieee -lm -Wl,-rpath,/tools/lib
-L/tools/lib -ltclstub8.5
: libexpect5.45.so
i686-lfs-linux-gnu-gcc -B/tools/lib/ -DPACKAGE_NAME=\expect\
-DPACKAGE_TARNAME=\expect\ -DPACKAGE_VERSION=\5.45\
-DPACKAGE_STRING=\expect\ 5.45\ -DPACKAGE_BUGREPORT=\\
-DBUILD_expect= -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1
-DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1
-D_THREAD_SAFE=1 -DTCL_THREADS=1 -DMODULE_SCOPE=extern\
__attribute__\(\(__visibility__\(\hidden\\)\)\)
-D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long
-DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1
-DHAVE_TYPE_OFF64_T=1 -DUSE_TCL_STUBS=1 -DUSE_TCL_STUBS=1
-DHAVE_SYS_SELECT_H=1 -DHAVE_SYSMACROS_H=1 -DHAVE_STROPTS_H=1
-DHAVE_SYS_FCNTL_H=1 -DRETSIGTYPE=void -DHAVE_SYS_TIME_H=1
-DTIME_WITH_SYS_TIME=1 -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1
-DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1
-DHAVE_TIMEZONE_VAR=1 -DHAVE_OPENPTY=1 -DHAVE_MEMMOVE=1
-DHAVE_SYSCONF=1 -DHAVE_STRFTIME=1 -DHAVE_STRCHR=1 -DHAVE_TIMEZONE=1
-DHAVE_SIGLONGJMP=1 -DHAVE_MEMCPY=1 -DWNOHANG_BACKUP_VALUE=1
-DSELECT_MASK_TYPE=fd_set -DHAVE_PTMX=1 -DHAVE_TCSETATTR=1 -DPOSIX=1
-DHAVE_TERMIO=1 -DHAVE_TERMIOS=1 -DSETPGRP_VOID=1 -DHAVE_SV_TIMEZONE=1
-DHAVE_LONG_FILE_NAMES=1  -DTCL_DEBUGGER -DUSE_NON_CONST
-DSCRIPTDIR=\/tools/lib/expect5.45\
-DEXECSCRIPTDIR=\/tools/lib/expect5.45\ -DSTTY_BIN=\/bin/stty\
-DDFLT_STTY=\sane\ -I. -I. -I/tools/include-pipe -O2
-fomit-frame-pointer -Wall -fPIC  -c `echo exp_main_exp.c` -o
exp_main_exp.o
i686-lfs-linux-gnu-gcc -B/tools/lib/ \
-pipe -O2 -fomit-frame-pointer -Wall -fPIC  \
-Wl,--export-dynamic  \
   -o expect exp_main_exp.o \
   -L/mnt/lfs/sources/expect5.45 -lexpect5.45 \
   -L/tools/lib -ltcl8.5 \
   -ldl  -lieee -lm \
   -Wl,-rpath,/tools/lib \
   -Wl,-rpath,/tools/lib/expect5.45
/mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.5.2/../../../../i686-lfs-linux-gnu/bin/ld:
warning: libutil.so.1, needed by
/mnt/lfs/sources/expect5.45/libexpect5.45.so, not found (try using
-rpath or -rpath-link)
/mnt/lfs/sources/expect5.45/libexpect5.45.so: undefined reference to
`openpty@GLIBC_2.0'
collect2: ld returned 1 exit status
make: *** [expect] Error 1
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: setclock Question (lfs-bootscripts-20110424)

2011-05-02 Thread alupu
May 1, 2011 12:12:01 AM, neal.p.murphy  wrote.

Hi Neil,

Thank you very much for your comments.
I'm trying to comment on your comments now.

Alex said:
 '/lib/udev/rules.d/50-udev-default.rules':
 SUBSYSTEM==rtc, DRIVERS==rtc_cmos, SYMLINK+=rtc
 FWIW, I don't see the relevance of rule 50-udev

Neil said:
 The rule in 50-udev creates the symlink '/dev/rtc' to
 the actual node '/dev/rtc0'.
 It isn't relevant to the clock being set or not being set.

Alex is saying:
 1.  On all my queries, there's NO 'SUBSYSTEM==rtc'.
 To reinforce to the readers (in case they missed it),
 I had asked,
  What is a possible configuration that would trigger
 the _SUBSYSTEM_ action in 55-lfs (2) ?

Neil answered:
 *As written*, the subsystem rule is triggered *if* the RTC is in
 subsystem rtc; if there is no such subsystem, the rule will never
 be triggered. The kernel rule will never be triggered because it is
 looking for a device with kernel name 'rtc'; this device doesn't exist.
 If this rule is changed to look for a device with correct kernel name
 of 'rtc0', it will be triggered.

Alex is saying:
 What rtc0 are we talking about?
 As a reminder to the readers (in case they missed it),
 I had written,
  ls -l /dev/rtc*
  crw-r--r-- 1 root root 10, 135 2011-04-30 20:32 /dev/rtc
 [please note the star above]

Alex said:
 I'm still puzzled about not being able to find any traces on the
 console about 'setclock' being run by udev (55-lfs above).
 Is it possible that inside udevd the standard message
 Setting system clock... goes somewhere else? The log-fog?

Neil answered:
 The log level may be set to, or default to, 'err'.
 If you change it via
  udevadm control --log-priority=info
  or
  udevadm control --log-priority=debug
 you should see all the info you're looking for--'debug' will show
 a *ton* of info.
   
Alex is saying:
 1. I'm not so sure.  You're suggestion works only during a live system
 to change log levels dynamically (as they say).  Would work like
 when you through another clock (like a grandfather's) at the machine
 and you want to see how udevd reacts in detail :)
 Our case (whether setclock script is run by Udev on start-up or not)
 is obviously a booting situation par excellence.
 You prepare for it _before_ reboot by statically setting the
 _following_ udevd log-level in '/etc/udev/udev.conf'
 (from say, default err to debug).

 2. That said, there's NO trace (so to speak) of a setclock run
 what so ever (as they type now a days) in the debug-log.
 OTOH, I have now positive proof that udev _does_ run setclock on 
 start-up.
 That's a 360 (as they say) reversal of what I said in my previous
 post.  Rest assured, the crow has already been boiled, enjoyed and
 the green remains ecologically disposed of.

Alex, on departing, is raising some new questions:
 Based on already (twice) mentioned
  ls -l /dev/rtc*
  crw-r--r-- 1 root root 10, 135 2011-04-30 20:32 /dev/rtc,
 I'm speculating that the difference between me and the rest
 of users (see also Simon's previous post of May 2, 2011 04:19:34 AM)
 who can proudly display a /dev/rtc0 (with a /dev/rtc symlink)
 or some such, is that I have CONFIG_RTC set to M as opposed to [Y] :(

 Questions:
 1.  Can this be true (a well known fact to everybody else)?
 (I know, I know, recompile the kernel with [Y] and see what happens :)
 As a matter of principle, I've always favored kernel/Udev to decide
 for me what module(s) is needed and when.

 2.  Normally, the kernel configuration has been careful to make a
 distinction between [Y/N] and [Y/M/N] depending on the situation.
 Is this a mis-coordination between Kernel and Udev, and the RTC
 _must_ be either Y or N (i.e., no M)?

 All I can certify is that my machines, always with M,
 have worked very smoothly (RTC-wise) all these years.
 I've never ever missed a /dev/rtc17 or the symlink.

Thanks,
-- Alex 

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


Re: Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Manuel Gonzalez Montoya
On Mon, May 2, 2011 at 2:45 AM, Brett brettsca...@email.com wrote:
 Hi

 I am trying to build LFS SVN-20110427 on an AMD64 system

 I get a consistent failure when running the checks for Binutils in
 chapter 6. This is the output where the error occurs:


For the error in new.cc you need to remove the include
  exception_defines.h
from the file ld/testsuite/ld-elf/new.cc
or see http://comments.gmane.org/gmane.linux.lfs.support/32431

For the errors in the selective test find the following line in the
file ld/testsuite/ld-selective/selective.exp
   set cxxflags -fvtable-gc -fno-exceptions -fno-rtti
and remove -fvtable-gc parameter
or see http://sourceware.org/ml/binutils/2010-12/msg00189.html
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: setclock Question (lfs-bootscripts-20110424)

2011-05-02 Thread Bruce Dubbs
al...@verizon.net wrote:

  That's a 360 (as they say) reversal of what I said in my previous
  post.  

Not sure if I got the attribution right.

LOL.  I think you mean 180.  :)

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


Re: Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Bruce Dubbs
Manuel Gonzalez Montoya wrote:
 On Mon, May 2, 2011 at 2:45 AM, Brett brettsca...@email.com wrote:
 Hi

 I am trying to build LFS SVN-20110427 on an AMD64 system

 I get a consistent failure when running the checks for Binutils in
 chapter 6. This is the output where the error occurs:

 
 For the error in new.cc you need to remove the include
   exception_defines.h
 from the file ld/testsuite/ld-elf/new.cc
 or see http://comments.gmane.org/gmane.linux.lfs.support/32431

sed -i /exception_defines.h/d ld/testsuite/ld-elf/new.cc

 For the errors in the selective test find the following line in the
 file ld/testsuite/ld-selective/selective.exp
set cxxflags -fvtable-gc -fno-exceptions -fno-rtti
 and remove -fvtable-gc parameter
 or see http://sourceware.org/ml/binutils/2010-12/msg00189.html

sed -i s/-fvtable-gc // ld/testsuite/ld-selective/selective.exp

I created a ticket to make these fixes.  Thanks.

   -- Bruce

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


Re: Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Ken Moffat
On Mon, May 02, 2011 at 04:45:59PM -0500, Bruce Dubbs wrote:
 Manuel Gonzalez Montoya wrote:
  On Mon, May 2, 2011 at 2:45 AM, Brett brettsca...@email.com wrote:
  Hi
 
  I am trying to build LFS SVN-20110427 on an AMD64 system
 
  I get a consistent failure when running the checks for Binutils in
  chapter 6. This is the output where the error occurs:
 
  
  For the error in new.cc you need to remove the include
exception_defines.h
  from the file ld/testsuite/ld-elf/new.cc
  or see http://comments.gmane.org/gmane.linux.lfs.support/32431
 
 sed -i /exception_defines.h/d ld/testsuite/ld-elf/new.cc
 
  For the errors in the selective test find the following line in the
  file ld/testsuite/ld-selective/selective.exp
 set cxxflags -fvtable-gc -fno-exceptions -fno-rtti
  and remove -fvtable-gc parameter
  or see http://sourceware.org/ml/binutils/2010-12/msg00189.html
 
 sed -i s/-fvtable-gc // ld/testsuite/ld-selective/selective.exp
 
 I created a ticket to make these fixes.  Thanks.
 
-- Bruce
 
 Glad Manuel has provided a fix to disable that test (although it
comes down to what I don't know about cannot harm me ;).  I
haven't built recently, but I'd just like to note that (at least on
x86_64) during the past 3 years I've *often* seen failures in 'ld'
tests, but everything has still worked ok.  I think the ld tests are
*good* at testing corner cases, and that seeing some failures there
is not necessarily a reason to worry.

 The fix is nice and tidy, but I do wonder if it might be better to
accept [ at least for people using the development book ] that tests
fail when the infrastructure changes (in this case, newer gcc) ?

 But, I've no strong feelings either way.

ĸ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: setclock Question (lfs-bootscripts-20110424)

2011-05-02 Thread alupu
May 2, 2011 05:24:23 PM, Bruce wrote:

 Alex wrote:
  That's a 360 (as they say) reversal of what I said in my previous  post.

 Not sure if I got the attribution right.LOL.
 I think you mean 180.  :)

Hi Bruce,

This is a relatively known joke (expression) in relative wide use.
It is attributed to Sammy Davis Jr.

Etymology:  during a conversation/interview he said something like 
 He did a full 360
meaning a complete change of opinion/attitude etc.

IMHO, he, as a top notch performer, can be forgiven for not
being too versed in geometry, when we all, technical people,
know full well that a complete reversal in direction actually
involves making a turn of 270 degrees (Celsius :)

-- Alex

PS  I expect the story to be found on YouTube somewhere.
I definitely remember hearing it on a sound bite at the time.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: lfs-support Digest, Vol 2302, Issue 2

2011-05-02 Thread janu mam
hi all
in my system windows was there on -sda1,sda2-extended partition ,personal
data drive-sda5
 i am doing lfs6.7(book)- on sda6,swap-sda7(i am using lfs-livecd)
---

 see this is  my grub.cfg file

root:/# cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_
- Hide quoted text -

entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
  fi
}
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set f02e767d-d75e-4e3c-93ac-85d3fdadcec0
set locale_dir=($root)/boot/grub/locale
set lang=
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry GNU/Linux, with Linux 2.6.35.4-lfs-6.7 --class gnu-linux --class
gnu --class os {
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set
f02e767d-d75e-4e3c-93ac-85d3fdadcec0
echoLoading Linux 2.6.35.4-lfs-6.7 ...
linux   /boot/vmlinux-2.6.35.4-lfs-6.7 root=/dev/sda6 ro
}
menuentry GNU/Linux, with Linux 2.6.35.4-lfs-6.7 (recovery mode) --class
gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set
f02e767d-d75e-4e3c-93ac-85d3fdadcec0
echoLoading Linux 2.6.35.4-lfs-6.7 ...
linux   /boot/vmlinux-2.6.35.4-lfs-6.7 root=/dev/sda6 ro single
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type
the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
-
right now i am here
8.4.3. Testing the Configuration

/sbin/reboot
...
grub root (hd0,6)
grub kernel /boot/grub/core.img
grub boot

question: when i issued above command its rebooted
on screen
one warning came and
stopping process

 stopping process...
stopping process
take cd remove cr tray,press enter
--

so i removed cd and i pressed enter
then  its directly booted into windows
why its not return to root(means to lfs)

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


Re: lfs-support Digest, Vol 2302, Issue 2

2011-05-02 Thread Bruce Dubbs
janu mam wrote:
 hi all
 in my system windows was there on -sda1,sda2-extended partition ,personal
 data drive-sda5
  i am doing lfs6.7(book)- on sda6,swap-sda7(i am using lfs-livecd)
 ---
 
  see this is  my grub.cfg file
 


 /sbin/reboot
 ...
 grub root (hd0,6)
 grub kernel /boot/grub/core.img
 grub boot
 
 question: when i issued above command its rebooted
 on screen
 one warning came and
 stopping process
 
  stopping process...
 stopping process
 take cd remove cr tray,press enter
 --
 
 so i removed cd and i pressed enter
 then  its directly booted into windows
 why its not return to root(means to lfs)
 
 i would appreciate any help

The reason you get windows is that the book assumes that your MBR boots 
to Grub.  Your system's MBR still has a Windows boot loader.  You will 
have to do 'grub-setup /dev/sda' and forgo the testing in section 8.4.3.

To get to windows from grub, you will need to do the following either 
from the grub command line or grub.cfg

insmod chain
insmod ntfs
set root=(hd0,1)
chainloader +1

See 
http://www.gnu.org/software/grub/manual/html_node/Chain_002dloading.html#Chain_002dloading

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


Re: Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Brett
Hi

Manuel Gonzalez Montoya wrote:
 On Mon, May 2, 2011 at 2:45 AM, Brett brettsca...@email.com wrote:
 Hi

 I am trying to build LFS SVN-20110427 on an AMD64 system

 I get a consistent failure when running the checks for Binutils in
 chapter 6. This is the output where the error occurs:

 
 For the error in new.cc you need to remove the include
   exception_defines.h
 from the file ld/testsuite/ld-elf/new.cc
 or see http://comments.gmane.org/gmane.linux.lfs.support/32431

sed -i /exception_defines.h/d ld/testsuite/ld-elf/new.cc

 For the errors in the selective test find the following line in the
file ld/testsuite/ld-selective/selective.exp
set cxxflags -fvtable-gc -fno-exceptions -fno-rtti
 and remove -fvtable-gc parameter
 or see http://sourceware.org/ml/binutils/2010-12/msg00189.html

sed -i s/-fvtable-gc // ld/testsuite/ld-selective/selective.exp

I created a ticket to make these fixes.  Thanks.

   -- Bruce

That worked fine, thanks

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


Re: Binutils 2.21 - check failure in chapter 6.13

2011-05-02 Thread Brett
 Glad Manuel has provided a fix to disable that test (although it
 comes down to what I don't know about cannot harm me ;).  I
 haven't built recently, but I'd just like to note that (at least on
 x86_64) during the past 3 years I've *often* seen failures in 'ld'
 tests, but everything has still worked ok.  I think the ld tests are
 *good* at testing corner cases, and that seeing some failures there
 is not necessarily a reason to worry.

 The fix is nice and tidy, but I do wonder if it might be better to
 accept [ at least for people using the development book ] that tests
 fail when the infrastructure changes (in this case, newer gcc) ?

 But, I've no strong feelings either way.

 ĸen

I don't think I have strong feelings either way either but a
warning about possible failures would be helpful even if
a fix isn't written up.

I spent a lot of time trying to find out if the failures were
significant but wasn't able to find the info until this list
pointed me in the right direction.

Thanks for the help

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