From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Setup shows errors from gnuplot-base.dash and python38-devel.sh
Date: Wed, 14 Jul 2021 21:59:44 +0200 [thread overview]
Message-ID: <d69baa77-8d7e-053f-5563-0de6e730795a@gmail.com> (raw)
In-Reply-To: <87sg0g67o7.fsf@Rainer.invalid>
On 14.07.2021 21:02, Achim Gratz 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).
>
>
> Regards,
> Achim.
>
Hi Doug,
any error running directly
/etc/postinstall/python38-devel.sh
After that the following commands should produce
somthing similar to :
$ alternatives --display 2to3
2to3 - status is auto.
link currently points to /usr/bin/2to3-3.8
/usr/bin/2to3-3.8 - priority 38
/usr/bin/2to3-3.6 - priority 36
/usr/bin/2to3-3.7 - priority 37
Current `best' version is /usr/bin/2to3-3.8.
$ alternatives --display python3-config
python3-config - status is auto.
link currently points to /usr/bin/python3.8-config
/usr/bin/python3.8-config - priority 38
/usr/bin/python3.6-config - priority 36
/usr/bin/python3.7-config - priority 37
Current `best' version is /usr/bin/python3.8-config.
next prev parent reply other threads:[~2021-07-14 19:59 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 [this message]
2021-07-14 21:08 ` Doug Henderson
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=d69baa77-8d7e-053f-5563-0de6e730795a@gmail.com \
--to=marco.atzeri@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).