This is the mail archive of the
mailing list for the Cygwin project.
Re: What's wrong? gcc brain-damaged on cygwin?
- From: "Dockeen" <dockeen at mchsi dot com>
- To: <cygwin at cygwin dot com>
- Date: Sun, 22 Dec 2002 09:59:08 -0600
- Subject: Re: What's wrong? gcc brain-damaged on cygwin?
"Could it be that when compiling and installing gcc with
--enable-languages=c++ only gcc doesn't install some
Why in the world are you creating your own gcc? I used to do it
just because I wanted to use the gcc-3.1 code, but it is darn
tricky and completely unneccessary now, as gcc comes pre-built
in the devel directory. If there is something unique you want
to do with a version of gcc, make a parallel build, don't build
over Cygwin's gcc.
When I was creating my own stuff, I was creating it as an additional
compiler to the Cygwin compiler. I created it in a directory I called
mygcc. And I believe, if memory served, when I compiled I had to
do something like the following (I had aliased my new compiler to
newg++ hello.cpp -L\mygcc\lib
to make sure that the libstdc++ stuff got found.
But again, I would not do a build of gcc now, certainly not one that
replaces the Cygwin binaries.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html