LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 06-26-2014, 10:01 AM   #1
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Rep: Reputation: Disabled
Linux from scratch on top of debian!


Hi all,

I am trying to compile the latest sources as listed in lfs on top of my debian 7.5 wheezy.

Lets see how this end !!!

Any suggestions?
 
Old 06-26-2014, 02:31 PM   #2
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,307
Blog Entries: 2

Rep: Reputation: Disabled
Make sure you back up everything before you begin
 
Old 06-26-2014, 05:22 PM   #3
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dijetlo View Post
Make sure you back up everything before you begin
Yup. Double backed up !!!
 
Old 06-27-2014, 04:13 AM   #4
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
Didnt work out. I compiled all the necessary software. But when I rebooted, the sys hangs. Had to reinstall the debian sys.
 
Old 06-27-2014, 05:19 AM   #5
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Then at some point you forgot to su to lfs system & ran the commands in your debian path. On next go around you may want to do it in virtualbox. That way if you forget to su into lfs it doesn't Affect your main system.
Believe me I have done it while on my first run & second run for buiding my tool chain. Also next time it happens try resetting your path in debian before reinstalling debian.
Good Luck on your next run.
P.S. Before you start your next run, check & copy your path even if you save it in text document under libreoffice. That way you will know the original path.
 
Old 06-27-2014, 09:01 AM   #6
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by EDDY1 View Post
Then at some point you forgot to su to lfs system & ran the commands in your debian path. On next go around you may want to do it in virtualbox. That way if you forget to su into lfs it doesn't Affect your main system.
Believe me I have done it while on my first run & second run for buiding my tool chain. Also next time it happens try resetting your path in debian before reinstalling debian.
Good Luck on your next run.
P.S. Before you start your next run, check & copy your path even if you save it in text document under libreoffice. That way you will know the original path.

Um. Maybe first i should have done it in Qemu...
 
Old 06-27-2014, 09:02 AM   #7
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
what about 'linux from script'?

Has anybody tried it yet? Does it work as they say?
 
Old 06-27-2014, 06:25 PM   #8
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
I haven't tried it from script, but have from debian & it was a learning experience.
 
Old 06-27-2014, 06:45 PM   #9
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,307
Blog Entries: 2

Rep: Reputation: Disabled
Linux from Scratch, not script.
I make minimal Slackware server stubbs using tag files. It's a very similar process to Linux From Scratch, it works fine as long as your careful to insure you have all the dependencies accounted for.
I'm not sure how it would work on top of (beside?) a debian install, I pull these things into KVM environment where they run as virtual servers, not the same thing.
 
Old 06-28-2014, 03:25 AM   #10
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
Trying it using 'linux from script'. The original lfs book just seems too much work

Lets see how it works out.
 
Old 06-28-2014, 06:52 AM   #11
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
Tried alfs.

Am getting this error. Anybody has any idea?"""

Are you happy with these settings? yes/no (no): y

Rerun make to fix the configuration options.


<jhalfs-trunk> exit
"""
 
Old 06-29-2014, 10:46 AM   #12
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
I tried jhalfs, lfscript.... to no avail. Can Anybody suggest some way I could build linux from scratch? Can I post the errors that i get on this forum?
 
Old 06-29-2014, 11:13 AM   #13
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,307
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Can I post the errors that i get on this forum?
Goodness yes, we love a good error message 'round here.
Quote:
Rerun make to fix the configuration options.
The process for compiling binaries is "configure -> make " so you probably just have to run make again.
Quote:
The original lfs book just seems too much work
Have we reached the point where we're reconsidering that?

You'll often see people post "RTFM" around here. It means " Read the F'ing Manual". If you really want to be proficient with anything in Linux, you eventually have to break down and do it. After a few years, it becomes the first thing you do. When learning something new, I normally read approximately 1000 times as much as I type. It's a productive ratio.

Last edited by dijetlo; 06-29-2014 at 11:14 AM.
 
Old 06-30-2014, 02:50 AM   #14
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
OK: Here goes:

in phase 1, binutils build without errors. But gcc fails to build. The last part of the gcc log file is below: (i have 1gb ram and 8 gb swap space, so that is not an issue).

../../gcc-4.6.2/gcc/doc/cppopts.texi:772: @itemx must follow @item
Makefile:4270: recipe for target 'doc/cpp.info' failed
make[2]: *** [doc/cpp.info] Error 1
make[2]: *** Waiting for unfinished jobs....
../../gcc-4.6.2/gcc/doc/gcc.texi:89: warning: @tex should only appear at a line beginning
../../gcc-4.6.2/gcc/doc/gcc.texi:89: warning: @end should only appear at a line beginning
../../gcc-4.6.2/gcc/doc/gcc.texi:91: warning: @tex should only appear at a line beginning
../../gcc-4.6.2/gcc/doc/gcc.texi:91: warning: @end should only appear at a line beginning
../../gcc-4.6.2/gcc/doc/invoke.texi:168: superfluous argument to @end smallexample: -fdump-go-spec=@var{file} (possibly involving @gccoptlist)
../../gcc-4.6.2/gcc/doc/invoke.texi:5088: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5092: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5103: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5107: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5152: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5182: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:5194: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/cppopts.texi:772: @itemx must follow @item
../../gcc-4.6.2/gcc/doc/invoke.texi:977: warning: node next `Overall Options' in menu `C Dialect Options' and in sectioning `Invoking G++' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:977: warning: node up `Overall Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:1442: warning: node prev `C Dialect Options' in menu `Overall Options' and in sectioning `Invoking G++' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:1442: warning: node up `C Dialect Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:1811: warning: node up `C++ Dialect Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:2513: warning: node up `Objective-C and Objective-C++ Dialect Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:2745: warning: node up `Language Independent Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:2808: warning: node up `Warning Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:4538: warning: node up `Debugging Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:5862: warning: node up `Optimize Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:8917: warning: node up `Preprocessor Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:8955: warning: node up `Assembler Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:8978: warning: node up `Link Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:9230: warning: node up `Directory Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:9374: warning: node up `Spec Files' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/invoke.texi:9936: warning: node up `Target Options' in menu `Option Summary' and in sectioning `Invoking GCC' differ
../../gcc-4.6.2/gcc/doc/implement-c.texi:6: warning: node next `C Implementation' in menu `C Extensions' and in sectioning `C++ Implementation' differ
../../gcc-4.6.2/gcc/doc/implement-cxx.texi:6: warning: node next `C++ Implementation' in menu `C++ Extensions' and in sectioning `C Extensions' differ
../../gcc-4.6.2/gcc/doc/implement-cxx.texi:6: warning: node prev `C++ Implementation' in menu `C Extensions' and in sectioning `C Implementation' differ
../../gcc-4.6.2/gcc/doc/extend.texi:8: warning: node next `C Extensions' in menu `C++ Implementation' and in sectioning `C++ Extensions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:8: warning: node prev `C Extensions' in menu `C Implementation' and in sectioning `C++ Implementation' differ
../../gcc-4.6.2/gcc/doc/extend.texi:771: warning: node next `Conditionals' in menu `Long Long' and in sectioning `__int128' differ
../../gcc-4.6.2/gcc/doc/extend.texi:809: warning: node next `__int128' in menu `Complex' and in sectioning `Long Long' differ
../../gcc-4.6.2/gcc/doc/extend.texi:809: warning: node prev `__int128' in menu `Long Long' and in sectioning `Conditionals' differ
../../gcc-4.6.2/gcc/doc/extend.texi:820: warning: node next `Long Long' in menu `__int128' and in sectioning `Complex' differ
../../gcc-4.6.2/gcc/doc/extend.texi:820: warning: node prev `Long Long' in menu `Conditionals' and in sectioning `__int128' differ
../../gcc-4.6.2/gcc/doc/extend.texi:852: warning: node prev `Complex' in menu `__int128' and in sectioning `Long Long' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1246: warning: node next `Zero Length' in menu `Variable Length' and in sectioning `Empty Structures' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1344: warning: node next `Empty Structures' in menu `Variadic Macros' and in sectioning `Variable Length' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1344: warning: node prev `Empty Structures' in menu `Variable Length' and in sectioning `Zero Length' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1360: warning: node next `Variable Length' in menu `Empty Structures' and in sectioning `Variadic Macros' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1360: warning: node prev `Variable Length' in menu `Zero Length' and in sectioning `Empty Structures' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1441: warning: node prev `Variadic Macros' in menu `Empty Structures' and in sectioning `Variable Length' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1659: warning: node next `Designated Inits' in menu `Cast to Union' and in sectioning `Case Ranges' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1803: warning: node next `Case Ranges' in menu `Mixed Declarations' and in sectioning `Cast to Union' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1803: warning: node prev `Case Ranges' in menu `Cast to Union' and in sectioning `Designated Inits' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1840: warning: node next `Cast to Union' in menu `Case Ranges' and in sectioning `Mixed Declarations' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1840: warning: node prev `Cast to Union' in menu `Designated Inits' and in sectioning `Case Ranges' differ
../../gcc-4.6.2/gcc/doc/extend.texi:1881: warning: node prev `Mixed Declarations' in menu `Case Ranges' and in sectioning `Cast to Union' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10004: warning: node next `MIPS Loongson Built-in Functions' in menu `Other MIPS Built-in Functions' and in sectioning `picoChip Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10407: warning: node next `picoChip Built-in Functions' in menu `PowerPC AltiVec/VSX Built-in Functions' and in sectioning `Other MIPS Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10407: warning: node prev `picoChip Built-in Functions' in menu `Other MIPS Built-in Functions' and in sectioning `MIPS Loongson Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10443: warning: node next `Other MIPS Built-in Functions' in menu `picoChip Built-in Functions' and in sectioning `PowerPC AltiVec/VSX Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10443: warning: node prev `Other MIPS Built-in Functions' in menu `MIPS Loongson Built-in Functions' and in sectioning `picoChip Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:10455: warning: node prev `PowerPC AltiVec/VSX Built-in Functions' in menu `picoChip Built-in Functions' and in sectioning `Other MIPS Built-in Functions' differ
../../gcc-4.6.2/gcc/doc/extend.texi:13701: warning: node prev `C++ Extensions' in menu `C++ Implementation' and in sectioning `C Extensions' differ
../../gcc-4.6.2/gcc/doc/trouble.texi:7: warning: node next `Trouble' in menu `Service' and in sectioning `Bugs' differ
../../gcc-4.6.2/gcc/doc/trouble.texi:7: warning: node prev `Trouble' in menu `Bug Reporting' and in sectioning `Gcov' differ
../../gcc-4.6.2/gcc/doc/trouble.texi:7: warning: node up `Trouble' in menu `Bugs' and in sectioning `Top' differ
../../gcc-4.6.2/gcc/doc/service.texi:6: warning: node prev `Service' in menu `Trouble' and in sectioning `Bugs' differ
../../gcc-4.6.2/gcc/doc/service.texi:6: warning: node up `Service' in menu `Bugs' and in sectioning `Top' differ
Makefile:4270: recipe for target 'doc/gcc.info' failed
make[2]: *** [doc/gcc.info] Error 1
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/gcc'
Makefile:5256: recipe for target 'all-gcc' failed
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build'
Makefile:877: recipe for target 'all' failed
make: *** [all] Error 2

*** BUILD_PROBLEM_DETECTED ***

make[1]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build'
/bin/sh ../gcc-4.6.2/mkinstalldirs /tools /tools
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/fixincludes'
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/lto-plugin'
rm -rf /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools
/bin/sh ../../gcc-4.6.2/fixincludes/../mkinstalldirs /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools
make[3]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/lto-plugin'
test -z "/tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2" || /bin/mkdir -p "/tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2"
make[3]: Nothing to be done for 'install-data-am'.
mkdir -p -- /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools
/bin/sh ../../gcc-4.6.2/fixincludes/../mkinstalldirs /tools/lib/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/include
/bin/sh ./libtool --tag=disable-static --mode=install /usr/bin/install -c liblto_plugin.la '/tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2'
mkdir -p -- /tools/lib/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/include
/usr/bin/install -c -m 644 ../../gcc-4.6.2/fixincludes/README-fixinc \
/tools/lib/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/include/README
/usr/bin/install -c fixinc.sh /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/fixinc.sh
/usr/bin/install -c fixincl \
/tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/fixincl
/usr/bin/install -c mkheaders /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/install-tools/mkheaders
libtool: install: /usr/bin/install -c .libs/liblto_plugin.so.0.0.0 /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/liblto_plugin.so.0.0.0
libtool: install: (cd /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2 && { ln -s -f liblto_plugin.so.0.0.0 liblto_plugin.so.0 || { rm -f liblto_plugin.so.0 && ln -s liblto_plugin.so.0.0.0 liblto_plugin.so.0; }; })
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/fixincludes'
libtool: install: (cd /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2 && { ln -s -f liblto_plugin.so.0.0.0 liblto_plugin.so || { rm -f liblto_plugin.so && ln -s liblto_plugin.so.0.0.0 liblto_plugin.so; }; })
libtool: install: /usr/bin/install -c .libs/liblto_plugin.lai /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2/liblto_plugin.la
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/intl'
make[2]: Nothing to be done for 'install'.
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/intl'
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libcpp'
test -f config.h || (rm -f stamp-h1 && make stamp-h1)
cats=""; for cat in $cats; do \
lang=`basename $cat | sed 's/\.gmo$//'`; \
if [ -f $cat ]; then :; \
elif [ -f ../../gcc-4.6.2/libcpp/$cat ]; then cat=../../gcc-4.6.2/libcpp/$cat; \
else continue; \
fi; \
dir=/tools/share/locale/$lang/LC_MESSAGES; \
echo /usr/bin/install -c -m 644 $cat $dir/cpplib.mo; \
/usr/bin/install -c -m 644 $cat $dir/cpplib.mo; \
done
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libcpp'
libtool: finish: PATH="/tools/bin:/bin:/usr/bin:/sbin" ldconfig -n /tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libdecnumber'
make[2]: Nothing to be done for 'install'.
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libdecnumber'
----------------------------------------------------------------------
Libraries have been installed in:
/tools/libexec/gcc/x86_64-lfs-linux-gnu/4.6.2

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.
----------------------------------------------------------------------
make[3]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/lto-plugin'
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/lto-plugin'
make[2]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty'
/bin/sh: line 3: cd: x86_64-lfs-linux-gnu/libgcc: No such file or directory
Makefile:13305: recipe for target 'install-target-libgcc' failed
make[1]: *** [install-target-libgcc] Error 1
make[1]: *** Waiting for unfinished jobs....
make[3]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty/testsuite'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty/testsuite'
make[3]: Entering directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty/testsuite'
make[3]: Nothing to be done for 'install'.
make[3]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty/testsuite'
/bin/sh ../../gcc-4.6.2/libiberty/../mkinstalldirs /tools/lib/`gcc -g -O2 -print-multi-os-directory`
/usr/bin/install -c -m 644 ./libiberty.a /tools/lib/`gcc -g -O2 -print-multi-os-directory`/./libiberty.an
( cd /tools/lib/`gcc -g -O2 -print-multi-os-directory` ; chmod 644 ./libiberty.an ;ranlib ./libiberty.an )
mv -f /tools/lib/`gcc -g -O2 -print-multi-os-directory`/./libiberty.an /tools/lib/`gcc -g -O2 -print-multi-os-directory`/./libiberty.a
if test -n ""; then \
case "" in \
/*) thd=;; \
*) thd=/tools/include/;; \
esac; \
/bin/sh ../../gcc-4.6.2/libiberty/../mkinstalldirs ${thd}; \
for h in ../../gcc-4.6.2/libiberty/../include/ansidecl.h ../../gcc-4.6.2/libiberty/../include/demangle.h ../../gcc-4.6.2/libiberty/../include/dyn-string.h ../../gcc-4.6.2/libiberty/../include/fibheap.h ../../gcc-4.6.2/libiberty/../include/floatformat.h ../../gcc-4.6.2/libiberty/../include/hashtab.h ../../gcc-4.6.2/libiberty/../include/libiberty.h ../../gcc-4.6.2/libiberty/../include/objalloc.h ../../gcc-4.6.2/libiberty/../include/partition.h ../../gcc-4.6.2/libiberty/../include/safe-ctype.h ../../gcc-4.6.2/libiberty/../include/sort.h ../../gcc-4.6.2/libiberty/../include/splay-tree.h; do \
/usr/bin/install -c -m 644 $h ${thd}; \
done; \
fi
make[2]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build/libiberty'
make[1]: Leaving directory '/home/build/Desktop/lfscript4-revision21/builddir.23952.tmp/sources/builddir/gcc-build'
Makefile:2689: recipe for target 'install' failed
make: *** [install] Error 2

*** BUILD_PROBLEM_DETECTED ***

/sources/buildmgr/scripts/lfs-9742/gcc: line 84: x86_64-lfs-linux-gnu-gcc: command not found
'./libgcc.a' -> 'libgcc.a'
 
Old 06-30-2014, 04:17 AM   #15
manishthatte
Member
 
Registered: May 2014
Distribution: Linux from scratch, Ubuntu, Mint, Slackware
Posts: 53

Original Poster
Rep: Reputation: Disabled
As per advice given by djetlo I f**ing have started to read the lfs book again And begun compiling again. no errors for binutils so far. Will post further progress.

Caio !!!
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: News: Linux Top 3: Nussbaum Remains Debian Project Leader, Heartbleed Hits Linux and Linux 3.1 LXer Syndicated Linux News 0 04-15-2014 03:30 PM
Linux from scratch to Debian Badal Naik Linux From Scratch 8 09-01-2013 06:08 AM


All times are GMT -5. The time now is 08:59 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration