From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin mount option -s is not supported
Date: Fri, 27 Nov 2020 16:15:41 -0700 [thread overview]
Message-ID: <db719f81-1ca6-f047-492b-3b5d610934ad@SystematicSw.ab.ca> (raw)
In-Reply-To: <ff4142aff39a4b139aa0759aff0626fb@BELBRU-EXMP101.eeas.europa.eu>
On 2020-11-26 04:12, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> -----Original Message-----
>> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Brian Inglis
>> Sent: 25 November 2020 21:59
>>
>> On 2020-11-25 11:26, Vlado via Cygwin wrote:
>>> On 25.11.2020 15:18, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>>
>> Mount -s was removed in 2008:
>> https://sourceware.org/git/?p=newlib-
>> cygwin.git;a=commitdiff;h=5f853b3fc5277da8cb5ba3ac7406447fe82e65de
>> three months after it was set to be ignored.
>
> That explains the mystery. Thanks!
>
>>>> if [ -n "`uname -s |grep -i cygwin_`" ]; then
>>>> # If we are on an new version of Cygnus we need to turn <letter>:/
>>>> in
>>>> # the path to/cygdrive/<letter>/
>>
>> Use of 'Cygnus' refers to 20+ years ago when Cygwin was a product.
>
> So, it might have been working quite "recently" then :)
>
>>> Hard to say why Oracle's script is written this way. Standard Cygwin
>>> tool for file names conversion is cygpath. Instead of using sed, one
>>> can write WL_HOME_CYGWIN=`cygpath -u $WL_HOME`
>>> - simpler and the result will be more consistent. Example
>>>
>>> $ WL_HOME='C:\some\dir\subdir' # Windows path $ echo
>>> "$WL_HOME" | sed "s#\([a-zA-Z]\):#/cygdrive/c/\1#g"
>>> /cygdrive/c/C\some\dir\subdir # mixed forward and back
>>> slashes $ cygpath -u "$WL_HOME"
>>> /cygdrive/c/some/dir/subdir # pretty Cygwin path
>>
>> Especially note the cygpath -U -> /proc/cygdrive/, -a -> /..., and -p path
>> conversion options should be used as appropriate: try all three!
>
> Cygpath then is the correct approach to resolve this issue. I had no doubt about that. Anyway, this is not the only problem. They have messed the CLASSPATH as well and it needs to be updated to the correct libraries.
If you have an Oracle support contract, please submit a TAR, and attach any
patches you make, to upstream support, to avoid having to keep making changes
every update.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-11-27 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:18 KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-25 18:26 ` Vlado
2020-11-25 20:58 ` Brian Inglis
2020-11-26 11:12 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-27 23:15 ` Brian Inglis [this message]
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=db719f81-1ca6-f047-492b-3b5d610934ad@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).