From: tmacchant <tmacchant@yahoo.co.jp>
To: cygwin@cygwin.com
Subject: Re: built gnuplot does not run on the cygwin 2.0.0
Date: Mon, 04 May 2015 13:24:00 -0000 [thread overview]
Message-ID: <1430731959187-118060.post@n5.nabble.com> (raw)
In-Reply-To: <loom.20150504T103114-181@post.gmane.org>
> That status code is described as:
> 0xC0000022 STATUS_ACCESS_DENIED
> {Access Denied} A process has requested access to an object but has not
> been
> granted those access rights.
> https://msdn.microsoft.com/en-us/library/cc704588.aspx
> Check the modes and ACL on the executable and libraries you're trying to
> use.
> Regards,
> Achim.
Achim
As you said, I add the execute access right to the cygwx*.dll by chmod +x
command.
Now the gnuplot executable starts ordinary,
**************************************************
$ src/gnuplot
G N U P L O T
Version 5.1 patchlevel 0 last modified 2015-05-03
Copyright (C) 1986-1993, 1998, 2004, 2007-2015
Thomas Williams, Colin Kelley and many others
gnuplot home: http://www.gnuplot.info
mailing list: gnuplot-beta@lists.sourceforge.net
faq, bugs, etc: type "help FAQ"
immediate help: type "help" (plot window: hit 'h')
Terminal type set to 'wxt'
**************************************************
Thanks for the help.
Tatsuro
--
View this message in context: http://cygwin.1069669.n5.nabble.com/built-gnuplot-does-not-run-on-the-cygwin-2-0-0-tp118056p118060.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
prev parent reply other threads:[~2015-05-04 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 8:29 tmacchant
2015-05-04 8:36 ` Marco Atzeri
2015-05-04 9:32 ` tmacchant
2015-05-04 9:13 ` Achim Gratz
2015-05-04 13:24 ` tmacchant [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=1430731959187-118060.post@n5.nabble.com \
--to=tmacchant@yahoo.co.jp \
--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).