This is the mail archive of the gcc-help@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: Updating powerpc-crosscompile environment from gcc-2.95.3

From: Kai Ruottu <karuottu at mbnet dot fi>
To: corey taylor <corey dot taylor at gmail dot com>
Cc: Frank Beesley <frank dot beesley at aeroflex dot com>, gcc-help at gcc dot gnu dot org
Date: Thu, 10 Nov 2005 00:31:10 +0200
Subject: Re: Updating powerpc-crosscompile environment from gcc-2.95.3
References: <43725835.4070503@aeroflex.com> <43726A38.4060506@mbnet.fi> <2e393d080511091333k5ea4eaefi668237a1d1a8013d@mail.gmail.com>
Reply-to: karuottu at mbnet dot fi

corey taylor wrote:

Not entirely true.  You just typically interact with the wrapper
program, but compiling and lnking are distinct processes in msvc..


Oops, my point was to tell that those Windoze compilers I have met,
always have had both binutils and all the standard libraries for
both C and C++. But GCC can come totally alone, without any binutils
and libraries.  A GCC-builder shouldn't expect a "complete compiler"
coming from the 'gcc' subdirectory after it is built !

References:
- Re: Updating powerpc-crosscompile environment from gcc-2.95.3
  - From: Frank Beesley
- Re: Updating powerpc-crosscompile environment from gcc-2.95.3
  - From: Kai Ruottu
- Re: Updating powerpc-crosscompile environment from gcc-2.95.3
  - From: corey taylor

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