From: Martin Ortuno <martinortunogonzalez@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: Cygwin List <cygwin@cygwin.com>
Subject: Re: scons v4.3.0-1 outputs nothing on cygwin v2. 3.1
Date: Sun, 15 May 2022 20:43:47 -0500 [thread overview]
Message-ID: <CAGgcKD-feahZNPfPkTukw6Oym0u_gg1euzsuHfndp-ZmbFWmHQ@mail.gmail.com> (raw)
In-Reply-To: <887c2a73-c325-b86b-37d1-9ad281078a5f@cornell.edu>
Hi everyone,
Here the results...
$ which -a alternatives
/usr/sbin/alternatives
Then..
$ ls -glo $(which -a alternatives)
-rwxrwx---+ 1 18944 Apr 5 2009 /usr/sbin/alternatives
After that I ran…
$ /usr/sbin/alternatives --verbose --auto python
reading /var/lib/alternatives/python
Just to see if that helped I ran:
$ /usr/sbin/alternatives --test --auto python
auto
/usr/bin/python
/usr/bin/python3.9
39
would link /etc/alternatives/python -> /usr/bin/python3.9
Finally I ran:
$ /usr/sbin/alternatives --display python
python - status is auto.
link currently points to /usr/bin/python3.9
/usr/bin/python3.9 - priority 39
Current `best' version is /usr/bin/python3.9.
Thanks,
Martin
El dom., 15 de mayo de 2022 7:59 p. m., Ken Brown <kbrown@cornell.edu>
escribió:
> On 5/15/2022 6:03 PM, Martin Ortuno wrote:
> > $ ls -glo /usr/bin/python
> >
> > lrwxrwxrwx 1 13 Jun 3 2015 /usr/bin/python -> python2.7.exe
>
> This shows that you have a very old version of python2, going back to
> before the
> python versions were managed by the alternatives system.
>
> You can't expect to have a working Cygwin installation if you selectively
> update
> some packages while keeping old versions of others. I suggest that you
> update
> to the current release of each package.
>
> Ken
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
next prev parent reply other threads:[~2022-05-16 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 15:45 Martin Ortuno
2022-05-13 16:51 ` William Deegan
2022-05-13 20:30 ` Martin Ortuno
2022-05-13 20:41 ` Martin Ortuno
2022-05-13 22:12 ` William Deegan
2022-05-13 22:16 ` Martin Ortuno
2022-05-13 22:46 ` Brian Inglis
2022-05-15 17:10 ` Martin Ortuno
2022-05-15 20:43 ` Brian Inglis
2022-05-15 22:03 ` Martin Ortuno
2022-05-16 0:57 ` Ken Brown
2022-05-16 1:43 ` Martin Ortuno [this message]
2022-05-16 17:49 ` William Deegan
2022-05-15 23:37 ` Doug Henderson
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=CAGgcKD-feahZNPfPkTukw6Oym0u_gg1euzsuHfndp-ZmbFWmHQ@mail.gmail.com \
--to=martinortunogonzalez@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).