This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: GCC linker problem since last cygwin update
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Jul 2006 10:35:04 -0400
- Subject: Re: GCC linker problem since last cygwin update
- References: <400BDC416E2A0042AA35DF3919BB8A51351AF7@mail.mtl.proksim.com>
- Reply-to: cygwin at cygwin dot com
Olivier Langlois wrote:
Hi Larry,
I would suggest you start by reading and following the problem
reporting
guidelines outlined here:
Problem reports: http://cygwin.com/problems.html
Ok, I will
In particular, you want to look closely at whether you're actually
using
Cygwin's tools. Your paths look suspect to me.
You are right. The compiler/linker that I'm using are not part of cygwin
but I think that I need cygwin since the compiler is based on gcc and my
OS is Windows. cygwin is somehow involved in my problem since
'/cygwin/c' is displayed in the error message but my cygwin knowledge is
big enough to fully understand the interaction between my compiler and
cygwin. All I know is that it was working fine few minutes before my
upgrade that included
cygwin DLL (1.5.20-1), coreutils (5.97-1) and binutils (20060709-1)
(My novice instinct makes me suspect these modules...)
and right after it was not working anymore.
I'd recommend looking at your paths then. You can also try running
from a Cygwin shell. I'd recommedn using POSIX paths as well. Beyond
that, I can't make any more detailed recommendations with the
information you've provided so far.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/