delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/10/20/14:16:31

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20001020141005.0204f008@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 20 Oct 2000 14:12:52 -0400
To: cygwin AT sources DOT redhat DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Cygwin SEGVs
In-Reply-To: <200010201803.OAA19313@envy.delorie.com>
References: <20001020135305 DOT C14359 AT cygnus DOT com>
<20001017120354 DOT A9810 AT cygnus DOT com>
<20001017205249 DOT 7782 DOT qmail AT lizard DOT curl DOT com>
<20001020053504 DOT 5350 DOT qmail AT lizard DOT curl DOT com>
<20001020135305 DOT C14359 AT cygnus DOT com>
Mime-Version: 1.0

At 02:03 PM 10/20/2000, DJ Delorie wrote:

> > There is a problem.  Someone changed the top level configure a while ago
> > and broke things.
>
>That would be me, so I guess I better explain ;-)
>
>GCC has a "-B" flag that *used* to be used just to find things like
>cc1, cpp, as, and ld.  However, the GCC team has been using that
>option for many other things.  One of those things is to find crt0.o
>(the libraries have their own options).  There is *no* other way to
>find crt0.o!  So, this switch is kinda mandatory if you want to link
>your programs with the right crt0.o.
>
>Unfortunately, gcc warns you if the -B option isn't used to find cc1,
>cpp, as, or ld.  The warning totally ignores other valid uses of -B,
>so the warning was removed from the gcc sources (by me).  If old
>versions didn't exist, we'd be all set.
>
>As for workarounds for old gccs, there are two:
>
>1. Binary-edit your gcc.exe to remove that warning.  Not for the feint
>    of heart.
>
>2. Remove that option in configure, and hope that the *installed*
>    crt0.o is compatible with the *built* crt0.o (or copy it).
>
>You could also go through all the Makefiles and add that -B option to
>the specific link lines, but that's a tricky thing to get right.

Hi DJ,

So what version of gcc is this NOT a problem for?  Is the current version
available for download affected?  It would be great if the answer to this
problem was simply, upgrade gcc to the latest!;-)





Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019