Re: live and learn
On Tue, Jun 8, 2010 at 11:45 PM, Mike McCarty mike.mcca...@sbcglobal.net wrote: Neal Murphy wrote: A possible future enhancement to 'the book' might be to incorporate checkboxes that a newbie would check off as she performs each step. Extra work? Yes. But worth it to make each step clearer? Yes again. Possibly. However, who prints the book? Mostly, I was cut'n'pasting the commands. I print the book. However, I print it 9-up to save paper. I like having the hard copy to read on the train. Unfortunately, this sometimes has the side-effect of making 1 (one) and l (ell) difficult to distinguish, though I've built enough times that I usually guess right. (I recall once spending quite some time trying to figure out why GRUB couldn't find menu.1st.) And during my last build I couldn't figure out why cp -sv libbz2.so* /lib wouldn't work. (The options are -av, of course.) Theron -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Error compiling texinfo-4.13
Those undefined references are for functions in curses. Note this warning you got earlier: configure: WARNING: probably need a terminal library, one of: ncurses curses termlib termcap terminfo So you appear to be missing a terminal library. Is ncurses installed properly? Theron On Mon, Oct 20, 2008 at 11:50 AM, Stefan Breitegger [EMAIL PROTECTED] wrote: There's also the same error with the original LFS package. So I installed texinfo-4.13. I'm compiling with debian lenny and gcc-4.1 Here's the log: ./configure --prefix=/tools make make install checking for a BSD-compatible install... /tools/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /tools/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for ranlib... ranlib checking whether gcc and cc understand -c and -o together... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /tools/bin/grep checking for egrep... /tools/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for working alloca.h... yes checking for alloca... yes checking for C/C++ restrict keyword... __restrict checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking for getopt_long_only... yes checking whether optreset is declared... no checking for working GNU getopt function... yes checking whether getenv is declared... yes checking whether the preprocessor supports include_next... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking for unistd.h... (cached) yes checking for stdint.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for sys/stat.h... (cached) yes checking wctype.h usability... yes checking wctype.h presence... yes checking for wctype.h... yes checking for struct timeval... yes checking for gettimeofday... yes checking for isascii... yes checking for mbsinit... yes checking for setenv... yes checking for lstat... yes checking for iswcntrl... yes checking for wcwidth... yes checking for inline... inline checking for nl_langinfo and CODESET... yes checking whether getc_unlocked is declared... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking whether we are using the GNU C Library 2.1 or newer... yes checking whether malloc, realloc, calloc are POSIX compliant... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for long long int... yes checking for mbstate_t... yes checking whether mbrtowc and mbstate_t are properly declared... yes checking whether memmem is declared... yes checking for memmem... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for unsigned long long int... yes checking whether strdup is declared... yes checking for working strerror function... yes checking whether strndup is declared... yes checking whether strnlen is declared... yes checking whether stat file-mode macros are broken... no checking for wint_t... yes checking for wchar_t... yes checking for alloca as a compiler built-in... yes checking for argz.h... yes checking for error_t... yes checking for argz_replace... yes checking if argz actually works... yes checking if environ is properly declared... yes checking for error_at_line... yes checking for gettimeofday with POSIX
Re: Glibc cannot find -lstdc++
If you read the book, you will discover that On Tue, Aug 26, 2008 at 2:54 PM, satish patel [EMAIL PROTECTED] wrote: Again I got new error [snip] /lfs/sources/glibc-build/nptl /mnt/lfs/sources/glibc-build/nptl/tst-cancel1 /mnt/lfs/sources/glibc-build/nptl/tst-cancel1.out Didn't expect signal from child: got `Aborted' make[2]: *** [/mnt/lfs/sources/glibc-build/nptl/tst-cancel1.out] Error 1 is an expected error. Theron -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Confusion re: separate gcc-build directory
On Tue, Aug 26, 2008 at 6:36 PM, [EMAIL PROTECTED] wrote: I am using the html version of Linux From Scratch Version 6.3. I have completed all steps up to and including application of the specs patch in section 5.11. GCC-4.1.2 - Pass 2, 5.11.1. Re-installation of GCC. HOWEVER, the following instructions have me confused: Create a separate build directory again: mkdir -v ../gcc-build cd ../gcc-build What is the meaning of create AGAIN? The separate gcc-build directory I created in section 5.4. GCC-4.1.2 - Pass 1 still exists and is still populated with files and directories. Am I supposed to delete the contents and start over with an empty gcc-build directory in the same location? Yes, delete it and start over. (I was confused at first, too.) Theron -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
