Kai Ruottu wrote:
GCC configure. But there are long-standing bugs in the GCC sources and
workarounds/fixes are required.
Since you seem to have an understanding of the problems here, perhaps
you could file some bugzilla bug reports to document them.
then not... As told the "eabi" is not and one
On Fri, 2005-04-29 at 17:29, Amir Fuhrmann wrote:
> 1. If I am ONLY interested in the compiler, and do NOT want to build
> libraries, what would be the process ??
"make all-gcc" will build just the compiler without the libraries.
> 2. I looked at newlib, but wasn't sure of the process of includin
E. Weddington wrote:
The suggestion to look at Dan Kegel's crosstool is a good one,
>> but crosstool only handles cross compilers to linux, and hence isn't relevant here.
There have been patches to it for building on Cygwin,
plus the occasional success story on Cygwin, IIRC.
(Perhaps Dan can comm
Amir Fuhrmann kirjoitti:
1. If I am ONLY interested in the compiler, and do NOT want to build
libraries, what would be the process ??
Be happy with what you already have?
Ok
- 'make all-gcc' builds ONLY GCC
- 'make install-gcc' installs ONLY GCC
The "ONLY GCC" of course means the stuff
James E Wilson kirjoitti:
Amir Fuhrmann wrote:
checking whether byte ordering is bigendian... cross-compiling...
unknown
checking to probe for byte ordering...
/usr/local/powerpc-eabi/bin/ld: warning: cannot find entry symbol
_start; defaulting to 01800074
Looking at libiberty configure, I see i
E. Weddington kirjoitti:
I don't know if the specific combination will work, but one could
always try. At least it's sometimes a better starting point for
building a lot of cross-toolchains.
If building more than 1000 cross-GCCs is already "a lot of", then the
experience got from that says it
is
move over to the gcc tree ??
Again, thanks for your help
Amir
> -Original Message-
> From: James E Wilson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 28, 2005 5:50 PM
> To: Amir Fuhrmann
> Cc: gcc@gcc.gnu.org
> Subject: Re: FW: GCC Cross Compiler for cygwin
>
Amir Fuhrmann wrote:
checking whether byte ordering is bigendian... cross-compiling...
unknown
checking to probe for byte ordering... /usr/local/powerpc-eabi/bin/ld: warning:
cannot find entry symbol _start; defaulting to 01800074
Looking at libiberty configure, I see it first tries to get the
by
cc/gcc-3.4.3/libiberty/configure: line 3289: exit: please:
numeric argument required
make: *** [configure-target-libiberty] Error 1
-Original Message-
From: James E Wilson [mailto:[EMAIL PROTECTED]
Sent: Wed 4/27/2005 7:18 PM
To: Amir Fuhrmann
Cc: gcc@gcc.gnu.org
Subject:
James E Wilson wrote:
Amir Fuhrmann wrote:
../gcc-3.4.3/configure --exec-prefix=/usr/local --program-prefix=ppc-
--with-stabs -with-cpu=603 --target=powerpc-eabi --with-gnu-as=ppc-as
--with-gnu-ld=ppc-ld --enable-languages=c,c++
The suggestion to look at Dan Kegel's crosstool is a good one, but
Amir Fuhrmann wrote:
../gcc-3.4.3/configure --exec-prefix=/usr/local --program-prefix=ppc-
--with-stabs -with-cpu=603 --target=powerpc-eabi --with-gnu-as=ppc-as
--with-gnu-ld=ppc-ld --enable-languages=c,c++
Try adding --with-newlib. You either have to use a combined tree so
that newlib will be a
Amir Fuhrmann wrote:
Does anyone have a working recipe to build gcc as a cross compiler for
powerpc, to execute under cygwin
I've been able to compile binutils, and build the c/c++ compiler, but am
failing in:
configure: error: No support for this host/target combination.
make: *** [configure-targe
Does anyone have a working recipe to build gcc as a cross compiler for
powerpc, to execute under cygwin
I've been able to compile binutils, and build the c/c++ compiler, but am
failing in:
configure: error: No support for this host/target combination.
make: *** [configure-target-libstdc++-v3] Er
13 matches
Mail list logo
