libvpx @1.13.1 conflicts with installed gtest

[MaintenanceCosts]

libvpx fails consistently, after cleaning, with "Undefined symbols for architecture arm64" error. Error is the same whether variant is default or +universal. Log attached.

[MaintenanceCosts]

Logfile

[kencu (Ken)]

and yet, I built it without any trouble:

% port -v installed libvpx
The following ports are currently installed:
  libvpx @1.13.1_0 requested_variants='' platform='darwin 24' archs='arm64' date='2024-09-25T14:47:24-0700'

[kencu (Ken)]

I can reproduce your error if I install the "gtest" port and then try to rebuild libvpx.

So deactivate gtest

sudo port deactivate gtest

and then clean and install libvpx, and you should be good. You can reactivate gtest after libvpx is installed if you want.

We have a "conflicts_build" mechanism in MacPorts, so we'll have to declare this in the libvpx Portfile.

On a broader note, gtest is a port that often collides like this. It should probably be installed in a sequestered folder, not in the main "lib" folder, to avoid accidentally linking it in when you don't really want it.

[ryandesign (Ryan Carsten Schmidt)]

Replying to kencu:

It should probably be installed in a sequestered folder, not in the main "lib" folder, to avoid accidentally linking it in when you don't really want it.

…creating additional work everytime you actually want to use it.

[kencu (Ken)]

but avoiding 100,000 errors by including it by accident.

[kencu (Ken)]

In bd7859ad676b93ea0dfe3eb11b2b09da870a3009/macports-ports (master):

libvpx-*: conflicts with gtest

closes: #70989

[jmroot (Joshua Root)]

Is there not any way to avoid this? Declaring a build-time conflict still results in really poor UX.

[kencu (Ken)]

there may be some method that could be discovered, certainly.

I’ll reopen this and we can see if anyone can do that.