Has scallywag problems with requirements ?

Has scallywag problems with requirements ?

[Marco Atzeri]

Hi Kon,

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

but python38 python39 python-38-devel python39-devel

all should require alternatives


$ grep require python38-devel/python38-devel-3.8.16-1.hint
requires: alternatives bash pkg-config python38 python38-setuptools 
libcrypt-devel


Regards
Marco

Re: Has scallywag problems with requirements ?

[Marco Atzeri]

On 15.04.2023 18:34, Marco Atzeri wrote:
> Hi Kon,

Jon (of course)

> 
> 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
> 
> but python38 python39 python-38-devel python39-devel
> 
> all should require alternatives
> 
> 
> $ grep require python38-devel/python38-devel-3.8.16-1.hint
> requires: alternatives bash pkg-config python38 python38-setuptools 
> libcrypt-devel
> 
> 
> Regards
> Marco

It seems there are other general issues

 >>> Compiling make-4.4.1-2.x86_64
cp: cannot stat '/usr/share/gettext/config.rpath': No such file or directory
autoreconf-2.71: export WARNINGS=
autoreconf-2.71: Entering directory '.'
autoreconf-2.71: running: autopoint --force
Can't exec "autopoint": No such file or directory at 
/usr/share/autoconf2.7/Autom4te/FileUtils.pm line 293.
autoreconf-2.71: error: autopoint failed with exit status: 1
*** ERROR: autoreconf failed

Re: Has scallywag problems with requirements ?

[Jon Turney]

On 15/04/2023 17:42, Marco Atzeri via Cygwin-apps wrote:
> On 15.04.2023 18:34, Marco Atzeri wrote:
>> Hi Kon,
> 
> Jon (of course)
> 
>>
>> 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.

[...]
> 
> It seems there are other general issues
> 
>  >>> Compiling make-4.4.1-2.x86_64
[...]
> Can't exec "autopoint": No such file or directory at 
> /usr/share/autoconf2.7/Autom4te/FileUtils.pm line 293.
> autoreconf-2.71: error: autopoint failed with exit status: 1
> *** ERROR: autoreconf failed

I think this is just a failure to BUILD_REQUIRES gettext-devel for 
autopoint?

Re: Has scallywag problems with requirements ?

[Jon Turney]

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.

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?

Re: Has scallywag problems with requirements ?

[Marco Atzeri]

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

Re: Has scallywag problems with requirements ?

[Marco Atzeri]

On 16.04.2023 03:32, Marco Atzeri wrote:
> On 15.04.2023 20:31, Jon Turney wrote:

>> 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
> 

for documentation this variant works

    --with-python PYTHON=/usr/bin/python${v}

just implemented in version -2 as I was re-enabling the FTP
protocol that was disabled by default upstream

Regards
Marco