Cross compiling

Cross compiling

[Paul A. Kerr]

Hi, my name is Paul.

I have been trying to find information on how to "cross
compiling".
What I am actually trying to do is compile linux on an I686
for a Dec alpha server.

Is this possible?
If so where can I find the information?

Best regards
Paul A. Kerr
Phone: +27 (0)83 326 5209
Fax: 0866401539
E-mail stardust@starmail.co.za
_____________________________________________________________________
For super low premiums ,click here http://www.dialdirect.co.za/quote

Re: Cross compiling

[Andrew Walrond]

On Sunday 05 Sep 2004 12:25, Paul A. Kerr wrote:
> Hi, my name is Paul.
>
> I have been trying to find information on how to "cross
> compiling".
> What I am actually trying to do is compile linux on an I686
> for a Dec alpha server.
>
> Is this possible?
> If so where can I find the information?
>

http://kegel.com/crosstool/

Andrew Walrond

re: cross compiling

[Daniel Kegel]

vivek sukumaran <vike_justdoit@yahoo.co.in> wrote:
> Are there any ready to use gcc rpms for,
>  host:x-86,redhat9.0
>  target:alpha

The right mailing list to ask is the one at
    http://sources.redhat.com/ml/crossgcc/
When you do post there, be sure to mention what OS
the target will be running.

If the target is alpha-linux, you might want to build
your own using http://kegel.com/crosstool
http://kegel.com/crosstool/crosstool-0.28-rc37/buildlogs/0.28/
shows that crosstool-0.28-rc37 builds at least semi-working
alpha-linux toolchains.
- Dan

cross compiling

[vivek sukumaran]

Are there any ready to use gcc rpms for,
host:x-86,redhat9.0
target:alpha

thanking you 
vivek


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

Re: Cross compiling

[Alexandre Oliva]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

On Mar  9, 2000, POUGET Patrick <pouget@francenet.fr> wrote:

> I have currently 2.8.1 version of the gcc compiler. The archive seems to 
> be able to recompile on another plateform, but I would like to know how 
> to compile on the i386 a software to be used on m68k or ppc.

You'd have to start by building a cross compiler.  Somewhere in the
GCC web site there's a link to a `Cross GCC FAQ'; you could start by
taking a look at it.

-- 
Alexandre Oliva     http://www.ic.unicamp.br/~oliva/     Enjoy Guaraná
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

Cross compiling

[POUGET Patrick]

I have currently 2.8.1 version of the gcc compiler. The archive seems to 
be able to recompile on another plateform, but I would like to know how 
to compile on the i386 a software to be used on m68k or ppc.

Thanks

Cross compiling

[Larbi El Hajjaoui]

Hi,

when I try to build cross compiler gcc on linux "host" for mips "target", I
get one error message in the last stage:
before to build gcc I already buld and install binutils 2.91.05 for mips
 
  _m16addsf3
xgcc: installation problem, cannot exec `mips-tfile': no such file or
directory
make[1]: *** [libgcc1-asm.a] Error 1
make[1]: Leaving directory `/home/larbi/gcc-2.95.1/gcc'
make: *** [all-gcc] Error 2


Thank's for help

Cross compiling

[Larbi El Hajjaoui]

Hi,

when I try to build cross compiler gcc on linux "host" for mips "target", I
get one error message in the last stage:
before to build gcc I already buld and install binutils 2.91.05 for mips
 
  _m16addsf3
xgcc: installation problem, cannot exec `mips-tfile': no such file or
directory
make[1]: *** [libgcc1-asm.a] Error 1
make[1]: Leaving directory `/home/larbi/gcc-2.95.1/gcc'
make: *** [all-gcc] Error 2


Thank's for help

Re: Cross Compiling

[Daniel Jacobowitz]

On Mon, Aug 16, 1999 at 04:16:38PM -0600, Jeffrey A Law wrote:
>   In message < 19990816180939.A588@them.org >you write:
>   > Is there any way to configure which will not require the libraries? 
>   > For instance, if you have no library for the target system?
> No.  The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
> require system libraries.

Hm, but is it possible to build a target C compiler without a target
libiberty (obviously you'd need a host libiberty but that isn't a
problem)?

>   > Will libgcc build with just the headers for the target?
> Yes.
> 
> 
> jeff
> 
> 
> 


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

Re: Cross Compiling

[Daniel Jacobowitz]

On Mon, Aug 16, 1999 at 02:35:44PM -0600, Jeffrey A Law wrote:
>   In message < Pine.LNX.4.10.9908161402380.19574-100000@m.wolfram.com >you write:
>   > I'm trying to build a cross-compiler from a Red Hat Linux system to a
>   > Cygwin system (this is actually the first of several cross-compilers I'm
>   > trying to build, so prebuilt packages won't help).  Anyway, here is the
>   > process I'm going through
> You have to provide header files and libraries for your target system.
> Please read the installation instructions.
> 
> jeff

Is there any way to configure which will not require the libraries? 
For instance, if you have no library for the target system?

Will libgcc build with just the headers for the target?

This has become a FAQ, and the crossgcc document is badly in need of
updates (which I would volunteer if I knew the answers).

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

Cross Compiling

[Jonathan Bartlett]

I'm trying to build a cross-compiler from a Red Hat Linux system to a
Cygwin system (this is actually the first of several cross-compilers I'm
trying to build, so prebuilt packages won't help).  Anyway, here is the
process I'm going through

mkdir build_binutils
cd build_binutils
../binutils-2.9.1/configure --host=i686-pc-linux-gnu \
	--target=i586-pc-cygwin32 \
	--prefix=/home/johnnyb/cross
make
make install

mkdir build_gcc
cd build_gcc
../gcc-2.95/configure --host=i686-pc-linux-gnu --target=i586-pc-cygwin32 \
	--prefix=/home/johnnyb/cross --without-headers

With this configuration issuing make gives me this error:

  /home/johnnyb/build_gcc/gcc/xgcc -B/home/johnnyb/build_gcc/gcc/
-B/usr/local/i586-pc-cygwin32/bin/ -I/usr/local/i586-pc-cygwin32/include
-O2 -I../../gcc-2.95/gcc/../winsup/include -DCROSS_COMPILE -DIN_GCC     -g
-O2 -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I.
-I../../gcc-2.95/gcc -I../../gcc-2.95/gcc/config
-I../../gcc-2.95/gcc/../include -c -DL${name} \
       ../../gcc-2.95/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  i586-pc-cygwin32-ar rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
../../gcc-2.95/gcc/libgcc2.c:41: stdlib.h: No such file or directory
../../gcc-2.95/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[1]: *** [libgcc2.a] Error 1
make[1]: Leaving directory `/home/johnnyb/build_gcc/gcc'
make: *** [all-gcc] Error 2


However, if I specify that I'm going to use newlib, with --with-newlib, I
get:
_lshrdi3
_ashldi3
_ashrdi3
_ffsdi2
_udiv_w_sdiv
_udivmoddi4
_cmpdi2
_ucmpdi2
_floatdidf
_floatdisf
_fixunsdfsi
In file included from include/syslimits.h:7,
                 from include/limits.h:11,
                 from ../../gcc-2.95/gcc/libgcc2.c:1105:
/home/johnnyb/build_gcc/gcc/include/limits.h:117: limits.h: No such file
or directory
make[1]: *** [libgcc2.a] Error 1
make[1]: Leaving directory `/home/johnnyb/build_gcc/gcc'
make: *** [all-gcc] Error 2

I think this is all caused because I don't have newlib installed for that
platform.  However, I can't install newlib for that platform until I have
GCC built.  Any ideas?  Am I just doing it wrong?

Jonathan Bartlett

Re: Cross Compiling

[Jeffrey A Law]

  In message < Pine.LNX.4.10.9908161402380.19574-100000@m.wolfram.com >you write:
  > I'm trying to build a cross-compiler from a Red Hat Linux system to a
  > Cygwin system (this is actually the first of several cross-compilers I'm
  > trying to build, so prebuilt packages won't help).  Anyway, here is the
  > process I'm going through
You have to provide header files and libraries for your target system.
Please read the installation instructions.

jeff

Re: Cross Compiling

[Jeffrey A Law]

  In message < 19990816180939.A588@them.org >you write:
  > Is there any way to configure which will not require the libraries? 
  > For instance, if you have no library for the target system?
No.  The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
require system libraries.

  > Will libgcc build with just the headers for the target?
Yes.


jeff

Re: Cross Compiling

[Mumit Khan]

Daniel Jacobowitz <drow@false.org> writes:
> Is there any way to configure which will not require the libraries? 
> For instance, if you have no library for the target system?
>
> Will libgcc build with just the headers for the target?

Depends on the target. You may not be able to build libgcc.a when
cross-compiling for some targets; for others, having just the target
headers will suffice.

> This has become a FAQ, and the crossgcc document is badly in need of
> updates (which I would volunteer if I knew the answers).

You may want to check out the various howtos at
  http://www.xraylith.wisc.edu/~khan/software/gnu-win32/

The linux->cygwin cross assumes you have the Cygwin development tree
already installs. If you look at the linux->mingw howto, it shows how
and what to install for the target environment (headers/libs); the
latest one, cygwin->linux, gives more details.

Regards,
Mumit

Re: Cross Compiling

[Philip Blundell]

>Hm, but is it possible to build a target C compiler without a target
>libiberty (obviously you'd need a host libiberty but that isn't a
>problem)?

Yes.  You can, in extremis, bootstrap a system in a piecemeal fashion if you 
don't have any prebuilt libraries available.

p.

Re: Cross Compiling

[Philip Blundell]

>Hm, but is it possible to build a target C compiler without a target
>libiberty (obviously you'd need a host libiberty but that isn't a
>problem)?

Yes.  You can, in extremis, bootstrap a system in a piecemeal fashion if you 
don't have any prebuilt libraries available.

p.

Re: Cross Compiling

[Daniel Jacobowitz]

On Mon, Aug 16, 1999 at 04:16:38PM -0600, Jeffrey A Law wrote:
>   In message < 19990816180939.A588@them.org >you write:
>   > Is there any way to configure which will not require the libraries? 
>   > For instance, if you have no library for the target system?
> No.  The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
> require system libraries.

Hm, but is it possible to build a target C compiler without a target
libiberty (obviously you'd need a host libiberty but that isn't a
problem)?

>   > Will libgcc build with just the headers for the target?
> Yes.
> 
> 
> jeff
> 
> 
> 


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

Re: Cross Compiling

[Jeffrey A Law]

  In message < 19990816180939.A588@them.org >you write:
  > Is there any way to configure which will not require the libraries? 
  > For instance, if you have no library for the target system?
No.  The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
require system libraries.

  > Will libgcc build with just the headers for the target?
Yes.


jeff

Re: Cross Compiling

[Mumit Khan]

Daniel Jacobowitz <drow@false.org> writes:
> Is there any way to configure which will not require the libraries? 
> For instance, if you have no library for the target system?
>
> Will libgcc build with just the headers for the target?

Depends on the target. You may not be able to build libgcc.a when
cross-compiling for some targets; for others, having just the target
headers will suffice.

> This has become a FAQ, and the crossgcc document is badly in need of
> updates (which I would volunteer if I knew the answers).

You may want to check out the various howtos at
  http://www.xraylith.wisc.edu/~khan/software/gnu-win32/

The linux->cygwin cross assumes you have the Cygwin development tree
already installs. If you look at the linux->mingw howto, it shows how
and what to install for the target environment (headers/libs); the
latest one, cygwin->linux, gives more details.

Regards,
Mumit

Re: Cross Compiling

[Daniel Jacobowitz]

On Mon, Aug 16, 1999 at 02:35:44PM -0600, Jeffrey A Law wrote:
>   In message < Pine.LNX.4.10.9908161402380.19574-100000@m.wolfram.com >you write:
>   > I'm trying to build a cross-compiler from a Red Hat Linux system to a
>   > Cygwin system (this is actually the first of several cross-compilers I'm
>   > trying to build, so prebuilt packages won't help).  Anyway, here is the
>   > process I'm going through
> You have to provide header files and libraries for your target system.
> Please read the installation instructions.
> 
> jeff

Is there any way to configure which will not require the libraries? 
For instance, if you have no library for the target system?

Will libgcc build with just the headers for the target?

This has become a FAQ, and the crossgcc document is badly in need of
updates (which I would volunteer if I knew the answers).

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

Re: Cross Compiling

[Jeffrey A Law]

  In message < Pine.LNX.4.10.9908161402380.19574-100000@m.wolfram.com >you write:
  > I'm trying to build a cross-compiler from a Red Hat Linux system to a
  > Cygwin system (this is actually the first of several cross-compilers I'm
  > trying to build, so prebuilt packages won't help).  Anyway, here is the
  > process I'm going through
You have to provide header files and libraries for your target system.
Please read the installation instructions.

jeff

Cross Compiling

[Jonathan Bartlett]

I'm trying to build a cross-compiler from a Red Hat Linux system to a
Cygwin system (this is actually the first of several cross-compilers I'm
trying to build, so prebuilt packages won't help).  Anyway, here is the
process I'm going through

mkdir build_binutils
cd build_binutils
../binutils-2.9.1/configure --host=i686-pc-linux-gnu \
	--target=i586-pc-cygwin32 \
	--prefix=/home/johnnyb/cross
make
make install

mkdir build_gcc
cd build_gcc
../gcc-2.95/configure --host=i686-pc-linux-gnu --target=i586-pc-cygwin32 \
	--prefix=/home/johnnyb/cross --without-headers

With this configuration issuing make gives me this error:

  /home/johnnyb/build_gcc/gcc/xgcc -B/home/johnnyb/build_gcc/gcc/
-B/usr/local/i586-pc-cygwin32/bin/ -I/usr/local/i586-pc-cygwin32/include
-O2 -I../../gcc-2.95/gcc/../winsup/include -DCROSS_COMPILE -DIN_GCC     -g
-O2 -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I.
-I../../gcc-2.95/gcc -I../../gcc-2.95/gcc/config
-I../../gcc-2.95/gcc/../include -c -DL${name} \
       ../../gcc-2.95/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  i586-pc-cygwin32-ar rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
../../gcc-2.95/gcc/libgcc2.c:41: stdlib.h: No such file or directory
../../gcc-2.95/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[1]: *** [libgcc2.a] Error 1
make[1]: Leaving directory `/home/johnnyb/build_gcc/gcc'
make: *** [all-gcc] Error 2


However, if I specify that I'm going to use newlib, with --with-newlib, I
get:
_lshrdi3
_ashldi3
_ashrdi3
_ffsdi2
_udiv_w_sdiv
_udivmoddi4
_cmpdi2
_ucmpdi2
_floatdidf
_floatdisf
_fixunsdfsi
In file included from include/syslimits.h:7,
                 from include/limits.h:11,
                 from ../../gcc-2.95/gcc/libgcc2.c:1105:
/home/johnnyb/build_gcc/gcc/include/limits.h:117: limits.h: No such file
or directory
make[1]: *** [libgcc2.a] Error 1
make[1]: Leaving directory `/home/johnnyb/build_gcc/gcc'
make: *** [all-gcc] Error 2

I think this is all caused because I don't have newlib installed for that
platform.  However, I can't install newlib for that platform until I have
GCC built.  Any ideas?  Am I just doing it wrong?

Jonathan Bartlett

Re: Cross Compiling

[H.J. Lu]

> I don't know how easily this works with glibc though, as I have never tried
> that.  Most people use newlib for cross compilers to embedded targets.
> 

It is possible to cross-compile glibc. I have done that. But I never
did a one-pass cross-compile to build binutils, glibc and egcs. I
am afraid cross-compiling glibc may require a different approach
which may not be compatible with cross-compiling binutils and egcs.

-- 
H.J. Lu (hjl@gnu.org)

RE: Cross Compiling

[Jerry Alexandratos]

In Reply to Your Message of Tue, 21 Apr 1998 13: 14:41 PDT
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4546.893193876.1@hawk.pearson.udel.edu>
Date: Tue, 21 Apr 1998 17:24:37 -0400
From: Jerry Alexandratos <alexandr@hawk.pearson.udel.edu>

: Building a cross compiler is not as easy as it should be yet.  This is
: something that we are hoping to have fixed for the egcs 1.1 release.

Let me guess...Don't ask we don't know exactly when it'll be out.  8)

: You should be able to put everything in subdirs and do a one-pass build.
: However, this probably requires working around various bugs.
: 
: I don't know how easily this works with glibc though, as I have never tried
: that.  Most people use newlib for cross compilers to embedded targets.

I'd love to use newlib.  However, I'm FreeBSD and newlib doesn't seem to
support that OS.  8(

       --Jerry

8) Jerry Alexandratos              % - %  "Nothing inhabits my    (8 
8) alexandr@louie.udel.edu         % - %   thoughts, and oblivion (8
8) alexandr@hawk.pearson.udel.edu  % - %   drives my desires."    (8

Re: Cross Compiling

[Jim Wilson]

Building a cross compiler is not as easy as it should be yet.  This is
something that we are hoping to have fixed for the egcs 1.1 release.

	How do I setup to compile?  Should I extract and build each step
	separately (binutils, egcs, glibc) or do I make a single directory
	structure?  I was under the impression that I could do a one-pass build
	by putting all of the appropriate subdirs from binutils and glibc into
	the egcs directory and then doing a "make cross."  Am I correct?

You should be able to put everything in subdirs and do a one-pass build.
However, this probably requires working around various bugs.

I don't know how easily this works with glibc though, as I have never tried
that.  Most people use newlib for cross compilers to embedded targets.

Jim

Cross Compiling

[Jerry Alexandratos]

Hi, I'm hoping that I can get some clarification here.  I've read the
FAQ on using egcs as a cross-compiler and I'm still in the dark.

How do I setup to compile?  Should I extract and build each step
separately (binutils, egcs, glibc) or do I make a single directory
structure?  I was under the impression that I could do a one-pass build
by putting all of the appropriate subdirs from binutils and glibc into
the egcs directory and then doing a "make cross."  Am I correct?

Is there anything else I should keep an eye out for?

Thanks in advance.

        --Jerry

8) Jerry Alexandratos              % - %  "Nothing inhabits my    (8 
8) alexandr@louie.udel.edu         % - %   thoughts, and oblivion (8
8) alexandr@hawk.pearson.udel.edu  % - %   drives my desires."    (8