This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: cross compiling problem
- To: "Todd Vierling" <tv at pobox dot com>
- Subject: Re: cross compiling problem
- From: "Paul Forgey" <paulf at aphrodite dot com>
- Date: Wed, 22 Jul 1998 06:56:36 -0700
- Cc: <egcs-bugs at cygnus dot com>
well, this seems only partly fixed for 1.1. Using 19980715, it doesn't
choke on libgcc1.a anymore, but building the libgcc2.a provokes a crapload
of 'illegal operand' and 'unknown opcode' messages -- but it seems to be
using the correct cross compiler/ar - perhaps the cross compiler isn't
properly calling the correct as?
By the way, for either 1.0.3a or 1.1, I figured out the libio/libstdc++
problems I was having. My linux target isn't glibc2 - so I just had to
specify the correct i586-linuxlibc1 target!
-----Original Message-----
From: Todd Vierling <tv@pobox.com>
To: Paul Forgey <paulf@aphrodite.com>
Cc: egcs-bugs@cygnus.com <egcs-bugs@cygnus.com>
Date: Tuesday, July 21, 1998 12:35 PM
Subject: Re: cross compiling problem
>: In ./objdir/i586-linux/gcc, I get:
>: "You must find a way to build libgcc1.a"
>
>I believe this is fixed in the upcoming egcs 1.1 sources. I sent in a note
>that on almost all i386 systems, libgcc1.a is unnecessary (it's all inlined
>instructions).
>
>For now, you can `touch libgcc1.a' (make an empty file) and it should work.
>
>--
>-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)
>