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
Date:	Thu, 21 Mar 2002 13:43:28 +0000
Message-ID:	<7794-Thu21Mar2002134328+0000-starksb@ebi.ac.uk>
X-Mailer:	emacs 20.7.1 (via feedmail 9-beta-7 I);
	VM 7.00 under Emacs 20.7.1
From:	David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version:	1.0
To:	"Sankaran,
	Senthil K (Indsys)" <Senthil DOT Sankaran AT geind DOT GE DOT com>
Cc:	cygwin AT cygwin DOT com
Subject:	GCC- Error
In-Reply-To:	<05C613689F01D611AC820002A54177C0CBF1A7@GIAHYDMSX2.SGE.INDSYS.GE.COM>
References:	<05C613689F01D611AC820002A54177C0CBF1A7 AT GIAHYDMSX2 DOT SGE DOT INDSYS DOT GE DOT COM>

Sheesh.

If you would have checked the mailing list archives for even just the
previous 24 hours, you would have learned that this is a known problem
and is being worked on.

David

On Thursday 21 Mar 02, Sankaran, Senthil K (Indsys) writes:
> $ gcc hello.c -o hello.exe
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/ld:
> cann
> ot find -luser32
> collect2: ld returned 1 exit status


--
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 -