linux-mips
[Top] [All Lists]

RE: problem building cross compiler gcc-3.4.4

To: <linux-mips@linux-mips.org>
Subject: RE: problem building cross compiler gcc-3.4.4
From: "De Jong, Rienco" <Marinus.DeJong@flir.com>
Date: Tue, 16 May 2006 07:49:15 -0700
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Thread-index: AcZ4qpak6ACT7djqRd+dkBQ0ILv95QAS9rBQ
Thread-topic: problem building cross compiler gcc-3.4.4
Hi Shyamal,

I also have problems with compiling a mips platform for threads.  I used
the buildroot environment but made no progress.  I am able to compile
buildroot for the old/stable version of linux threads which also
includes a version of gcc.  I also tried posting to this list but have
heard no response as of yet so this is probably not the right list for
this kind of question.

I was trying to get the use of the NPTL. Are you trying to build for
NPTL as well?  If not you should be able to use the previous build of
the compiler to build the old and stable version of linux threads.
Apparently gcc doesn't need to have the --enable_threads flag set for
that but I can't say for sure.

Rienco De Jong


-----Original Message-----
From: linux-mips-bounce@linux-mips.org
[mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Shyamal Sadanshio
Sent: Monday, May 15, 2006 10:35 PM
To: linux-mips@linux-mips.org
Subject: Fwd: problem building cross compiler gcc-3.4.4

Hi,

I am facing gcc 3.4.4 build problem for mips platform with
--enable-thread options.

../gcc-3.4.4/configure --target=$TARGET --prefix=$PREFIX
--enable-language=c
--with-headers=/opt/crosstool/mipsel-unknown-linux-gnu/sys-include/
--with-gnu-ld --with-gnu-as --disable-shared --enable-threads

Error message are listed as below:
************************************************************************
*************************
In file included from ./tm.h:13,
                 from ../../gcc-3.4.4/gcc/libgcc2.c:43:
../../gcc-3.4.4/gcc/config/mips/linux.h:198: error: parse error before
"stack_t"
../../gcc-3.4.4/gcc/config/mips/linux.h:198: warning: no semicolon at
end of str
uct or union
../../gcc-3.4.4/gcc/config/mips/linux.h:201: error: parse error before
'}' token
../../gcc-3.4.4/gcc/config/mips/linux.h:201: warning: type defaults to
`int' in
declaration of `_sig_ucontext_t'
../../gcc-3.4.4/gcc/config/mips/linux.h:201: warning: data definition
has no typ
e or storage class
In file included from ./tm.h:13,
                 from ../../gcc-3.4.4/gcc/libgcc2.c:43:
../../gcc-3.4.4/gcc/config/mips/linux.h:198: error: parse error before
"stack_t"
../../gcc-3.4.4/gcc/config/mips/linux.h:198: warning: no semicolon at
end of str
uct or union
../../gcc-3.4.4/gcc/config/mips/linux.h:201: error: parse error before
'}' token
../../gcc-3.4.4/gcc/config/mips/linux.h:201: warning: type defaults to
`int' in
declaration of `_sig_ucontext_t'
../../gcc-3.4.4/gcc/config/mips/linux.h:201: warning: data definition
has no typ
e or storage class
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [libgcc/./_negdi2.o] Error 1
make[2]: Leaving directory
`/tmp/mipsel-unknown-linux-gnu-toolchain/build-gcc-bo
otstrap/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory
`/tmp/mipsel-unknown-linux-gnu-toolchain/build-gcc-bo
otstrap/gcc'
make: *** [all-gcc] Error 2

************************************************************************
*************************
I am able to build the minimal version of compiler for kernel build
with config options as below:

../gcc-3.4.4/configure --target=$TARGET --prefix=$PREFIX
--enable-language=c --without-headers --with-gnu-ld --with-gnu-as
--disable-shared --disable-threads

Has anybody faced this issue earlier?
Will be grateful if someone could comment on this issue.

Thanks and Regards,
Shyamal


Thanks and Regards,
Shyamal

**********************************************************************
Notice to recipient: This email is meant for only the intended recipient of the 
transmission, and may be a communication privileged by law, subject to export 
control restrictions or that otherwise contains proprietary information.  If 
you receive this email by mistake, please notify us immediately by replying to 
this message and then destroy it and do not review, disclose, copy or 
distribute it.  Thank you in advance for your cooperation.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>