[Fwd: Re: gcc-3.4 cross support for non C languages]

[Fwd: Re: gcc-3.4 cross support for non C languages]

[Jim Wilson]

[-- Attachment #1: Type: text/plain, Size: 97 bytes --]

Mistyped the mailing list address.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

[-- Attachment #2: Re: gcc-3.4 cross support for non C languages --]
[-- Type: message/rfc822, Size: 2988 bytes --]

From: Jim Wilson <wilson@specifixinc.com>
To: Stefan Traby <stefan@hello-penguin.com>
Cc: Marc Lehmann <pcg@goof.com>,  gcc-bugs@gcc.gun.org
Subject: Re: gcc-3.4 cross support for non C languages
Date: Sun, 16 May 2004 17:35:25 -0700
Message-ID: <40A808CD.90807@specifixinc.com>

Stefan Traby wrote:
> cross for the following environment:
> tgt=i686-pc-cygwin
> host=$(gcc -dumpmachine) (ahhh: i686-gnu-linux):

The best source of info I know of for cross compiler builds targetting 
linux is:
   http://kegel.com/crosstool/
This provides info and scripts that will build both gcc and glibc.  It 
is a little tricky as you can't completely build either without the other.

If you already have a linux target, and have access to its root file 
system, then a simpler way is to use the --with-sysroot= option to 
specify where the target linux libraries and header files can be found. 
  You just put a copy of the target linux root file system on your host, 
and specify the path to it as an option to the --with-sysroot= configure 
option.  You don't need the full root file system, you just need 
/usr/lib, /usr/include, /lib, and maybe a few other things.

> 1. libstdc++-V3 does not build - ok but there is no
>    option to disable it - which would be _reasonable_ for
>    cross builds.

You didn't say what problem you ran into.  We can't help if we don't 
know what went wrong.

The C++ compiler isn't really that useful without libstdc++.  Some 
important C++ functionality is implemented in libstdc++.

  (anyway, rm -rf ./libstdc++-v3 works)

renaming the directory works also.  E.g.
   mv libstdc++-v3 libstdc++-v3-do-not-build
Renaming it to anything will prevent it from being built.  (er, that is 
anything other than one of the other library names).

The library should build if you follow either of the options presented 
above, e.g. Dan Kegel's crosstool script, or using the --with-sysroot 
configure option.

> F77 builds fine but not the library. libU77 forgets
> that we are building cross and tries to exec a test
> excutable

Again, you didn't say what exactly the problem was.  You mentioned it 
tried to run an executable, but it isn't clear if that was wrong.  We 
need more details.

f77 is not very useful without the library.

As above, the library should build if you set up the cross build correctly.

> Well, java is a problem, it builds ok but:
> LANG=C ./gcj
> gcj: libgcj.spec: No such file or directory

As above.  Java is not very useful without the library.  The library 
should build if you set up the cross build correctly.  You didn't say 
why libjava didn't build.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com