delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/08/17/11:48:09

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
Message-ID: <008701c24606$9f1cfb60$0111cf84@Zorglub>
From: "Eric Bechet" <eric DOT bechet AT polymtl DOT ca>
To: <cygwin AT cygwin DOT com>
Subject: trouble updating gcc
Date: Sat, 17 Aug 2002 11:56:16 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

Hello,

I did update the shipped gcc (2.95 or so) with a newer one (v. 3.2).
I did not erase the older version, but I put the new on in a separate
directory.
This works fine except that :
1- I had to change the path to get access to the new version (i think this
is normal :-)
2- ld (linker) (which is invoked by gcc automatically), still tries to
access to older library folder as there was no new version of those
libraries. The path unfortunately have no effect on this...

How can I get rid of that ?

and  is there a canonical way to update any package inside cygwin ?

Thanks for any help,

Eric



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


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