building a cross compiler

building a cross compiler

[erwan ancel]

Hi,

I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
target.
my configure parameters are:
./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
--with-gnu-as --with-gnu-ld --disable-multilib

when typing make, the xgcc is built, but I got the error:
checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
-B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
-B/usr/cross-compile/i386-mingw32/lib/ -isystem
/usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
configure: error: installation or configuration problem: C compiler
cannot create executables.
make: *** [configure-target-libiberty] Erreur 1

Does anyone know what happens ?

		Erwan.

Re: building a cross compiler

[LLeweLLyn Reese]

erwan ancel <erwan.ancel@free.fr> writes:

> Hi,
> 
> I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> target.
> my configure parameters are:
> ./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
> --with-gnu-as --with-gnu-ld --disable-multilib
> 
> when typing make,

try:

$make cross

instead.

> the xgcc is built, but I got the error:
> checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
> -B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
> -B/usr/cross-compile/i386-mingw32/lib/ -isystem
> /usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
> make: *** [configure-target-libiberty] Erreur 1
> 
> Does anyone know what happens ?
> 
> 		Erwan.

Re: building a cross compiler

[erwan ancel]

I tried: same result ...


Le mer 30/04/2003 à 22:36, LLeweLLyn Reese a écrit :
> erwan ancel <erwan.ancel@free.fr> writes:
> 
> > Hi,
> > 
> > I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> > target.
> > my configure parameters are:
> > ./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
> > --with-gnu-as --with-gnu-ld --disable-multilib
> > 
> > when typing make,
> 
> try:
> 
> $make cross
> 
> instead.
> 
> > the xgcc is built, but I got the error:
> > checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
> > -B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
> > -B/usr/cross-compile/i386-mingw32/lib/ -isystem
> > /usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
> > configure: error: installation or configuration problem: C compiler
> > cannot create executables.
> > make: *** [configure-target-libiberty] Erreur 1
> > 
> > Does anyone know what happens ?
> > 
> > 		Erwan.
> 

Re: building a cross compiler

[npat]

On Wed, Apr 30, 2003 at 01:36:37PM -0700, LLeweLLyn Reese wrote:
> erwan ancel <erwan.ancel@free.fr> writes:
> 
> > Hi,
> > 
> > I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> > target.
> 
> try:
> 
> $make cross
> 
> instead.
> 

Is this true for other targets also? I'm pretty sure I have not seen
this in the documentation, and I have also managed to build an
ix86/linux hosted, sparc-linux targeting cross-compiler without saying
"make cross".

/npat

-- 
Developing skills that depend on a proprietary product makes you a
sharecropper on your own brain.
  -- Donald B. Marti Jr.

Re: building a cross compiler

[Pieter Thysebaert]

On 30 Apr 2003, erwan ancel wrote:

> Hi,
>
> I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> target.
> my configure parameters are:
> ./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
> --with-gnu-as --with-gnu-ld --disable-multilib
>
> when typing make, the xgcc is built, but I got the error:
> checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
> -B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
> -B/usr/cross-compile/i386-mingw32/lib/ -isystem
> /usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
> make: *** [configure-target-libiberty] Erreur 1

check the last lines of config.log, it will include the error as reported
by the compiler when attempting to compile a test program.


Have you built cross-binutils AND put them (or rather, the name
of the directory
containing them) in your PATH variable?

BTW you're configuring for mingw, not cygwin .

Pieter

Re: building a cross compiler

[erwan ancel]

Yes. You're right, I want to build it for MinGW :)
Any way, I managed to compile it: just by adding the MinGW libraries in
$PREFIX/i386-mingw32/library

Thanks.

	Erwan

Le jeu 01/05/2003 à 20:56, Pieter Thysebaert a écrit :
> On 30 Apr 2003, erwan ancel wrote:
> 
> > Hi,
> >
> > I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> > target.
> > my configure parameters are:
> > ./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
> > --with-gnu-as --with-gnu-ld --disable-multilib
> >
> > when typing make, the xgcc is built, but I got the error:
> > checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
> > -B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
> > -B/usr/cross-compile/i386-mingw32/lib/ -isystem
> > /usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
> > configure: error: installation or configuration problem: C compiler
> > cannot create executables.
> > make: *** [configure-target-libiberty] Erreur 1
> 
> check the last lines of config.log, it will include the error as reported
> by the compiler when attempting to compile a test program.
> 
> 
> Have you built cross-binutils AND put them (or rather, the name
> of the directory
> containing them) in your PATH variable?
> 
> BTW you're configuring for mingw, not cygwin .
> 
> Pieter
> 
> 

RE: building a cross compiler

[David Korn]

    Hi Al,

>make[2]: Entering directory
>`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
>arc-sun-solaris2/libiberty'
>
>make[2]: *** No targets specified and no makefile found.  Stop.
>make[2]: Leaving directory
>`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
>arc-sun-solaris2/libiberty'
>
>make[1]: *** [../libiberty/libiberty.a] Error 2
>make[1]: Leaving directory
>`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
>arc-sun-solaris2/libstdc++'
>
>make: *** [all-target-libstdc++] Error 2

  This looks very much like something failed badly during the configure
stage, since that's when the makefiles should have been created. Was there
anything unusual in the output from that ?

     DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: building a cross compiler

[Albert Niessner]

Nothing appears to be wrong in the configure output. It is long so I decided
not to post it. There are no errors or warnings though. I did modify the
configure line a little bit and now get a little further:

target=sparc-sun-solaris2
../gcc-2.95.2/configure --target=$target --prefix=$prefix -v
--with-headers=../Solaris-2.6/include --with-libraries=../Solaris-2.6/lib

and the compile fails with:

/Scratch/CrossCompiler/build-gcc-sparc/gcc/
-B/usr/local/CrossCompiler/sparc-sun-solaris2/bin/ -c -g -O2
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
../../../gcc-2.95.2/libio/iostream.cc -o pic/iostream.o
/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/gcc/xgcc
-B/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/gcc/
-B/usr/local/CrossCompiler/sparc-sun-solaris2/bin/ -c -g -O2
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
../../../gcc-2.95.2/libio/iostream.cc
../../../gcc-2.95.2/libio/iostream.cc:40: printf.h: No such file or directory
make[1]: *** [iostream.o] Error 1
make[1]: Leaving directory
`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sparc-sun-solaris2/libio'

make: *** [all-target-libio] Error 2

I found a reference to this error from February 2000. I am going to try and
track it down using those hints and advice.

Al Niessner

David Korn wrote:

>     Hi Al,
>
> >make[2]: Entering directory
> >`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
> >arc-sun-solaris2/libiberty'
> >
> >make[2]: *** No targets specified and no makefile found.  Stop.
> >make[2]: Leaving directory
> >`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
> >arc-sun-solaris2/libiberty'
> >
> >make[1]: *** [../libiberty/libiberty.a] Error 2
> >make[1]: Leaving directory
> >`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sp
> >arc-sun-solaris2/libstdc++'
> >
> >make: *** [all-target-libstdc++] Error 2
>
>   This looks very much like something failed badly during the configure
> stage, since that's when the makefiles should have been created. Was there
> anything unusual in the output from that ?
>
>      DaveK
> --
> The Boulder Pledge: "Under no circumstances will I ever purchase anything
> offered to me as the result of an unsolicited email message. Nor will I
> forward chain letters, petitions, mass mailings, or virus warnings to large
> numbers of others. This is my contribution to the survival of the online
> community."
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************

building a cross compiler

[Albert Niessner]

gcc version = 2.95.2
host = i686-pc-linux-gnu
target = sparc-sun-solaris2
configure line = ../gcc-2.95.2/configure --target=$target
--prefix=/usr/local -v --with-headers=../Solaris-2.6/include

I am attempting to build a cross compiler for the sparc platform and the
make is crashing when it gets to libiberty. I looked through the
configure.in and libiberty/configure.in looking for extra controls and
found none that helped. The specific error make is throwing is:

make[2]: Entering directory
`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sparc-sun-solaris2/libiberty'

make[2]: *** No targets specified and no makefile found.  Stop.
make[2]: Leaving directory
`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sparc-sun-solaris2/libiberty'

make[1]: *** [../libiberty/libiberty.a] Error 2
make[1]: Leaving directory
`/export/home/niessner/Scratch/CrossCompiler/build-gcc-sparc/sparc-sun-solaris2/libstdc++'

make: *** [all-target-libstdc++] Error 2


Just as a test I then did a make -k to proceed past the errors. It
completed and installed, but is not functional. It crashes during the ld
phase. Since the test program compiles and runs with a host compiler, it
should compile and link with the cross.

What is missing in the configure line which will allow the compiler to
build?


Al Niessner

Building a cross compiler.

[Mark A. Framness]

Hey

What is the deal with a cross compiler?  It seems to me that a x-compiler 
will allow one to build programs for differing target systems.
 
Anyone have experience building this for perhaps Linux - OS/2 - Win*?

Thanks

From:  Mark A. Framness
http://netnet.net/~farmer/
mframness@lakefield.net

 Go Pack Go!

Re: Building a cross compiler.

[Mumit Khan]

In article < 8Sd1uPikEGru-pn2-2W84zN2R5OIC@www.framnett.net >,
Mark A. Framness <mframness@NOSPAM.lakefield.net> wrote:
>Hey
>
>What is the deal with a cross compiler?  It seems to me that a x-compiler 
>will allow one to build programs for differing target systems.
> 
>Anyone have experience building this for perhaps Linux - OS/2 - Win*?
>

For general cross-gcc information, see http://www.objsw.com/CrossGCC/

Unfortunately, the information about win32 compilers there is a bit
outdated. For that, see my Linux->Windows and Windows->Linux cross
compiler howtos at http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ 

Regards,
Mumit

Re: Building a cross compiler.

[Mumit Khan]

In article < 8Sd1uPikEGru-pn2-2W84zN2R5OIC@www.framnett.net >,
Mark A. Framness <mframness@NOSPAM.lakefield.net> wrote:
>Hey
>
>What is the deal with a cross compiler?  It seems to me that a x-compiler 
>will allow one to build programs for differing target systems.
> 
>Anyone have experience building this for perhaps Linux - OS/2 - Win*?
>

For general cross-gcc information, see http://www.objsw.com/CrossGCC/

Unfortunately, the information about win32 compilers there is a bit
outdated. For that, see my Linux->Windows and Windows->Linux cross
compiler howtos at http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ 

Regards,
Mumit

Building a cross compiler.

[Mark A. Framness]

Hey

What is the deal with a cross compiler?  It seems to me that a x-compiler 
will allow one to build programs for differing target systems.
 
Anyone have experience building this for perhaps Linux - OS/2 - Win*?

Thanks

From:  Mark A. Framness
http://netnet.net/~farmer/
mframness@lakefield.net

 Go Pack Go!