Re: How overcome error installing GCC-4.3.2

Re: How overcome error installing GCC-4.3.2

[Sergio Rojas]

Thanks Brian. You were right. For some reason 
the gcc-4.3.2 tree was missing the "include" directory.

Now the error is as follows:

/usr/sfw/bin/gcc   -g -fkeep-inline-functions -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -DGENERATOR_FILE -L/usr/sfw/lib/amd64 -R/usr/sfw/lib/amd64  -o build/genmodes \
    build/genmodes.o build/errors.o ../build-i386-pc-solaris2.10/libiberty/libiberty.a
ld: warning: file ../build-i386-pc-solaris2.10/libiberty/libiberty.a(hashtab.o): wrong ELF class: ELFCLASS64
Undefined                       first referenced
 symbol                             in file
htab_create_alloc                   build/genmodes.o
htab_find                           build/genmodes.o
xcalloc                             build/genmodes.o
htab_hash_string                    build/genmodes.o
htab_find_slot                      build/genmodes.o
xmalloc                             build/genmodes.o
xstrdup                             build/genmodes.o
ld: fatal: Symbol referencing errors. No output written to build/genmodes
collect2: ld returned 1 exit status
gmake[3]: *** [build/genmodes] Error 1
gmake[3]: Leaving directory `/home/srojas/MySoftware/my_install/gcc'
gmake[2]: *** [all-stage1-gcc] Error 2
gmake[2]: Leaving directory `/home/srojas/MySoftware/my_install'
gmake[1]: *** [stage1-bubble] Error 2
gmake[1]: Leaving directory `/home/srojas/MySoftware/my_install'
gmake: *** [bootstrap] Error 2

Please, advise me on possible way to finish the compilation
correctly.

Regards,

Sergio

----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@gcc.gnu.org
Subject: Re: How overcome error installing GCC-4.3.2
Date: Thu, 04 Dec 2008 19:14:41 -0800


Sergio Rojas wrote:

> gmake[3]: *** No rule to make target
> `../../gcc-4.3.2/libiberty/../include/ansidecl.h', needed by
> `regex.o'.  Stop.

Does the file gcc-4.3.2/include/ansidecl.h exist?  If no, then something
is wrong as you have an incomplete tree.

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> ld: warning: file ../build-i386-pc-solaris2.10/libiberty/libiberty.a(hashtab.o): wrong ELF class: ELFCLASS64
> Undefined                       first referenced
>  symbol                             in file
> htab_create_alloc                   build/genmodes.o

It looks like it's trying to link a 32 bit genmodes with a 64 bit
libiberty.  That's probably because you configured with CFLAGS=-m64. 
I'm not sure why you're doing that, it shouldn't be necessary. 
i386-pc-solaris2.10 should be bi-arch by default without you having to
set anything.

Brian

Re: How overcome error installing GCC-4.3.2

[Sergio Rojas]

OK. I now switched gcc-4.2.2 and gcc-4.2.3 In both cases the compilations seems
to have been succesful (gmake ended without errors). I am wondering whether one 
could  make a full test of the compilation without installing DejaGnu, Tcl, and Expect. 

The installation seems to have been OK. The Expect installation is
given this error

usr/sfw/bin/gcc -c  -I. -I. -I/home/srojas/MySoftware/tcl8.5.5/generic   -DEXP_VERSION=\"5.43.0\" -DSCRIPTDIR=\"/home/srojas/My_prog/expect-5.43/lib/expect5.43\" -DEXECSCRIPTDIR=\"/home/srojas/My_prog/expect-5.43/lib/expect5.43\" -DTCL_DEBUGGER -DUSE_NON_CONST -DSTTY_BIN=\"/bin/stty\" -I/home/srojas/MySoftware/tcl8.5.5/unix   -pipe  -DDFLT_STTY="\"sane\""  exp_inter.c
exp_inter.c: In function `intMatch':
exp_inter.c:294: error: `TCL_REG_BOSONLY' undeclared (first use in this function)


Sergio

----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@gcc.gnu.org
Subject: Re: How overcome error installing GCC-4.3.2
Date: Sun, 07 Dec 2008 12:57:23 -0800


Sergio Rojas wrote:

> Brian, I switched  to the gnu linker, the error now looks like:

Note that the target-specific install notes recommend the opposite for
Solaris 10, the GNU assembler and Sun linker:


>  [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 
> amd64/libgcc_s.so.1.backup; else true; fi && mv 
> amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s 
> libgcc_s.so.1 amd64/libgcc_s.so
> /usr/sfw/bin/gld: cannot open linker script file 
> ldscripts/elf_x86_64.xsc: No such file or directory
>
> I searched ( find / -name elf_x86_64.xsc -print) without success 
> for that file "elf_x86_64.xsc"
> in my Solaris 10 distribution. Any advise were to go for it?

It's trying to link a 64 bit library, but apparently your gld doesn't
have 64 bit support installed.  You could build the linker yourself
(from binutils), but given the above I don't think it would be the best
use of time.

> By the way, Brian, as I understand, the workaround you mentioned 
> below, which is
> formally listed at: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00441.html
> should be included in the "gcc/config.gcc". At what level in the script
> should one includes the suggested lines?

It's a diff that's meant to be applied with the patch program.  It uses
the line number hints (@@) as well as the surrounding context to make
the intended changes.  Alternatively since this patch has already been
applied to the gcc-4_3-branch in svn you could just use that (or a
recent 4.3 snapshot tarball.)

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> Brian, I switched  to the gnu linker, the error now looks like:

Note that the target-specific install notes recommend the opposite for
Solaris 10, the GNU assembler and Sun linker:
<http://gcc.gnu.org/install/specific.html#ix86-x-solaris210>

>  [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 amd64/libgcc_s.so.1.backup; else true; fi && mv amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s libgcc_s.so.1 amd64/libgcc_s.so
> /usr/sfw/bin/gld: cannot open linker script file ldscripts/elf_x86_64.xsc: No such file or directory
> 
> I searched ( find / -name elf_x86_64.xsc -print) without success for that file "elf_x86_64.xsc"
> in my Solaris 10 distribution. Any advise were to go for it?

It's trying to link a 64 bit library, but apparently your gld doesn't
have 64 bit support installed.  You could build the linker yourself
(from binutils), but given the above I don't think it would be the best
use of time.

> By the way, Brian, as I understand, the workaround you mentioned below, which is
> formally listed at: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00441.html
> should be included in the "gcc/config.gcc". At what level in the script
> should one includes the suggested lines?

It's a diff that's meant to be applied with the patch program.  It uses
the line number hints (@@) as well as the surrounding context to make
the intended changes.  Alternatively since this patch has already been
applied to the gcc-4_3-branch in svn you could just use that (or a
recent 4.3 snapshot tarball.)

Brian

Re: How overcome error installing GCC-4.3.2

[Sergio Rojas]

Brian, I switched  to the gnu linker, the error now looks like:

 [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 amd64/libgcc_s.so.1.backup; else true; fi && mv amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s libgcc_s.so.1 amd64/libgcc_s.so
/usr/sfw/bin/gld: cannot open linker script file ldscripts/elf_x86_64.xsc: No such file or directory

I searched ( find / -name elf_x86_64.xsc -print) without success for that file "elf_x86_64.xsc" 
in my Solaris 10 distribution. Any advise were to go for it?

By the way, Brian, as I understand, the workaround you mentioned below, which is
formally listed at: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00441.html
should be included in the "gcc/config.gcc". At what level in the script
should one includes the suggested lines?


Sergio
----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@gcc.gnu.org
Subject: Re: How overcome error installing GCC-4.3.2
Date: Fri, 05 Dec 2008 15:12:07 -0800


Sergio Rojas wrote:

> I though that "--with-mpfr=$MPFRDIR and --with-gmp=$GMPDIR"
> were taken care of that. Well, now the error is as follows

Those options tell the compiler and link editor where to find the files
during compilation and linking.  They don't tell the operating system's
dynamic loader where to find the libraries at runtime.

> (after setting LD_LIBRARY_PATH to the respectives libraries dir
> and also LDFLAGS="-L$MPFRDIR -R$MPFRDIR -L$GMPDIR -R$GMPDIR"):

You really shouldn't have to set LDFLAGS.  Just the --with options alone
should take care of it.

> & if [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 
> amd64/libgcc_s.so.1.backup; else true; fi && mv 
> amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s 
> libgcc_s.so.1 amd64/libgcc_s.so
> ld: fatal: unwind table: file 
> /home/srojas/MySoftware/my_install/./gcc/amd64/crtend.o: section 
> .eh_frame: bad cie version 0: offset 0xfffffd7fffdfa200

This is a bug in Sun's linker, see
 which includes a
workaround (which will be in 4.3.3.)

> By the way, is there a way to track at which stage of the 
> compilation the script is stopping?

If you watch the build messages you'll regularly see e.g. "Configuring
stage 1 in i386-pc-solaris2.10/libgcc" scroll by, so just scroll up from
the error to the first such line.  (It helps to log the output and then
you can grep instead.)  You can also 'cat stage_current' which should
tell you the current state of the tree at any given time.

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: How overcome error installing GCC-4.3.2

[Sergio Rojas]

I am sorry Brian. You should have spent your time
in a more knowledgeable profitable task, instead of 
dealing with a SUN MYCROSYSTEM SOLARIS BUG.

I see now the reasonable blaming people make because so many
SUN-SOLARIS bugs.

I am wondering,
why AMD did not go to a better company? I mean
too many bugs in SUN SOLARIS!!!. Either the
managers at SUN did not care about the damage they
are making to the developer community
or they are too stubborn to realize such amount of
damage and be aware of the clear amount of mistakes
SUN MICROSYSTEM intentionally have made around the world.\

It is clear, after searching the internet,  that SUN MYCROSYSTEM
have intentionally made available a buggy system. Why AMD is following
so desastrous company is a mistery.  This is thel ast HPF AMD
processor on my part!!!! My boss could fire me, but I will not val any
purchae of AMD pocessors under SOLARIS !!!


egio
----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@gcc.gnu.org
Subject: Re: How overcome error installing GCC-4.3.2
Date: Fri, 05 Dec 2008 15:12:07 -0800


Sergio Rojas wrote:

> I though that "--with-mpfr=$MPFRDIR and --with-gmp=$GMPDIR"
> were taken care of that. Well, now the error is as follows

Those options tell the compiler and link editor where to find the files
during compilation and linking.  They don't tell the operating system's
dynamic loader where to find the libraries at runtime.

> (after setting LD_LIBRARY_PATH to the respectives libraries dir
> and also LDFLAGS="-L$MPFRDIR -R$MPFRDIR -L$GMPDIR -R$GMPDIR"):

You really shouldn't have to set LDFLAGS.  Just the --with options alone
should take care of it.

> & if [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 
> amd64/libgcc_s.so.1.backup; else true; fi && mv 
> amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s 
> libgcc_s.so.1 amd64/libgcc_s.so
> ld: fatal: unwind table: file 
> /home/srojas/MySoftware/my_install/./gcc/amd64/crtend.o: section 
> .eh_frame: bad cie version 0: offset 0xfffffd7fffdfa200

This is a bug in Sun's linker, see
 which includes a
workaround (which will be in 4.3.3.)

> By the way, is there a way to track at which stage of the 
> compilation the script is stopping?

If you watch the build messages you'll regularly see e.g. "Configuring
stage 1 in i386-pc-solaris2.10/libgcc" scroll by, so just scroll up from
the error to the first such line.  (It helps to log the output and then
you can grep instead.)  You can also 'cat stage_current' which should
tell you the current state of the tree at any given time.

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> I though that "--with-mpfr=$MPFRDIR and --with-gmp=$GMPDIR"
> were taken care of that. Well, now the error is as follows

Those options tell the compiler and link editor where to find the files
during compilation and linking.  They don't tell the operating system's
dynamic loader where to find the libraries at runtime.

> (after setting LD_LIBRARY_PATH to the respectives libraries dir
> and also LDFLAGS="-L$MPFRDIR -R$MPFRDIR -L$GMPDIR -R$GMPDIR"):

You really shouldn't have to set LDFLAGS.  Just the --with options alone
should take care of it.

> & if [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 amd64/libgcc_s.so.1.backup; else true; fi && mv amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s libgcc_s.so.1 amd64/libgcc_s.so
> ld: fatal: unwind table: file /home/srojas/MySoftware/my_install/./gcc/amd64/crtend.o: section .eh_frame: bad cie version 0: offset 0xfffffd7fffdfa200

This is a bug in Sun's linker, see
<http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33100> which includes a
workaround (which will be in 4.3.3.)

> By the way, is there a way to track at which stage of the compilation the script is stopping?

If you watch the build messages you'll regularly see e.g. "Configuring
stage 1 in i386-pc-solaris2.10/libgcc" scroll by, so just scroll up from
the error to the first such line.  (It helps to log the output and then
you can grep instead.)  You can also 'cat stage_current' which should
tell you the current state of the tree at any given time.

Brian

Re: How overcome error installing GCC-4.3.2

[Sergio Rojas]

I though that "--with-mpfr=$MPFRDIR and --with-gmp=$GMPDIR"
were taken care of that. Well, now the error is as follows
(after setting LD_LIBRARY_PATH to the respectives libraries dir
and also LDFLAGS="-L$MPFRDIR -R$MPFRDIR -L$GMPDIR -R$GMPDIR"):

& if [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 amd64/libgcc_s.so.1.backup; else true; fi && mv amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s libgcc_s.so.1 amd64/libgcc_s.so
ld: fatal: unwind table: file /home/srojas/MySoftware/my_install/./gcc/amd64/crtend.o: section .eh_frame: bad cie version 0: offset 0xfffffd7fffdfa200

collect2: ld returned 1 exit status
gmake[5]: *** [libgcc_s.so] Error 1
gmake[5]: Leaving directory `/home/srojas/MySoftware/my_install/i386-pc-solaris2.10/amd64/libgcc'
gmake[4]: *** [multi-do] Error 1

By the way, is there a way to track at which stage of the compilation the script is stopping?

Sergio



----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@gcc.gnu.org
Subject: Re: How overcome error installing GCC-4.3.2
Date: Fri, 05 Dec 2008 13:31:17 -0800


Sergio Rojas wrote:

> OK. I am using the flag -m64 to have everything compiled
> with the same options, so one could make use of the processor
> 64 bit computational capabilities.

In general setting CFLAGS=-m64 is a terrible idea because that disables
all optimizations!  Remember, you only get the default "-g -O2" setting
of CFLAGS if you don't override it, and the compiler only optimizes when
-O is specified.  So what you probably want is CFLAGS="-m64 -g -O2".
For this reason it's traditional when doing this to set it in $CC
instead, e.g. CC="gcc -m64", and leave CFLAGS untouched.

In the specific case of bootstrapping gcc however, everything's a little
more complicated.  I think that you would have to override both CFLAGS
and BOOT_CFLAGS, and setting -m64 in CC wouldn't work as that would only
apply to the stage1.

> checking for i386-pc-solaris2.10-gcc...
> /home/srojas/MySoftware/my_install/./gcc/xgcc
> -B/home/srojas/MySoftware/my_install/./gcc/
> -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/bin/
> -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/lib/ -isystem
> /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/include -isystem
> /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/sys-include
> checking for suffix of object files... configure: error: cannot
> compute suffix of object files: cannot compile
> See `config.log' for more details.

Well, what does config.log say?  Note that you need to look in the
correct one, corresponding to the dir where it was running configure
when the error occured.  The usual cause of this error (if this is in
libgcc/) is that the loader can't find the gmp/mpfr libraries when
trying to exec cc1 for the first time, which happens if you installed
shared libraries outside of the system default paths and didn't add the
location to LD_LIBRARY_PATH.  (There should have been a message about
this when you ran "make install" for gmp and mpfr.)

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> OK. I am using the flag -m64 to have everything compiled
> with the same options, so one could make use of the processor
> 64 bit computational capabilities. 

In general setting CFLAGS=-m64 is a terrible idea because that disables
all optimizations!  Remember, you only get the default "-g -O2" setting
of CFLAGS if you don't override it, and the compiler only optimizes when
-O is specified.  So what you probably want is CFLAGS="-m64 -g -O2". 
For this reason it's traditional when doing this to set it in $CC
instead, e.g. CC="gcc -m64", and leave CFLAGS untouched.

In the specific case of bootstrapping gcc however, everything's a little
more complicated.  I think that you would have to override both CFLAGS
and BOOT_CFLAGS, and setting -m64 in CC wouldn't work as that would only
apply to the stage1.
  
> checking for i386-pc-solaris2.10-gcc...
> /home/srojas/MySoftware/my_install/./gcc/xgcc
> -B/home/srojas/MySoftware/my_install/./gcc/
> -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/bin/
> -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/lib/ -isystem
> /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/include -isystem
> /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/sys-include
> checking for suffix of object files... configure: error: cannot
> compute suffix of object files: cannot compile
> See `config.log' for more details.

Well, what does config.log say?  Note that you need to look in the
correct one, corresponding to the dir where it was running configure
when the error occured.  The usual cause of this error (if this is in
libgcc/) is that the loader can't find the gmp/mpfr libraries when
trying to exec cc1 for the first time, which happens if you installed
shared libraries outside of the system default paths and didn't add the
location to LD_LIBRARY_PATH.  (There should have been a message about
this when you ran "make install" for gmp and mpfr.)

Brian

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> gmake[3]: *** No rule to make target
> `../../gcc-4.3.2/libiberty/../include/ansidecl.h', needed by
> `regex.o'.  Stop.

Does the file gcc-4.3.2/include/ansidecl.h exist?  If no, then something
is wrong as you have an incomplete tree.

Brian

Re: How overcome error installing GCC-4.3.2

[Brian Dessent]

Sergio Rojas wrote:

> make: Fatal error: Don't know how to make target `../../gcc-4.3.2/include/ansidecl.h'
> Current working directory /home/srojas/MySoftware/my_ins/libiberty
> *** Error code 1
> The following command caused the error:

That does not look like the output of GNU make.  You can't use Solaris'
make to build gcc, GNU make is required.  Make sure you meet everything
listed in the prerequisites section of the installation instructions at
<http://gcc.gnu.org/install/>.

Brian

How overcome error installing GCC-4.3.2

[Sergio Rojas]

Hello folks, 

  I am wondering if anyone could share advice on how
to overcome the following problem, which is
obtained when trying to install gcc-4.3.2 on a box operating
two dual core AMD 64 bit processors under Solaris 10.

The configure set up, which finished without errors, is as follows:

../gcc-4.3.2/configure --prefix=/home/srojas/My_prog/GCC4_64bit  CC=/usr/sfw/bin/gcc              CFLAGS=-m64 LDFLAGS="-L/usr/sfw/lib/amd64 -R/usr/sfw/lib/amd64" CXX=/usr/sfw/bin/g++              CXXFLAGS=-m64  --with-mpfr=/home/srojas/My_prog/MPFR_64bit               --with-gmp=/home/srojas/My_prog/GMP_abi64   --enable-languages=c,c++,fortran,java               --enable-threads --enable-shared 

A portion of the make errors are:

config.status: config.h is unchanged
config.status: executing default commands
make: Fatal error: Don't know how to make target `../../gcc-4.3.2/include/ansidecl.h'
Current working directory /home/srojas/MySoftware/my_ins/libiberty
*** Error code 1
The following command caused the error:
r=`${PWDCMD-pwd}`; export r; \
s=`cd ../gcc-4.3.2; ${PWDCMD-pwd}`; export s; \
FLEX="/home/srojas/MySoftware/gcc-4.3.2/missing flex"; export FLEX;  LEX="lex";
...
...
ake: Fatal error: Command failed for target `all-stage1-libiberty'
Current working directory /home/srojas/MySoftware/my_ins
*** Error code 1
The following command caused the error:
r=`${PWDCMD-pwd}`; export r; \
s=`cd ../gcc-4.3.2; ${PWDCMD-pwd}`; export s; \
if test -f stage1-lean  ; then \
  echo Skipping rebuild of stage1 ; \
else \
  make stage1-start; \
  make "DESTDIR="  "RPATH_ENVVAR=LD_LIBRARY_PATH"  "TARGET_SUBDIR=i386-pc-solaris2.10"  "bindir=/home/srojas/My_prog/GCC4_64bit/bin" 
...
...
AKEINFO=/home/srojas/MySoftware/gcc-4.3.2/missing makeinfo --split-size=5000000 --split-size=5000000" all-stage1; \
fi
make: Fatal error: Command failed for target `stage1-bubble'
Current working directory /home/srojas/MySoftware/my_ins
*** Error code 1
The following command caused the error:
r=`${PWDCMD-pwd}`; export r; \
s=`cd ../gcc-4.3.2; ${PWDCMD-pwd}`; export s; \
make "DESTDIR="  "RPATH_ENVVAR=LD_LIBRARY_PATH"  "TARGET_SUBDIR=i386-pc-solaris2.10"  "bindir=/home/srojas/My_prog/GCC4_64bit/bin"  
...
...
FOO=/'`"  "LEAN=false"  "CONFIG_SHELL=/bin/bash"  "MAKEINFO=/home/srojas/MySoftware/gcc-4.3.2/missing makeinfo --split-size=5000000" `cat stage_final`-bubble
make: Fatal error: Command failed for target `all'


Thanks in advance.

Sergio

-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com