Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4

Mark Millard marklmi at
Sun May 16 08:11:51 UTC 2021

On 2021-May-16, at 00:16, Tatsuki Makino <tatsuki_makino at> wrote:

> Mark Millard via freebsd-ports wrote on 2021/05/16 10:57:
>> In the form that I use poudriere I use something
>> like the following. I presume here that /usr/src
>> is populated and has the source for the system
>> involved. (I do not remember your describing its
>> status.)
> (Omitted below)
> I was just wondering...
> If you want to use the sources in /usr/src and collect the files in /usr/obj to make a jail, the following is easier.
> poudriere jail -c -j main -m 'src=/usr/src' -v `make -C /usr/src/release/ -V VERSION VERSION=\$\{REVISION:Q\}-\$\{BRANCH:Q\}`
> Updating it can be done with just the following.
> poudriere jail -u -j main

Bob already does a buildworld based on /usr/src for other
reasons/uses than poudriere. My suggestions are targeted
to resusing that buildworld result instead of involving
doing another buildworld for poudriere. It is also biased
to not changing how he does that buildworld (out of scope
to what he was asking about). So far as I know he does
not use /usr/src/release to do builds. Bob's system is
not fast, each buildworld is time consuming.

Would your command suggestion reuse his already-existing

In my own use the same is true: I buildworld separately
before any poudriere activity (for other reasons/uses)
and then I reuse the buildworld that resulted for
also setting up poudriere later.

In essence, the same buildworld that generates what I
boot is later also used to set up (or update) a
poudriere. In other contexts, I set up (or update) an
independent chroot directory tree first and later a
poudriere directory tree --via one buildworld used
for setting up (or updating) both.

I do not use /usr/src/release to do buildworld or
installworld activities.

As most of the systems involved for my activity are
far from fast, avoiding extra buildworlds and reusing
buildworld results saves time. It also saves storage.
(I choose to work the same way on the fast
ThreadRipper 1950X for uniformity of procedure.)

Mark Millard
marklmi at
( went
away in early 2018-Mar)

More information about the freebsd-ports mailing list