Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dockeen" <dockeen AT mchsi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: What's wrong? gcc brain-damaged on cygwin?
Date:	Sun, 22 Dec 2002 09:59:08 -0600
Message-ID:	<NCBBLKKJGBJOLDFMCKFPEECFCBAA.dockeen@mchsi.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

"Could it be that when compiling and installing gcc with 
--enable-languages=c++ only gcc doesn't install some 
essential libs?"

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++):

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.

Wayne Keen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -