FW: Cygwin / GCC

[Keen Wayne A Contr AFRL/MNGG <keenwa at eglin dot af dot mil>]

-----Original Message-----
From: Keen Wayne A Contr AFRL/MNGG 
Sent: Thursday, February 28, 2002 12:51 PM
To: 'Kayvan A. Sylvan'
Cc: 'gcc-help@gcc.gnu.org'
Subject: RE: Cygwin / GCC


Thanks.
I have to be careful when I ask about what portions of Cygwin people have
installed.
If you have followed the Cygwin pages, you know that a suprising number of
people
think they don't have to do anything special in setup to install everything.
That
is, of course, not true.  If you open the individual categories you will
find things
that are labeled "skip".  There have even been some packages in the last few
weeks
that after installing, you have to reinstall to get everything working.

I noticed there are a couple of important things you left out.  Number 1, do
you
install Cygwin with a DOS or a Unix option?  Next, what additions, if any,
have
you made to your environment variables, and where did you make them.  It is
this
last portion that I believe is most critical, and I have asked a number of
times
for people who have done it successfully to give this environment / path
data,
and everyone has skipped over that...

One other question is this.  Do you use 3.0.3 daily on regular work?

I admit, somewhat in shame, that I have not used the -k option.  I will 
try your recipe, and look foward to finding the other Cygwin environment
information.

Thanks for your time.

Oh yeah, I take it for granted that
(a) You have no additional tools installed or modified above base Cygwin
tools
(b) You don't do anything after make -k install, i.e. move things around,
compile
something additional in.

Wayne Keen

-----Original Message-----
From: Kayvan A. Sylvan [mailto:kayvan@sylvan.com]
Sent: Thursday, February 28, 2002 10:33 AM
To: Keen Wayne A Contr AFRL/MNGG; Dockeen
Cc: 'gcc-help@gcc.gnu.org'
Subject: Re: Cygwin / GCC


On Thu, Feb 28, 2002 at 09:18:43AM -0600, Keen Wayne A Contr AFRL/MNGG
wrote:
> Out of curiousity, I'm wondering if you have ever built gcc anywhere other
> than cygwin. 
> It should be as simple as the above and, in my experience, it usually is. 
> In theory, cygwin is supposed to make things as easy to build on Windows
as
> on UNIX. 

With the latest Cygwin (1.3.9) and all the related packages (basically
doing a full install from the internet using the Cygwin setup.exe),
it is almost trivial to build a working GCC.

My Windows machine now is Windows XP but I have also build GCC and lots
of other Unix-centric software using Cygwin on NT and Win9x (I am right now
running the UDE X-window manager, compiled from source, for example).

Currently, I have gcc-2.95, gcc-3.0.3 and the latest CVS version of GCC
installed. The only "gotcha" is that I sometimes need to give the "-L" flag
to
gcc when linking (to ensure that the proper stdc++ and other libraries
are linked in).

I usually do something like:

./configure --prefix=/some/location
make LANGUAGES=c bootstrap install
make -k CC=/some/location/bin/gcc
make -k install

The "make -k" tells make to continue on even though a couple of targets
fail (I seem to recall problems with fastjar).

Best regards,

			---Kayvan

[[ Available for consulting. http://www.sylvan.com/~kayvan/Resume.html ]]
-- 
Kayvan A. Sylvan          | Proud husband of       | Father to my kids:
Sylvan Associates, Inc.   | Laura Isabella Sylvan  | Katherine Yelena
(8/8/89)
http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)