This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Can't bootstrap gcc 3.4.0 20040205 on cygwin: xgcc: cygwin1.o: No such file or directory


On Tue, Feb 17, 2004 at 03:35:39PM +0100, Rainer Orth wrote:
>Christian Joensson writes:
>
>> On Fri, Feb 13, 2004 at 01:01:01PM +0100, Christian Joensson wrote:
>> 
>> 
>> > > > > stage1/xgcc.exe -Bstage1/ -B/usr/local/gcc-binutils/pentium4-cygwin/bin/   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition     -DHAVE_CONFIG_H  -o gcj.exe gcc.o jvspec.o prefix.o intl.o \
>> > > > >   version.o cygwin1.o ../libiberty/libiberty.a -lintl -liconv
>> > > > > xgcc: cygwin1.o: No such file or directory
>> 
>> 
>> 
>> > 
>> > Feb 04, 20:45 gcc/gcc ChangeLog Makefile.in config/mips/t-ir ... ro
>> > 		http://gcc.gnu.org/ml/gcc-cvs/2004-02/msg00204.html
>> 
>> This is causing the problem, the Makfile.in patch.
>
>Sorry for the breakage.  I think I understand what's going on, but don't
>have access to any Cygwin system, so I'll need some help to fix this.
>
>Here's my understanding of the problem:
>
>config/i386/t-cygwin defines
>
>EXTRA_GCC_OBJS = cygwin1.o
>
>Before my change to move the target makefile fragments after the langage
>fragments, this macro was defined early in gcc/Makefile, and thus was
>available in several dependencies on $(EXTRA_GCC_OBJS) in gcc/Makefile.in
>and some language Make-lang.in's (cp, f, and java).
>
>Once the target fragments have been moved down, this doesn't work any
>longer, since macros *in dependencies* must be defined before they can be
>used.
>
>Looking into gcc/Makefile.in, I see this:
>
># List of extra object files that should be compiled and linked with
># the gcc driver.
>EXTRA_GCC_OBJS =@host_extra_gcc_objs@
>
>host_extra_gcc_objs is defined in gcc/config.host, so by moving the
>definition there, everything should work as before.  Unfortunately, I'm
>uncertain if cygwin1.c is really a host file or a target file, and am
>completely unfamiliar with cross compilers in general.

cygwin1.o is a target file.  It's only intended for x86 targeted
systems, not for any compiler hosted on cygwin.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]