From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Setup shows errors from gnuplot-base.dash and python38-devel.sh
Date: Wed, 14 Jul 2021 15:08:17 -0600 [thread overview]
Message-ID: <CAJ1FpuMLQjhM9-Sqz4sgu-dYd5qiiZsp89SnbnKPFFGvQJa=rQ@mail.gmail.com> (raw)
In-Reply-To: <87sg0g67o7.fsf@Rainer.invalid>
On Wed, 14 Jul 2021 at 13:03, Achim Gratz <Stromeko@nexgo.de> wrote:
>
> Doug Henderson via Cygwin writes:
> > The first error message occurred when I installed all pending packages
> > this morning. I hoped to heal the problem by reinstalling the
> > installed gnuplot packages. Now I get both the messages.
>
> If you look in /var7Log/setup.log.full you should be able to see what
> error messages, if any, were recorded.
>
> The gnuplot related script should just set up the current alternative
> for "gnuplot" to use, but something on your system seems to prevent
> that from happening. You can also run the script in sh (you must tell
> the shell to source it) and should get the same error (most likely).
When I do that in an elevated shell:
$ cd /etc/postinstall/
$ cat gnuplot-base.dash
/usr/sbin/alternatives --install /usr/bin/gnuplot gnuplot
/usr/bin/gnuplot-base.exe 10
$ . gnuplot-base.dash
failed to read link /usr/bin/gnuplot: No such file or directory
failed to link /usr/bin/gnuplot -> /etc/alternatives/gnuplot: No such
file or directory
$
These are the same messages as I find in "/var/Log/setup.log.full".
$ ls -l /usr/bin/gnuplot*
-rwxr-xr-x 1 Admin None 1444371 Jun 12 03:40 /usr/bin/gnuplot-base.exe
I don't know enough about alternatives to diagnose this problem.
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
next prev parent reply other threads:[~2021-07-14 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:59 Doug Henderson
2021-07-14 19:02 ` Achim Gratz
2021-07-14 19:59 ` Marco Atzeri
2021-07-14 21:08 ` Doug Henderson [this message]
2021-07-14 22:31 ` Ken Brown
2021-07-15 1:20 ` Doug Henderson
2021-07-15 11:57 ` Ken Brown
2021-07-15 16:04 ` Doug Henderson
2021-07-15 16:18 ` ASSI
2021-07-16 3:59 ` Andrey Repin
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='CAJ1FpuMLQjhM9-Sqz4sgu-dYd5qiiZsp89SnbnKPFFGvQJa=rQ@mail.gmail.com' \
--to=djndnbvg@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).