Trubles compiling lxqt on RPi4

Mark Millard marklmi at yahoo.com
Thu May 13 20:36:01 UTC 2021


bob prohaska fbsd at www.zefox.net wrote on
Thu May 13 15:39:41 UTC 2021 :

> On Thu, May 13, 2021 at 08:13:07AM +0200, Jan Beich wrote:
> > >
> > > Moving to /usr/ports/json-glib and using 
> > > make -DBATCH MAKE_JOBS_UNSAFE=yes MAKE_JOBS_NUMBER=4 DISABLE_VULNERABILITIES=yes > make.log
> > > reports several instances of 
> > > error: unknown argument: '-fno-color-diagnostics'
> > 
> > Likely caused by desync between USES=meson and devel/meson, see
> > https://cgit.freebsd.org/ports/commit/?id=ff2796d5bc83
> > 
> > Try again after re-installing devel/meson.
> 
> That might be a hint which circles back to Mark's comments related to
> python37 vs -38. Trying to re-make devel/meson finds.
> 
> root at nemesis:/usr/ports/devel/meson # make -DBATCH FORCE_PKG_REGISTER=yes install
> ===>   meson-0.57.1_1 depends on package: py38-setuptools>0 - not found
> ===>  Installing for py38-setuptools-44.0.0_1
> ===>   Registering installation for py38-setuptools-44.0.0_1 as automatic
> Installing py38-setuptools-44.0.0_1...
> pkg-static: py38-setuptools-44.0.0_1 conflicts with py37-setuptools-44.0.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/ports/devel/py-setuptools
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/devel/meson
> 
> The fix for the -37 vs-38 conflict invokes portmaster, might it 
> suffice to simply deinstall -37 and explicitly replace it with
> -38 ? I'll give it a try.
> 
> Hmm, no dice. After deinstalling python37 and reinstalling python38 an
> attempt to make devel/meson still stops with
> 
> root at nemesis:/usr/ports/devel/meson # make -DBATCH DISABLE_VULNERABILITIES=yes install
> ===>   meson-0.57.1_1 depends on package: py38-setuptools>0 - not found
> ===>  Installing for py38-setuptools-44.0.0_1
> ===>  Checking if py38-setuptools is already installed
> ===>   Registering installation for py38-setuptools-44.0.0_1 as automatic
> Installing py38-setuptools-44.0.0_1...
> pkg-static: py38-setuptools-44.0.0_1 conflicts with py37-setuptools-44.0.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
> *** Error code 1
> 
> How did python38 get installed without py38-setuptools?

You have apparently chosen to build/update ports via a
technique that requires you to manage the dependencies, at
least some of the time. (Not that when is necessarily
obvious up front.)

Your environment is now based on a mix of python37 and
python 38 related materials. You are likely going to
need to rework/rebuild/reinstall things to avoid that.

Hints may come from that UPDATING that I quoted but
things are more broken overall than what UPDATING is
intended to cover. You might end up needing to
uninstall a bunch of stuff until python is unused
(or only one python is used) and then follow the
notes if you have only python37 use and want to
get to python38. Finally rebuild/reinstall what
was uninstalled, based on python38 as a context.

(I'm not even sure uninstalls are going to always work
correctly/completely in the mixed context.)

QUOTE
20210425:
  AFFECTS: users of python
  AUTHOR: kai at FreeBSD.org


  The default version of python3 and python was switched to 3.8.

  For ports users wanting to keep version 3.7 as default,
  add DEFAULT_VERSIONS+= python=3.7 python3=3.7 to make.conf

  Following procedures may ease the upgrade:

  For users of pre-build packages:
  # sh
  # for i in $(pkg query -g %n 'py37-*'); do pkg set -yn ${i}:py38-${i#py37-}; done
  # pkg upgrade

  For portmaster users:
  # sh
  # portmaster -o lang/python38 python37
  # REINSTALL="$(pkg info -o "*py37*" | awk '{printf "%s ", $2}')"
  # pkg delete -f "*py37*"
  # portmaster $REINSTALL
  # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py38 | cut -d : -f 1 | sort -u)
  # portmaster $REBUILD
  # REBUILD2=$(pkg list | grep python-37 | xargs pkg which | awk '{print $6}' | sort -u)
  # portmaster $REBUILD2
END QUOTE

Due to how I build/install ports, I've not had to deal
with ending up with the mix so I'm not familiar with
the details for recovering from a messy mix.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)



More information about the freebsd-ports mailing list