delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/09/14/08:58:03

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,TW_BD
X-Spam-Check-By: sourceware.org
Message-ID: <4C8F7107.60204@cwilson.fastmail.fm>
Date: Tue, 14 Sep 2010 08:56:39 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1
References: <announce DOT 4C8EDA61 DOT 8030506 AT users DOT sourceforge DOT net> <AANLkTikW7P9+0Yxxi77vELMK=H-3-wceJdfobBJQB5Y0 AT mail DOT gmail DOT com> <4C8F1CF2 DOT 8000703 AT users DOT sourceforge DOT net> <4C8F2451 DOT 9020906 AT cwilson DOT fastmail DOT fm> <4C8F249D DOT 9050603 AT users DOT sourceforge DOT net> <20100914080327 DOT GD16534 AT calimero DOT vinschen DOT de> <4C8F4B29 DOT 8080209 AT users DOT sourceforge DOT net> <20100914111836 DOT GE15121 AT calimero DOT vinschen DOT de>
In-Reply-To: <20100914111836.GE15121@calimero.vinschen.de>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 9/14/2010 7:18 AM, Corinna Vinschen wrote:
> On Sep 14 18:15, JonY wrote:
>> What do you suggest the fix should be?
> 
> I really don't know, but it's certainly not a fix in Cygwin.  The fact
> that /usr/bin is a mount point to /bin is nothing which wouldn't be 
> allowed under Linux as well.  There's a default mechanism in gcc which
> evaluates the paths to the tools, headers and libdb dirs by massaging
> the $prefix and $exec_prefix values in some way.  I assume you can
> work around this issue by using slightly different values, but I'm
> not fluent enough with the path evaluationin gcc to suggest the
> correct solution, for a given value of "correct".

Actually, I don't think this "problem" is all that critical.  I think
that in order to trigger it, you have to do some fairly unusual things:
set your $PATH so that /bin precedes /usr/bin (which, in most cases, has
zero effect...so why would you do that?), or deliberately invoke the
compiler by one of its full PATH specifications (that is not the "usual"
/usr/bin/ one).

I think I'd just put a note in the README, the "Port Notes" section,
like this:

=====
If you invoke the compiler or other tools using a path like this:
	/bin/x86_64-w64-mingw32-gcc ...
rather than these
	/usr/bin/x86_64-w64-mingw32-gcc ...
	x86_64-w64-mingw32-gcc ...
you may see errors.  If you must invoke the compiler using the /bin
formulation, you can avoid these errors by creating a temporary mount
point (or add the following to your ~/.bashrc):
	mount -o bind /usr/x86_64-w32-mingw32 /x86_64-w32-mingw32
=====

This can certainly wait until the next normal package update. At least,
that's my opinion...

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


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