From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Has scallywag problems with requirements ?
Date: Sun, 16 Apr 2023 03:32:33 +0200 [thread overview]
Message-ID: <db3e23a7-a19f-48a0-5b9e-0ad77b7316e4@gmail.com> (raw)
In-Reply-To: <5bc4e0c6-b429-4997-3377-b5930031257b@dronecode.org.uk>
On 15.04.2023 20:31, Jon Turney wrote:
> On 15/04/2023 19:27, Jon Turney via Cygwin-apps wrote:
>> On 15/04/2023 17:42, Marco Atzeri via Cygwin-apps wrote:
>>> On 15.04.2023 18:34, Marco Atzeri wrote:
>>>> building libxml2
>>>>
>>>> Jobs 5790
>>>> https://github.com/cygwin/scallywag/actions/runs/4708605404
>>>>
>>>> I see
>>>>
>>>> /cygdrive/d/a/scallywag/libxml2/libxml2.cygport: line 72:
>>>> alternatives: command not found
>>
>> I don't understand how this cygport is supposed to work.
>>
>> It simply runs 'alternatives', but being installed as
>> /usr/sbin/alternatives, it's not on the path.
you are right. It worked locally on modified PATH.
I will modify the cygport.
>
> Also, if the configure script supports it, wouldn't it be better to set
> the PYTHON env var, or do --with-python=/usr/bin/python${v} than
> fiddling with alternatives?
the configure seems to not accept the
--with-python=/usr/bin/python${v}
it continued to pick python3.9 also when I requested 3.8
I have however not checked the details of the configure.ac
Regards
Marco
next prev parent reply other threads:[~2023-04-16 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 16:34 Marco Atzeri
2023-04-15 16:42 ` Marco Atzeri
2023-04-15 18:27 ` Jon Turney
2023-04-15 18:31 ` Jon Turney
2023-04-16 1:32 ` Marco Atzeri [this message]
2023-04-16 12:08 ` Marco Atzeri
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=db3e23a7-a19f-48a0-5b9e-0ad77b7316e4@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).