From: LRN <lrn1986@gmail.com>
To: cygwin@cygwin.com
Subject: Changes in process spawning break perl system() function
Date: Tue, 17 Mar 2015 04:52:00 -0000 [thread overview]
Message-ID: <5507768E.20108@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1258 bytes --]
How to reproduce:
1) create a shell script (say, /usr/bin/shellscript) containing this:
#!/bin/sh
echo ${0##*/}
2) create a symlink (say, /usr/bin/asymlink) that points to shellscript
3) create a perl script (say, /usr/bin/perlscript) containing this:
#! /usr/bin/perl -w
system '/usr/bin/asymlink';
4) run /usr/bin/perlscript
Expected results:
"asymlink" should be echoed by the shellscript when it is run by perlscript
Actual results:
"shellscript" is echoed instead
This affects 1.7.35.
I've tried various cygwin dll snapshots, everything is fine (symlink name is
echoed) with cygwin1-20150210.dll, cygwin1-20150211.dll breaks things first (a
full DOS path to shellscript is echoed), then from cygwin1-20150215.dll and
onward the target script name is echoed, as described above.
Symlink can be a Cygwin symlink or a native symlink, doesn't matter.
The use-case for this is autoconf wrapper (a shell script) that is being run by
autoreconf (a perl script) and uses the contents of $0 to find different
versions of autoconf, expecting $0 to be something like /usr/bin/autoconf, but
getting things like /usr/share/autotools/ac-wrapper.sh instead.
--
O< ascii ribbon - stop html email! - www.asciiribbon.org
[-- Attachment #1.2: 0x922360B0.asc --]
[-- Type: application/pgp-keys, Size: 1747 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2015-03-17 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 4:52 LRN [this message]
2015-03-17 10:50 ` Achim Gratz
2015-03-17 11:00 ` Corinna Vinschen
2015-03-17 12:05 ` LRN
2015-03-17 13:48 ` Corinna Vinschen
2015-03-17 12:09 ` Achim Gratz
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=5507768E.20108@gmail.com \
--to=lrn1986@gmail.com \
--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).