public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: mkshortcut (cygutils-1.4.14) free error
Date: Tue, 27 Oct 2015 09:30:00 -0000	[thread overview]
Message-ID: <loom.20151027T061000-194@post.gmane.org> (raw)
In-Reply-To: <1445904708.1171081.420968713.3D94007E@webmail.messagingengine.com>

Anthony Heading writes:
> I didn't hit any explicit configure issue myself,  rather a bunch of
> unrecognized case-invariant strcmp variants, which took about 10 seconds
> to fix but did make me wonder about the source code.    And then this
> below was the slightly trickier issue:
> 
> % src/mkshortcut/.libs/mkshortcut xyzzy
> mkshortcut: Saving "xyzzy.lnk" failed; does the target directory exist?
> 
> The packaged binary does not do this.

I really appreciate the leads and code you've provided.  Could we please
discuss only on the Cygwin mailing list?  That's the convention we have,
barring extraordinary circumstances :) .  It allows for public review.

Installing gettext-devel and popt-devel got rid of my configure issues.  I
updated lpr/Printer.cc and cygdrop/cygdrop.cc to use strcasecmp() instead of
stricmp() and strcmpi() respectively.  I did not (yet) look into the
compiler warnings that spew during the build of some of the cygutils
executables.

At that point I could reproduce your first mkshortcut issue.  Your patch
seems to fix that issue.  So far, so good.

The second issue with the non-absolute path is more problematic.  Without
your second patch, I do see the issue but only on the 2nd or later
invocation.  In other words, if the xyzzy.lnk file does not initially exist,
the command 'src/mkshortcut/.libs/mkshortcut xyzzy' works and does create
the link file.  Another invocation then shows the error.  Is it simply
mis-reporting that there's an existing link file?  I'm also assuming you're
in the /usr/src/cygutils-1.4.14-1.<arch>/build directory when you issue that
command.

..mark


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

  reply	other threads:[~2015-10-27  5:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18  2:30 Anthony Heading
2015-10-26 10:01 ` Anthony Heading
2015-10-26 10:08   ` Mark Geisert
2015-10-26 10:36     ` Corinna Vinschen
2015-10-27  5:29     ` Anthony Heading
2015-10-26 16:03   ` Ken Brown
2015-10-27  0:11     ` Mark Geisert
2015-10-27  8:46       ` Anthony Heading
2015-10-27  9:30         ` Mark Geisert [this message]
2015-10-28  4:49           ` Anthony Heading
2015-10-28  9:15             ` Mark Geisert
2015-10-28 13:05               ` Corinna Vinschen
2015-10-28 14:49                 ` Mark Geisert

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=loom.20151027T061000-194@post.gmane.org \
    --to=mark@maxrnd.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).