Bug 274498 - lang/python39: incorrectly links to /usr/local/lib/libuuid.so.1 installed by misc/e2fsprogs-libuuid (with patch)
Summary: lang/python39: incorrectly links to /usr/local/lib/libuuid.so.1 installed by ...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-python (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-15 17:48 UTC by Martin Birgmeier
Modified: 2023-10-21 16:11 UTC (History)
5 users (show)

See Also:

Attachments
patch to lang/python39 to disable linking to libuuid (743 bytes, patch)
2023-10-15 17:48 UTC, Martin Birgmeier 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Birgmeier 2023-10-15 17:48:30 UTC 
Created attachment 245643 [details]
patch to lang/python39 to disable linking to libuuid

Scenario:
- FreeBSD 12.4
- ports latest
- building ports using portmaster on machine A
- using some of the built ports on machine B: lang/python39 but not misc/e2fsprogs-libuuid

Result:
- on machine B, "pkg check -da" complains with "python39 is missing a required shared library: libuuid.so.1"

Expected result:
- lang/python39 should use only the uuid functions in FreeBSD's libc

Patch attached.

-- Martin
Comment 1 Vladimir Druzenko freebsd_committer freebsd_triage 2023-10-15 18:26:27 UTC 
Check this: https://github.com/python/cpython/issues/100369
Comment 2 Martin Birgmeier 2023-10-16 16:56:16 UTC 
(In reply to Vladimir Druzenko from comment #1)

Interesting, but only with python 3.12, whereas FreeBSD's default version is 3.9.
Comment 3 Charlie Li freebsd_committer freebsd_triage 2023-10-17 02:27:45 UTC 
Not inclined to accept this one. When building in isolated environments like poudriere, this has never been a problem. Not sorry but this is a great example of why building on live systems/environments is bad and is gradually recommended against anymore.

Regarding upstream activity on this issue, this isn't able to be backported to versions prior to the branch the relevant commits appeared in, due to being part of major structural changes.