On 2022-06-04 04:40, Stefan Esser wrote:
Am 04.06.22 um 01:02 schrieb Kubilay Kocak:
BUILD_ALL_PYTHON_FLAVORS was implemented in the reverse of what it should
have
been (DONT_BUILD_ALL_PYTHON_FLAVORS or other).
It was implemented ostensibly as a convenience for poudriere, such that the
default
Am 04.06.22 um 01:02 schrieb Kubilay Kocak:
> BUILD_ALL_PYTHON_FLAVORS was implemented in the reverse of what it should have
> been (DONT_BUILD_ALL_PYTHON_FLAVORS or other).
>
> It was implemented ostensibly as a convenience for poudriere, such that the
> default was for poudriere *not* build all
On 3/06/2022 2:42 pm, Tatsuki Makino wrote:
Sorry, this email was delivered to my junk folder.
I just pulled this up now :)
Chris wrote on 2022/05/28 14:25:
I just bumped into this problem after checking out a fresh ports tree and
building
a port that dependant on devel/py-doit. It complained
Sorry, this email was delivered to my junk folder.
I just pulled this up now :)
Chris wrote on 2022/05/28 14:25:
> I just bumped into this problem after checking out a fresh ports tree and
> building
> a port that dependant on devel/py-doit. It complained much the same as above.
> required
> my
On 2022-05-26 14:41, Chris wrote:
On 2022-05-26 14:29, Tatsuki Makino wrote:
Daniel Braniss wrote on 2022/05/27 00:23:
sorry, my bad, it was make FLAVOR=py37
and the result was
===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38.
Defining BUILD_ALL_PYTHON_FLA
> On 27 May 2022, at 02:35, Tatsuki Makino wrote:
>
> Chris wrote on 2022/05/27 06:41:
>> On 2022-05-26 14:29, Tatsuki Makino wrote:
>>>
>>> env BUILD_ALL_PYTHON_FLAVORS=1 make -C /usr/ports/multimedia/openshot
>>> FLAVOR=py39 build
>> Wouldn't make -DBUILD_ALL_PYTHON_FLAVORS ... get it?
>>
Chris wrote on 2022/05/27 06:41:
> On 2022-05-26 14:29, Tatsuki Makino wrote:
>>
>> env BUILD_ALL_PYTHON_FLAVORS=1 make -C /usr/ports/multimedia/openshot
>> FLAVOR=py39 build
> Wouldn't make -DBUILD_ALL_PYTHON_FLAVORS ... get it?
> Or add BUILD_ALL_PYTHON_FLAVORS=true to make.conf(5) work? Even if
## Daniel Braniss (da...@cs.huji.ac.il):
> but some have 3.6+, and make FLAVOR=37 failes with unknown flavor …
In theory you should only handle FLAVOR manually in rather rare cases.
Did you read UPDATING entry 20210425 and set DEFAULT_VERSIONS
accordingly?
Regards,
Christoph
--
Spare Space
On 2022-05-26 14:29, Tatsuki Makino wrote:
Daniel Braniss wrote on 2022/05/27 00:23:
sorry, my bad, it was make FLAVOR=py37
and the result was
===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38.
Defining BUILD_ALL_PYTHON_FLAVORS is a way to unlock thi
Daniel Braniss wrote on 2022/05/27 00:23:
>
> sorry, my bad, it was make FLAVOR=py37
> and the result was
> ===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38.
>
>
Defining BUILD_ALL_PYTHON_FLAVORS is a way to unlock this restriction.
Perhaps
ep 3,7.
>> some Makefiles require 3,8+, again no problem.
>> but some have 3.6+, and make FLAVOR=37 failes with unknown flavor …
>>
>> any work around?
>
> Use FLAVOR=py37, not FLAVOR=37.
>
> -Dimitry
>
sorry, my bad, it was make FLAVOR=py37
and the result was
===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38.
On 26 May 2022, at 16:10, Daniel Braniss wrote:
>
> im using portmaster.
>
> after a resent update to /usr/ports, the default python became 3.8, fine by
> me, but I still want to
> keep 3,7.
> some Makefiles require 3,8+, again no problem.
> but some have 3.6+, and make FLAVOR=37 failes with un
im using portmaster.
after a resent update to /usr/ports, the default python became 3.8, fine by me,
but I still want to
keep 3,7.
some Makefiles require 3,8+, again no problem.
but some have 3.6+, and make FLAVOR=37 failes with unknown flavor …
any work around?
cheers,
danny
13 matches
Mail list logo
