Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

That's exactly what I described above and what worked for me. On Wed, 2021-12-01 at 17:56 -0500, monochrome wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981 > > I guess the "fix" is to install one or more from within the ports > tree > and not using portmaster >

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

monochrome: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981 > > I guess the "fix" is to install one or more from within the ports tree and > not using portmaster No. py-packaging still has a BUILD_DEPENDS on py-setuptools, so the ports build will recurse there. Any py-setuptools sti

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

On 2/12/2021 9:56 am, monochrome wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981 I guess the "fix" is to install one or more from within the ports tree and not using portmaster On 12/1/21 16:55, Christian Weisgerber wrote: On 2021-11-28, Kevin Oberman wrote: If I remember

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259981 I guess the "fix" is to install one or more from within the ports tree and not using portmaster On 12/1/21 16:55, Christian Weisgerber wrote: On 2021-11-28, Kevin Oberman wrote: If I remember correctly, the fix is to de-install bot

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

On 2021-11-28, Kevin Oberman wrote: > If I remember correctly, the fix is to de-install both py38-packaging and > py38-setuptools. >> pkg delete -f py38-setuptools >> pkg delete -f py38-packaging >> portmaster devel/pkg-packaging >> portmaster devel/py-setuptools I'm stuck in the same catch-22 a

Re: (260087) log of changes to /usr/ports/UPDATING (was: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools)

On Sat, Nov 27, 2021 at 9:22 PM Graham Perrin wrote: > > > On 28/11/2021 02:52, Kevin Oberman wrote: > > … like /usr/ports/UPDATING had been abandoned. The last update was over > > a year ago. … > > Either Kevin's ports tree is more than a year out of

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

I could finally solve the issue. Obvously, py38-packaging was missing. Unfortunately, portmaster did not detect the dependency I devel/py- packaging could not even be installed using portmaster. But a "make install" helped. Subsequently I could upgrade the initially mentioned ports. I am not sure,

(260087) log of changes to /usr/ports/UPDATING (was: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools)

On 28/11/2021 02:52, Kevin Oberman wrote: … like /usr/ports/UPDATING had been abandoned. The last update was over a year ago. … Either Kevin's ports tree is more than a year out of date, or (more likely) we're disoriented by

Re: Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

On Sat, Nov 27, 2021 at 12:04 PM Dr. Peter Voigt wrote: > I am currently facing a strange problem when tryping to upgrade > following ports: > > # pkg version -vIL= > py38-pycparser-2.20< needs updating (index has 2.21) > py38-pyparsing-3.0.4 < needs updating (in

Unable to build Python38 ports like devel/py38-pycparser and even py38-setuptools

I am currently facing a strange problem when tryping to upgrade following ports: # pkg version -vIL= py38-pycparser-2.20< needs updating (index has 2.21) py38-pyparsing-3.0.4 < needs updating (index has 3.0.6) py38-snowballstemmer-2.1.0 < need