Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 20 Feb 2001 14:19:45 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: "'Cygwin Mailing List'" <cygwin AT cygwin DOT com>
Subject: Re: More problems building gcc
Message-ID: <20010220141945.B30769@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: 'Cygwin Mailing List' <cygwin AT cygwin DOT com>
References: <B7536E2DB26AD211A42500104BB49C72F60454 AT manbarapp1 DOT intgame DOT com> <3A92B7D5 DOT 38C65508 AT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3A92B7D5.38C65508@yahoo.com>; from earnie_boyd@yahoo.com on Tue, Feb 20, 2001 at 01:30:45PM -0500

On Tue, Feb 20, 2001 at 01:30:45PM -0500, Earnie Boyd wrote:
>"Blythe.Stephen" wrote:
>> 
>> Thanks to Earnie and Tim for your help.
>> 
>> OK, so I am now using the source from cygwin, GCC v2.95.2-7, and this makes
>> a native compiler OK.
>> I get problems when I try to build a m68k-coff cross-compiler from this
>> source.  Should I be able to do this, or should I build my xgcc from the
>> central GCC source?
>> 
>> I have no problems building binutils for m68k-coff, but when I come to build
>> the compiler, using "make all", I get the following.
>> 
>> gcc -c -DCROSS_COMPILE -DIN_GCC     -g -O2  -DHAVE_CONFIG_H    -I.
>> -I../../gcc-2
>> .95.2-7/gcc -I../../gcc-2.95.2-7/gcc/config
>> -I../../gcc-2.95.2-7/gcc/../include
>> ../../gcc-2.95.2-7/gcc/function.c
>> In file included from ../../gcc-2.95.2-7/gcc/function.c:48:
>> insn-flags.h:472: conflicting types for `gen_beq'
>> ../../gcc-2.95.2-7/gcc/rtl.h:1032: previous declaration of `gen_beq'
>> insn-flags.h:478: conflicting types for `gen_bge'
>> ../../gcc-2.95.2-7/gcc/rtl.h:1033: previous declaration of `gen_bge'
>> insn-flags.h:480: conflicting types for `gen_ble'
>> ../../gcc-2.95.2-7/gcc/rtl.h:1034: previous declaration of `gen_ble'
>> insn-flags.h:482: conflicting types for `gen_jump'
>> ../../gcc-2.95.2-7/gcc/rtl.h:1031: previous declaration of `gen_jump'
>> ../../gcc-2.95.2-7/gcc/function.c: In function `expand_function_end':
>> ../../gcc-2.95.2-7/gcc/function.c:6505: too many arguments to function
>> `gen_jump
>> '
>> make[1]: *** [function.o] Error 1
>> make[1]: Leaving directory `/usr/local/src/build-gcc/gcc'
>> make: *** [all-gcc] Error 2
>> 
>> As far as I can tell, the prototype of gen_beq() in
>> build-gcc/gcc/insn-flags.h has no parameters (void), while the version in
>> rtl.h has "rtx" as a parameter.
>> 
>> Sorry if I'm veering off-topic, but my initial question - whether the GCC
>> packaged with GNU can be used to build a cross-compiler - is still OK to be
>> asked here I think, and with the rest I'm just trying to give sufficient
>> information for anyone kind enough to help.
>> 
>
>I don't know.  Perhaps a better mail list for this question is
>crossgcc AT sources DOT redhat DOT com .

I'm not sure if they would appreciate hearing about a non-standard, patched
version of gcc.  That's what gcc 2.95.2-7 is.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple