public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Geoffrey Noer <noer@cygnus.com>
To: "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk>
Cc: Mumit Khan <khan@xraylith.wisc.EDU>,
	cygwin <cygwin@sourceware.cygnus.com>,
	Libtool List <libtool@gnu.org>
Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?
Date: Sun, 28 Feb 1999 23:02:00 -0000	[thread overview]
Message-ID: <19990225230358.B1388@cygnus.com> (raw)
Message-ID: <19990228230200.VNXdeOc7XB4cHoabwUYrjndJrLRkqp1uVTvW7I1-tSc@z> (raw)
In-Reply-To: <36D2DCFF.54E5B41F@oranda.demon.co.uk>

On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
[...]
> Not a problem as such, just a change.  The current libtool converts to
> UNC paths which I understand are no longer supported in winsup
> snapshots, so I need to rejig the code a bit more.

This shouldn't be the case.  //<drive-letter>/ support (which
conflicts with UNC support for machine names of one letter) will be
going away but we definitely intend to continue to support UNC path
names.

If UNC support is broken in current snapshots, please let me know...

-- 
Geoffrey Noer		Email: noer@cygnus.com
Cygnus Solutions

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-02-28 23:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-23  4:11 Suhaib M. Siddiqi
1999-02-23  4:56 ` Gary V. Vaughan
     [not found]   ` < 36D2A59D.603BF54E@oranda.demon.co.uk >
1999-02-23  8:39     ` Mumit Khan
1999-02-23  8:54       ` Gary V. Vaughan
     [not found]         ` < 36D2DCFF.54E5B41F@oranda.demon.co.uk >
1999-02-25 23:04           ` Geoffrey Noer [this message]
1999-02-28 23:02             ` Geoffrey Noer
1999-02-28 23:02         ` Gary V. Vaughan
     [not found]       ` < 199902231639.KAA04761@modi.xraylith.wisc.edu >
1999-02-23  9:13         ` DJ Delorie
     [not found]           ` < 199902231713.MAA11397@envy.delorie.com >
1999-02-23 14:16             ` Mumit Khan
1999-02-28 23:02               ` Mumit Khan
1999-02-28 23:02           ` DJ Delorie
1999-02-28 23:02       ` Mumit Khan
1999-02-28 23:02   ` Gary V. Vaughan
1999-02-28 23:02 ` Suhaib M. Siddiqi
  -- strict thread matches above, loose matches on Subject: below --
1999-02-26  2:32 Bernard Dautrevaux
1999-02-26  3:51 ` Gary V. Vaughan
1999-02-28 23:02   ` Gary V. Vaughan
1999-02-28 23:02 ` Bernard Dautrevaux
1999-02-23  5:01 Suhaib M. Siddiqi
1999-02-28 23:02 ` Suhaib M. Siddiqi
     [not found] <Bob>
     [not found] ` <Friesenhahn's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Mon,>
     [not found]         ` <22>
     [not found]           ` <Feb>
     [not found]             ` <1999>
     [not found]               ` <21:28:12>
     [not found]                 ` <-0600>
     [not found]                   ` <(CST)>
     [not found]                     ` <Pine.SO4.4.05.9902222125010.25431-100000@scooby.simple.dallas.tx.us>
     [not found]                       ` <d9btilixqo.fsf@han.cs.umn.edu>
1999-02-22 22:41                         ` Sebastien Barre
1999-02-23  3:06                           ` Gary V. Vaughan
1999-02-28 23:02                             ` Gary V. Vaughan
1999-02-28 23:02                           ` Sebastien Barre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990225230358.B1388@cygnus.com \
    --to=noer@cygnus.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=gvaughan@oranda.demon.co.uk \
    --cc=khan@xraylith.wisc.EDU \
    --cc=libtool@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).