Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-06-2005, 07:55 PM
|
#1
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Rep: 
|
LFS 6.0 Book question.
How long after chapeter 5 does the book explain installation an so forth. I would like to print off the book(or part of it) in order to build LFS. That way, I won't have to keep switching between the console and X in debian when I'm building it. Will stopping, and picking up the installation affect anything? Is ther anything else someone doing this for the first time should know?
|
|
|
|
|
07-06-2005, 09:41 PM
|
#2
|
|
Member
Registered: Jul 2004
Distribution: LFS, I felt the itch and scratched it
Posts: 227
Rep:
|
Re: LFS 6.0 Book question.
Quote:
Originally posted by microsoft/linux
How long after chapeter 5 does the book explain installation an so forth. I would like to print off the book(or part of it) in order to build LFS. That way, I won't have to keep switching between the console and X in debian when I'm building it. Will stopping, and picking up the installation affect anything? Is ther anything else someone doing this for the first time should know?
|
You can run the installation in a terminal in X.
Stopping the installation won't affect anything, although if you do restart or something like that causing stuff to become unmounted or environmental variables become unset, make sure to redo those steps. You'll have to redo 6.2 again if you restart (mounting kernel stuff). |
|
|
|
|
07-07-2005, 12:03 PM
|
#3
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Original Poster
Rep:
|
How difficult is LFS? Where do I unpack all of the source files? I downloaded the lfs-packages-6.0.tar, and unpacked it in /mnt/lfs/sources, is that correct? How about making a directory called ../binutils-build? I can't make it because debian gives me an error about not having permission. I could do it as root, but then I'd have to change the owner and do all of that. Is there any way to set it so the user lfs can do it? I have given the ownership of /mnt/lfs to lfs, as well as changed the group to lfs. Thoughts?
|
|
|
|
|
07-07-2005, 02:40 PM
|
#4
|
|
Member
Registered: Jul 2004
Distribution: LFS, I felt the itch and scratched it
Posts: 227
Rep:
|
Quote:
Originally posted by microsoft/linux
How difficult is LFS? Where do I unpack all of the source files? I downloaded the lfs-packages-6.0.tar, and unpacked it in /mnt/lfs/sources, is that correct? How about making a directory called ../binutils-build? I can't make it because debian gives me an error about not having permission. I could do it as root, but then I'd have to change the owner and do all of that. Is there any way to set it so the user lfs can do it? I have given the ownership of /mnt/lfs to lfs, as well as changed the group to lfs. Thoughts?
|
1. Depending on how much you want to deviate from the guide, it can be very easy or very difficult.
2. Yes, it should be unpacked to /mnt/lfs/source
3. Do a chown lfs $LFS/sources |
|
|
|
|
07-07-2005, 10:24 PM
|
#5
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Original Poster
Rep:
|
for some reason, when I rebooted, the mkdir command worked. Perhaps I should have logged out, then back in before attempting anything? Here's another question for you. I unpacked binutils into /mnt/lfs, then did 'mkdir binutils-build' as per the book, then i did 'cd binutils-build', and configured the source according to the book. This is the output from the configuration
Quote:
loading cache ./config.cache
checking host system type... config.sub: invalid option --disable-nls
Try `config.sub --help' for more information.
checking target system type... config.sub: invalid option --disable-nls
Try `config.sub --help' for more information.
checking build system type... config.sub: invalid option --disable-nls
Try `config.sub --help' for more information.
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether ln works... (cached) yes
checking whether ln -s works... (cached) yes
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gnatbind... no
checking whether compiler driver understands Ada... (cached) no
checking how to compare bootstrapped objects... (cached) cmp --ignore-initial=16 $$f1 $$f2
checking for correct version of gmp.h... no
checking for bison... (cached) bison
checking for bison... (cached) bison -y
checking for gm4... (cached) m4
checking for flex... (cached) flex
checking for flex... (cached) flex
checking for makeinfo... no
checking for --disable-nls-ar... no
checking for --disable-nls-as... no
checking for --disable-nls-dlltool... no
checking for --disable-nls-ld... no
checking for --disable-nls-nm... no
checking for --disable-nls-ranlib... no
checking for --disable-nls-windres... no
checking for --disable-nls-objcopy... no
checking for --disable-nls-objdump... no
checking for --disable-nls-ar... no
checking for --disable-nls-as... no
checking for --disable-nls-dlltool... no
checking for --disable-nls-ld... no
checking for --disable-nls-nm... no
checking for --disable-nls-ranlib... no
checking for --disable-nls-windres... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... (cached) yes
creating ./config.status
creating Makefile
|
Then it gave a bunch of errors about lines in the 3000s of the configure script not working, and a program 's' error from sed.
There is nothing in the Makefile, and the 'make configure-host' command fails. HELP!!!
Last edited by microsoft/linux; 07-07-2005 at 10:28 PM.
|
|
|
|
|
07-07-2005, 11:12 PM
|
#6
|
|
Member
Registered: Oct 2004
Location: somewhere in the street
Distribution: Window$
Posts: 192
Rep:
|
Quote:
Originally posted by microsoft/linux
for some reason, when I rebooted, the mkdir command worked. Perhaps I should have logged out, then back in before attempting anything? Here's another question for you. I unpacked binutils into /mnt/lfs, then did 'mkdir binutils-build' as per the book, then i did 'cd binutils-build', and configured the source according to the book. This is the output from the configuration
Then it gave a bunch of errors about lines in the 3000s of the configure script not working, and a program 's' error from sed.
There is nothing in the Makefile, and the 'make configure-host' command fails. HELP!!!
|
I guess, you had typo mistake  , could you post you command?
I have a little experience: using a OS has cut && patse abilities helps so much (ex: Knoppix, ...). All we have to do are just cut && patse
Cheers,
Giang Hu
Last edited by freegianghu; 07-07-2005 at 11:13 PM.
|
|
|
|
|
07-08-2005, 02:49 PM
|
#7
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Original Poster
Rep:
|
yeah, it was kind of a typo. I didn't realize when running '../binutils-2<etc. etc.>/configure --prefix=/tools \ --disable-nls' that you had to hit enter before the '--disable-nls' gibing you the second line on which to specify --disable-nls. S that worked and I got up to 'make install'. Tried it as user lfs, and it gave me a permission denied error. So then I tried it as root, and the output is here
Quote:
lfs@Agilitas:/lfs/sources/binutils-build$ make install
/bin/sh ../binutils-2.15.91.0.2/mkinstalldirs /tools /tools
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
Making install in doc
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
/bin/sh ../../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/info
/usr/bin/install -c -m 644 ./bfd.info /tools/info/bfd.info
/usr/bin/install: cannot remove `/tools/info/bfd.info': Permission denied
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/lib
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/include
/bin/sh ./libtool --mode=install /usr/bin/install -c libbfd.la /tools/lib/libbfd.la
/usr/bin/install -c .libs/libbfd.lai /tools/lib/libbfd.la
/usr/bin/install: cannot remove `/tools/lib/libbfd.la': Permission denied
make[3]: *** [install_libbfd] Error 1
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make: *** [install-bfd] Error 2
/bin/sh ../binutils-2.15.91.0.2/mkinstalldirs /tools /tools
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
Making install in doc
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
/bin/sh ../../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/info
/usr/bin/install -c -m 644 ./bfd.info /tools/info/bfd.info
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/lib
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/include
/bin/sh ./libtool --mode=install /usr/bin/install -c libbfd.la /tools/lib/libbfd.la
/usr/bin/install -c .libs/libbfd.lai /tools/lib/libbfd.la
/usr/bin/install -c .libs/libbfd.a /tools/lib/libbfd.a
ranlib /tools/lib/libbfd.a
chmod 644 /tools/lib/libbfd.a
PATH="$PATH:/sbin" ldconfig -n /tools/lib
----------------------------------------------------------------------
Libraries have been installed in:
/tools/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/usr/bin/install -c -m 644 bfd.h /tools/include/bfd.h
/usr/bin/install -c -m 644 ../../binutils-2.15.91.0.2/bfd/../include/ansidecl.h /tools/include/ansidecl.h
/usr/bin/install -c -m 644 ../../binutils-2.15.91.0.2/bfd/../include/symcat.h /tools/include/symcat.h
/usr/bin/install -c -m 644 ../../binutils-2.15.91.0.2/bfd/../include/bfdlink.h /tools/include/bfdlink.h
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/opcodes'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/opcodes/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/opcodes/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/opcodes'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/opcodes'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../binutils-2.15.91.0.2/opcodes/../mkinstalldirs /tools/lib
/bin/sh ../../binutils-2.15.91.0.2/opcodes/../mkinstalldirs /tools/include
/bin/sh ./libtool --mode=install /usr/bin/install -c libopcodes.la /tools/lib/libopcodes.la
/usr/bin/install -c .libs/libopcodes.lai /tools/lib/libopcodes.la
/usr/bin/install -c .libs/libopcodes.a /tools/lib/libopcodes.a
ranlib /tools/lib/libopcodes.a
chmod 644 /tools/lib/libopcodes.a
PATH="$PATH:/sbin" ldconfig -n /tools/lib
----------------------------------------------------------------------
Libraries have been installed in:
/tools/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/usr/bin/install -c -m 644 ../../binutils-2.15.91.0.2/opcodes/../include/dis-asm.h /tools/include/dis-asm.h
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/opcodes'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/opcodes'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/opcodes'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/binutils'
Making install in doc
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/binutils/doc'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/binutils/doc'
make[3]: Nothing to be done for `install-exec-am'.
make install-man1
make[4]: Entering directory `/mnt/lfs/sources/binutils-build/binutils/doc'
/bin/sh ../../../binutils-2.15.91.0.2/binutils/../mkinstalldirs /tools/man/man1
/usr/bin/install -c -m 644 addr2line.1 /tools/man/man1/addr2line.1
/usr/bin/install -c -m 644 ar.1 /tools/man/man1/ar.1
/usr/bin/install -c -m 644 dlltool.1 /tools/man/man1/dlltool.1
/usr/bin/install -c -m 644 nlmconv.1 /tools/man/man1/nlmconv.1
/usr/bin/install -c -m 644 nm.1 /tools/man/man1/nm.1
/usr/bin/install -c -m 644 objcopy.1 /tools/man/man1/objcopy.1
/usr/bin/install -c -m 644 objdump.1 /tools/man/man1/objdump.1
/usr/bin/install -c -m 644 ranlib.1 /tools/man/man1/ranlib.1
/usr/bin/install -c -m 644 readelf.1 /tools/man/man1/readelf.1
/usr/bin/install -c -m 644 size.1 /tools/man/man1/size.1
/usr/bin/install -c -m 644 strings.1 /tools/man/man1/strings.1
/usr/bin/install -c -m 644 strip.1 /tools/man/man1/strip.1
/usr/bin/install -c -m 644 windres.1 /tools/man/man1/windres.1
/usr/bin/install -c -m 644 c++filt.1 /tools/man/man1/c++filt.1
make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils/doc'
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils/doc'
/bin/sh ../../../binutils-2.15.91.0.2/binutils/../mkinstalldirs /tools/info
/usr/bin/install -c -m 644 ./binutils.info /tools/info/binutils.info
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils/doc'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/binutils/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/binutils'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/binutils'
/bin/sh ../../binutils-2.15.91.0.2/binutils/../mkinstalldirs /tools/bin
/bin/sh ./libtool --mode=install /usr/bin/install -c size /tools/bin/size
/usr/bin/install -c size /tools/bin/size
/bin/sh ./libtool --mode=install /usr/bin/install -c objdump /tools/bin/objdump
/usr/bin/install -c objdump /tools/bin/objdump
/bin/sh ./libtool --mode=install /usr/bin/install -c ar /tools/bin/ar
/usr/bin/install -c ar /tools/bin/ar
/bin/sh ./libtool --mode=install /usr/bin/install -c strings /tools/bin/strings
/usr/bin/install -c strings /tools/bin/strings
/bin/sh ./libtool --mode=install /usr/bin/install -c ranlib /tools/bin/ranlib
/usr/bin/install -c ranlib /tools/bin/ranlib
/bin/sh ./libtool --mode=install /usr/bin/install -c objcopy /tools/bin/objcopy
/usr/bin/install -c objcopy /tools/bin/objcopy
/bin/sh ./libtool --mode=install /usr/bin/install -c addr2line /tools/bin/addr2line
/usr/bin/install -c addr2line /tools/bin/addr2line
/bin/sh ./libtool --mode=install /usr/bin/install -c readelf /tools/bin/readelf
/usr/bin/install -c readelf /tools/bin/readelf
/bin/sh ./libtool --mode=install /usr/bin/install -c nm-new /tools/bin/nm
/usr/bin/install -c nm-new /tools/bin/nm
/bin/sh ./libtool --mode=install /usr/bin/install -c strip-new /tools/bin/strip
/usr/bin/install -c strip-new /tools/bin/strip
/bin/sh ./libtool --mode=install /usr/bin/install -c cxxfilt /tools/bin/c++filt
/usr/bin/install -c cxxfilt /tools/bin/c++filt
/bin/sh ../../binutils-2.15.91.0.2/binutils/../mkinstalldirs /tools/i686-pc-linux-gnu/bin
for i in nm-new strip-new ar ranlib dlltool; do \
if [ -f $i ]; then \
j=`echo $i | sed -e 's/-new//'`; \
k=`echo $j | sed 's,y,y,'`; \
if [ "/tools/bin/$k" != "/tools/i686-pc-linux-gnu/bin/$j" ]; then \
rm -f /tools/i686-pc-linux-gnu/bin/$j; \
ln /tools/bin/$k /tools/i686-pc-linux-gnu/bin/$j >/dev/null 2>/dev/null \
|| /bin/sh ./libtool --mode=install /usr/bin/install -c $i /tools/i686-pc-linux-gnu/bin/$j; \
fi; \
else true; \
fi; \
done
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/binutils'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/etc'
for f in standards.info configure.info; do \
if test -f ../../binutils-2.15.91.0.2/etc/`echo $f | sed -e 's/.info$/.texi/'`; then \
if make "MAKEINFO=/mnt/lfs/sources/binutils-2.15.91.0.2/missing makeinfo --split-size=5000000" $f; then \
true; \
else \
exit 1; \
fi; \
fi; \
done
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/etc'
make[2]: `standards.info' is up to date.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/etc'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/etc'
make[2]: `configure.info' is up to date.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/etc'
/bin/sh ../../binutils-2.15.91.0.2/etc/../mkinstalldirs /tools/info
if test ! -f standards.info; then cd ../../binutils-2.15.91.0.2/etc; fi; \
if test -f standards.info; then \
for i in standards.info*; do \
/usr/bin/install -c -m 644 $i /tools/info/$i; \
done; \
fi
if test ! -f configure.info; then cd ../../binutils-2.15.91.0.2/etc; fi; \
if test -f configure.info; then \
for i in configure.info*; do \
/usr/bin/install -c -m 644 $i /tools/info/$i; \
done; \
fi
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/etc'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/gas'
Making install in doc
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/gas/doc'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/gas/doc'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/tools/info" || mkdir -p -- . "/tools/info"
/usr/bin/install -c -m 644 '../../../binutils-2.15.91.0.2/gas/doc/as.info' '/tools/info/as.info'
test -z "/tools/man/man1" || mkdir -p -- . "/tools/man/man1"
/usr/bin/install -c -m 644 'as.1' '/tools/man/man1/as.1'
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/gas/doc'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/gas/doc'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/gas/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/gas/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/gas'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/gas'
/bin/sh ../../binutils-2.15.91.0.2/gas/../mkinstalldirs /tools/bin
/bin/sh ./libtool --mode=install /usr/bin/install -c as-new /tools/bin/as
/usr/bin/install -c as-new /tools/bin/as
/bin/sh ../../binutils-2.15.91.0.2/gas/../mkinstalldirs /tools/i686-pc-linux-gnu/bin
n=`echo as | sed 's,y,y,'`; \
if [ "/tools/bin/$n" != "/tools/i686-pc-linux-gnu/bin/as" ]; then \
rm -f /tools/i686-pc-linux-gnu/bin/as; \
ln /tools/bin/$n /tools/i686-pc-linux-gnu/bin/as >/dev/null 2>/dev/null \
|| /bin/sh ./libtool --mode=install /usr/bin/install -c as-new /tools/i686-pc-linux-gnu/bin/as; \
else \
true ; \
fi
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/gas'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/gas'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/gas'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/gprof'
make install-recursive
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/gprof'
Making install in po
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/gprof/po'
make[3]: Nothing to be done for `install'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof/po'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/gprof'
make[4]: Entering directory `/mnt/lfs/sources/binutils-build/gprof'
test -z "/tools/bin" || mkdir -p -- . "/tools/bin"
/bin/sh ./libtool --mode=install /usr/bin/install -c 'gprof' '/tools/bin/gprof'
/usr/bin/install -c gprof /tools/bin/gprof
Making install-info in po
make[5]: Entering directory `/mnt/lfs/sources/binutils-build/gprof/po'
make[5]: Nothing to be done for `install-info'.
make[5]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof/po'
make[5]: Entering directory `/mnt/lfs/sources/binutils-build/gprof'
test -z "/tools/info" || mkdir -p -- . "/tools/info"
/usr/bin/install -c -m 644 '../../binutils-2.15.91.0.2/gprof/gprof.info' '/tools/info/gprof.info'
make[5]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof'
test -z "/tools/man/man1" || mkdir -p -- . "/tools/man/man1"
/usr/bin/install -c -m 644 'gprof.1' '/tools/man/man1/gprof.1'
make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof'
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/gprof'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/intl'
if test "@PACKAGE@" = "gettext" \
&& test '' = 'intl-compat.o'; then \
if test -r ../../binutils-2.15.91.0.2/intl/../../mkinstalldirs; then \
../../binutils-2.15.91.0.2/intl/../../mkinstalldirs /tools/lib /tools/include; \
else \
../../binutils-2.15.91.0.2/intl/mkinstalldirs /tools/lib /tools/include; \
fi; \
/usr/bin/install -c -m 644 intlh.inst /tools/include/libintl.h; \
/usr/bin/install -c -m 644 libintl.a /tools/lib/libintl.a; \
else \
: ; \
fi
if test "@PACKAGE@" = "gettext"; then \
if test -r ../../binutils-2.15.91.0.2/intl/../../mkinstalldirs; then \
../../binutils-2.15.91.0.2/intl/../../mkinstalldirs /tools/share/gettext/intl; \
else \
../../binutils-2.15.91.0.2/intl/mkinstalldirs /tools/share/gettext/intl; \
fi; \
/usr/bin/install -c -m 644 VERSION /tools/share/gettext/intl/VERSION; \
dists="ChangeLog Makefile.in linux-msg.sed po2tbl.sed.in xopen-msg.sed gettext.h gettextP.h hash-string.h libgettext.h loadinfo.h bindtextdom.c dcgettext.c dgettext.c gettext.c finddomain.c loadmsgcat.c localealias.c textdomain.c l10nflist.c explodename.c intl-compat.c cat-compat.c"; \
for file in $dists; do \
/usr/bin/install -c -m 644 ../../binutils-2.15.91.0.2/intl/$file /tools/share/gettext/intl/$file; \
done; \
else \
: ; \
fi
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/intl'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/ld/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/ld/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
/bin/sh ../../binutils-2.15.91.0.2/ld/../mkinstalldirs /tools/bin /tools/i686-pc-linux-gnu/bin
/bin/sh ./libtool --mode=install /usr/bin/install -c ld-new /tools/bin/ld
/usr/bin/install -c ld-new /tools/bin/ld
n=`echo ld | sed 's,y,y,'`; \
if [ "/tools/bin/$n" != "/tools/i686-pc-linux-gnu/bin/ld" ]; then \
rm -f /tools/i686-pc-linux-gnu/bin/ld; \
ln /tools/bin/$n /tools/i686-pc-linux-gnu/bin/ld >/dev/null 2>/dev/null \
|| /bin/sh ./libtool --mode=install /usr/bin/install -c ld-new /tools/i686-pc-linux-gnu/bin/ld; \
fi
make install-man1
make[4]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
/bin/sh ../../binutils-2.15.91.0.2/ld/../mkinstalldirs /tools/man/man1
/usr/bin/install -c -m 644 ld.1 /tools/man/man1/ld.1
make[4]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
/bin/sh ../../binutils-2.15.91.0.2/ld/../mkinstalldirs /tools/i686-pc-linux-gnu/lib/ldscripts
for f in ldscripts/*; do \
/usr/bin/install -c -m 644 $f /tools/i686-pc-linux-gnu/lib/$f ; \
done
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
Making install-info in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/ld/po'
make[2]: Nothing to be done for `install-info'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/ld/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
/bin/sh ../../binutils-2.15.91.0.2/ld/../mkinstalldirs /tools/info
/usr/bin/install -c -m 644 ./ld.info /tools/info/ld.info
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/libiberty'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/libiberty/testsuite'
/bin/sh ../../binutils-2.15.91.0.2/libiberty/../mkinstalldirs /tools/lib
/usr/bin/install -c -m 644 ./libiberty.a /tools/lib/./libiberty.an
( cd /tools/lib ; ranlib ./libiberty.an )
mv -f /tools/lib/./libiberty.an /tools/lib/./libiberty.a
if test -n ""; then \
case "" in \
/*) thd=;; \
*) thd=/tools/include/;; \
esac; \
/bin/sh ../../binutils-2.15.91.0.2/libiberty/../mkinstalldirs ${thd}; \
for h in ../../binutils-2.15.91.0.2/libiberty/../include/ansidecl.h ../../binutils-2.15.91.0.2/libiberty/../include/demangle.h ../../binutils-2.15.91.0.2/libiberty/../include/dyn-string.h ../../binutils-2.15.91.0.2/libiberty/../include/fibheap.h ../../binutils-2.15.91.0.2/libiberty/../include/floatformat.h ../../binutils-2.15.91.0.2/libiberty/../include/hashtab.h ../../binutils-2.15.91.0.2/libiberty/../include/libiberty.h ../../binutils-2.15.91.0.2/libiberty/../include/objalloc.h ../../binutils-2.15.91.0.2/libiberty/../include/partition.h ../../binutils-2.15.91.0.2/libiberty/../include/safe-ctype.h ../../binutils-2.15.91.0.2/libiberty/../include/sort.h ../../binutils-2.15.91.0.2/libiberty/../include/splay-tree.h ../../binutils-2.15.91.0.2/libiberty/../include/ternary.h; do \
/usr/bin/install -c -m 644 $h ${thd}; \
done; \
fi
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/libiberty/testsuite'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/libiberty/testsuite'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/libiberty'
|
|
|
|
|
|
07-08-2005, 10:46 PM
|
#8
|
|
Member
Registered: Oct 2004
Location: somewhere in the street
Distribution: Window$
Posts: 192
Rep:
|
Quote:
Originally posted by microsoft/linux
yeah, it was kind of a typo. I didn't realize when running '../binutils-2<etc. etc.>/configure --prefix=/tools \ --disable-nls' that you had to hit enter before the '--disable-nls' gibing you the second line on which to specify --disable-nls. S that worked and I got up to 'make install'. Tried it as user lfs, and it gave me a permission denied error. So then I tried it as root, and the output is here
|
I think, you should change owner of /mnt/lfs/tools to lfs as LFS book suggest:
Cheers,
GH |
|
|
|
|
07-09-2005, 04:31 PM
|
#9
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Original Poster
Rep:
|
I beleive it is owned by lfs. Would doing that as root do anything? other thoughts? Thanks for the help
|
|
|
|
|
07-09-2005, 05:35 PM
|
#10
|
|
Senior Member
Registered: May 2004
Location: Sebec, ME, USA
Distribution: Debian Etch, Windows XP Home, FreeBSD
Posts: 1,445
Original Poster
Rep:
|
yes the entire /mnt/lfs is owned by user lfs. The ouput posted above is what happens when 'make install' is done as root.
Here is the output from doing 'make install' as lfs
Quote:
/bin/sh ../binutils-2.15.91.0.2/mkinstalldirs /tools /tools
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
Making install in doc
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/doc'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
/bin/sh ../../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/info
/usr/bin/install -c -m 644 ./bfd.info /tools/info/bfd.info
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/doc'
Making install in po
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Nothing to be done for `install'.
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd/po'
make[2]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Entering directory `/mnt/lfs/sources/binutils-build/bfd'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/lib
/bin/sh ../../binutils-2.15.91.0.2/bfd/../mkinstalldirs /tools/include
/bin/sh ./libtool --mode=install /usr/bin/install -c libbfd.la /tools/lib/libbfd.la
/usr/bin/install -c .libs/libbfd.lai /tools/lib/libbfd.la
make[3]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[2]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/bfd'
|
Sorry about the mix up.  |
|
|
|
All times are GMT -5. The time now is 08:00 AM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
