Re: [lfs-support] Error while compiling GCC 4.6.1 Pass 1
Hi Ken, Le jeudi 05 janvier 2012 à 02:04 +, Ken Moffat a écrit : On Wed, Jan 04, 2012 at 09:22:26PM -0400, Franck Chuiton wrote: make[2]: *** [s-gtype] Killed make[2]: Leaving directory `/mnt/LFS/sources/gcc-build/gcc' make[1]: *** [all-gcc] Error 2 make[1]: Leaving directory `/mnt/LFS/sources/gcc-build' make: *** [all] Error 2 Hi Franck, it's the '[s-gtype] Killed' that shows the problem. Yep, I think I got that right too ;) But as for what caused it, I've no idea - perhaps a segfault (hopefully, that would be logged somewhere?), perhaps OOM [ out of memory ]. Is this an old machine ? Is it short of space ? Has the RAM decided to start misbehaving [ memtest86 ] ? 512MB of DDR533, 1600Mhz CPU. Laptop seems to work fine. Just finished memtesting the RAM and no error came out. I guess I mistyped something because when I used Jason's piece of script (copy-paste), it went OK. Well, at least, a bit further down because I had another error... that I will track down tonight. Have a nice day. See you. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- Franck Chuiton fra...@chuiton.fr -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error while compiling GCC 4.6.1 Pass 1
Hi Guys, Hi Franck, it's the '[s-gtype] Killed' that shows the problem. Yep, I think I got that right too ;) I guess I mistyped something because when I used Jason's piece of script (copy-paste), it went OK. Well, at least, a bit further down because I had another error... that I will track down tonight. Sorry if I got anything wrong.. but I am not emailing you because of that. In the LFS Book it talks about wiping your source folders after each build so they are clean for the next. I've been taking a LAX approach to this, trying to only do that when I see that a source folder (or one of those temp ones is going to be used again. Well.. I've been fighting a chroot issue - that I didn't recall being an issue when I was doing the book by hand. Maybe not related - but a FIX I found nonetheless... Bin Utils is built twice early on, and my second build was erroring out and I didn't notice util I put PRESS ENTER to continue pauses after each compile to debug... and LOW and BEHOLD - NOT REMOVING the binutils and the temp build directory the book suggests was the culprit. Now BOTH binutil passes compile. Just thought I'd share because we are all hacking away at this! :) --Jason -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS -Chapter 6.4 - CHROOT - Frustrating me badly.... I've tried so many things...
On Wed, 04 Jan 2012 21:25:27 -0700 jasonps...@jegas.com wrote: Hello Folks, I need more help I'm afraid. Error Message: chroot failed to run command '/tools/bin/env' : No such file or directory What do you get when you run (on your host system): ldd /tools/bin/env If it lists anything in /lib or /usr then you've made a mistake somewhere. It should only list things in /tools. Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error while compiling GCC 4.6.1 Pass 1
On 1/4/2012 8:04 PM, Ken Moffat wrote: On Wed, Jan 04, 2012 at 09:22:26PM -0400, Franck Chuiton wrote: But it went wrong with gcc-4.6.1 : gcc -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/gengtype \ build/gengtype.o build/errors.o build/gengtype-lex.o build/gengtype-parse.o build/gengtype-state.o build/version.o ../build-i686-pc-linux-gnu/libiberty/libiberty.a /bin/bash ../../gcc-4.6.1/gcc/../move-if-change tmp-gi.list gtyp-input.list echo timestamp s-gtyp-input build/gengtype \ -S ../../gcc-4.6.1/gcc -I gtyp-input.list -w gtype.state build/gengtype \ -r gtype.state make[2]: *** [s-gtype] Killed make[2]: Leaving directory `/mnt/LFS/sources/gcc-build/gcc' make[1]: *** [all-gcc] Error 2 make[1]: Leaving directory `/mnt/LFS/sources/gcc-build' make: *** [all] Error 2 Hi Franck, it's the '[s-gtype] Killed' that shows the problem. But as for what caused it, I've no idea - perhaps a segfault (hopefully, that would be logged somewhere?), perhaps OOM [ out of memory ]. Is this an old machine ? Is it short of space ? Has the RAM decided to start misbehaving [ memtest86 ] ? ĸen The Aspire series of notebooks are fairly new; I have a model from last year that can triple boot from two types of installed Puppy and Windows. (Though I did learn why there is a GRUB for DOS..) Elly -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] short sanity-check of GMP-5.0.2 install
Hello All, I'm building LFS-DEV (SVN-20111228) and everything's going well so far. Just wanted to check on an item that doesn't turn up in any searches... Running make check on GMP-5.0.2 reports 162 tests passed, but running make install reports: libtool: install: warning: relinking `libgmpxx.la' I assume it's the expected result, but wanted to double-check before continuing. Thanks.-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] short sanity-check of GMP-5.0.2 install
Just to be clear-- I'm referring to the end of chapter 6.14 [GMP-5.0.2], just after install. From: str1chn1n3 Sent: Thursday, January 05, 2012 12:49 PM To: lfs-support@linuxfromscratch.org Subject: [lfs-support] short sanity-check of GMP-5.0.2 install Hello All, I'm building LFS-DEV (SVN-20111228) and everything's going well so far. Just wanted to check on an item that doesn't turn up in any searches... Running make check on GMP-5.0.2 reports 162 tests passed, but running make install reports: libtool: install: warning: relinking `libgmpxx.la' I assume it's the expected result, but wanted to double-check before continuing. Thanks. -- -- 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: [lfs-support] No to rewrite the wheel but I'm scripting the LFS Book...
Op Sun, 01 Jan 2012 10:03:05 +0100 schreef jasonps...@jegas.com:
I know there is ALFS and JALFS or whatever and I might refer and or use
those but for me, I personally
like the book layout, so I'm making scripts for each CHUNK along the
way.
HAPPY NEW YEAR FOLKS!
--Jason P Sage
Have you read the Hint More Control and Package Management using Package
Users (v1.2)
(www.linuxfromscratch.org/hints/read.html).? Also look into the enclosed
script; somebody send it to me,
but I don't remember who. There was also a discussion about this topic
last year or the year before
on this support-site.
Hans.
# Begin Build for PACKAGE
# The basis for this script, and actually the meat of it, came from
# Matthias Benkman's More Control and Package Users package management
# system. The hint for this is found at the Linux From Scratch Hints
# web page.
# This version came from a CLFS build, by Dan McGhee in September of
# using CLFS-SVN-snapshot date-x86_64-Multilib book. I owe a large
# debt of gratitude to Ken Moffat, a LFS developer, from whom I took
# a large portion of the start_commands.
# Run this script from the packag users home directory by invoking it with
# the package name--ex. vim-7.2. It will find the tarball in $PACKAGES,
# untar it, change to the created directory and configure, make install.
# Then it will clean up by creating a list of the installed files and
# remove the source tree.
# NOTE: There are sections in this script that must be uncommented to
# accomplish various things: 32 bit builds, 64 bit builds and
# running a test suite. Scroll through and you will find them.
# It will create 6 log files in the $HOME directory:
# configure.log: All messages output during configure
# configure.err: Just the errors output during configure
# make.log: All messages output during make
# make.err: Just the errors output during make
# install.log: All messages output during make install
# install.err: Just the errors output during make install
# variables
package=$@
logdir=$package-32bit-logs
PACKAGES=/sources
CURRENT=$package
# Begin function definitions
start_commands () {
# Make a log directory
mkdir -v $logdir
# determine type of tar, and name of its directory
# enter with current set to version name
# returns with current set with tar/type,
# directory set, and tarcmd set
if [ -r ${PACKAGES}/${CURRENT}.tar.bz2 ]; then
CURRENT=${CURRENT}.tar.bz2
TARCMD='-j'
elif [ -r ${PACKAGES}/${CURRENT}.tar.gz ]; then
CURRENT=${CURRENT}.tar.gz
TARCMD='-z'
elif [ -r ${PACKAGES}/${CURRENT}.tgz ]; then
CURRENT=${CURRENT}.tgz
TARCMD='-z'
elif [ -r ${PACKAGES}/${CURRENT}.tar ]; then
CURRENT=${CURRENT}.tar
TARCMD=
elif [ -r ${PACKAGES}/${CURRENT}.tbz2 ]; then
CURRENT=${CURRENT}.tbz2
TARCMD='-j'
elif [ -r ${PACKAGES}/${CURRENT}.tar.xz ]; then
CURRENT=${CURRENT}.tar.xz
TARCMD='-J'
else
echo identify: unable to identify tar for $CURRENT
exit 1
fi
echo testing ${CURRENT}
# /dev/null may not exist at start of ch6
# changed to test for character special file instead of file
#if [ -c /dev/null ]; then
# NUL='2/dev/null'
#fi
# util-linux uses ./ at start of directory names
#DIRECTORY=`tar -tv $TARCMD -f ${PACKAGES}/${CURRENT} $NUL | head -n 1
| awk '{ print $6}' | sed s'@^./@@' | \
# making NUL defined causes tar to try to look for 2/dev/null in the
tarball.
DIRECTORY=`tar -tv $TARCMD -f ${PACKAGES}/${CURRENT} | head -n 1 | awk
'{ print $6}' | sed s'@^./@@' | \
cut -d '/' -f 1`
if [ -z $DIRECTORY ]; then
echo indentify: error in trying to determine directory name
exit 1
fi
echo identify: directory is $DIRECTORY
# Untar
echo Untarring $CURRENT
tar -x $TARCMD -f $PACKAGES/$CURRENT
echo Entering source tree
cd $DIRECTORY
packagedir=$DIRECTORY
echo $packagedir
}
configure_commands()
{ :
CC=gcc ${BUILD32} ./configure --prefix=/usr
}
make_commands()
{ :
make
}
install_commands()
{ :
make install
}
test_pipe()
{
for i in ${PIPESTATUS[@]}
do
test $i != 0 { echo FAILED! ; exit 1 ; }
done
echo successful!
return 0
}
# End Functions
# Begin tests and function calls for fresh and failed builds.
# This one recovers from failed make.
if [ -e $logdir/make-`echo $package`.err ] \
[ ! -e $logdir/install-`echo $package`.err ]; then #Now build
cd $HOME/$packagedir
echo -n Building `echo $package`...
{ make_commands 31 12 23 | tee $Home/$logdir/make-`echo
$package`.err ;} $HOME/$logdir/make-`echo $package`.log
test_pipe echo -n Installing
[lfs-support] at command?
Since I get a command not found type error, I assume not, but I have to ask: 1) is the at command installed in any of the LFS packages? 2) Or, is there some other command that provides the same functionality? (start some job/batch file at a given time) 3) Finally, if not part of LFS, can anyone suggest where to find the sources so I can install it? Thanks for 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] at command?
On 6/01/2012 2:59 PM, David Gay wrote: Since I get a command not found type error, I assume not, but I have to ask: 1) is the at command installed in any of the LFS packages? 2) Or, is there some other command that provides the same functionality? (start some job/batch file at a given time) 3) Finally, if not part of LFS, can anyone suggest where to find the sources so I can install it? Thanks for any help. For cron type functionality I ended up using dcron. http://www.jimpryor.net/linux/releases/dcron-4.5.tar.gz -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] at command?
David Gay wrote: Since I get a command not found type error, I assume not, but I have to ask: 1) is the at command installed in any of the LFS packages? Not presently. It is mentioned in Section iv. LFS and Standards. 2) Or, is there some other command that provides the same functionality? (start some job/batch file at a given time) 3) Finally, if not part of LFS, can anyone suggest where to find the sources so I can install it? The classic 'at' command is contained in the package at-3.1.13.orig.tar.gz (http://packages.debian.org/source/unstable/at). You do not need the diff file. The package also provides the 'batch' command. You do need to create a boot script for it to function properly because the atd daemon needs to be running for it to work. This is the first time I've seen a request for it. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
