Summary: | net-im/libpurple: build error in package phase | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Felix Palmen <zirias> | ||||
Component: | Individual Port(s) | Assignee: | Joe Marcus Clarke <marcus> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | Flags: | bugzilla:
maintainer-feedback?
(marcus) |
||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Felix Palmen
2021-04-20 19:31:55 UTC
It packages fine for me. It seems something prevented your build from finding D-Bus. But without full logs, I cannot say for certain why this is happening. Ok, configure seems to disable dbus because it's missing python 3: checking for dbus-1 >= 0.60 dbus-glib-1 >= 0.60... yes checking for python3... no configure: WARNING: python3 interpreter not found in your path Building without D-Bus support Here's the full log: http://home.palmen-it.de/builder/data/def-default/2021-04-20_21h13m53s/logs/errors/libpurple-2.14.3_1.log The same seems to happen on official builders, although this is still an older version: http://beefy15.nyi.freebsd.org/data/130i386-default/338d8ba0f777/logs/errors/libpurple-2.14.3.log Created attachment 224320 [details]
fix building with dbus
Having a closer look: the ./configure argument for python changed. Attached patch fixes the build for me.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=1cf4c751968e4a05db44565f7db87c232ff8e9c3 commit 1cf4c751968e4a05db44565f7db87c232ff8e9c3 Author: Joe Marcus Clarke <marcus@FreeBSD.org> AuthorDate: 2021-04-21 12:31:50 +0000 Commit: Joe Marcus Clarke <marcus@FreeBSD.org> CommitDate: 2021-04-21 12:31:50 +0000 net-im/libpurple: Bump Python version. Pidgin now wants Python 3 so be explicit about that. It also changed the argument to find the Python command. PR: 255280 net-im/libpurple/Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) Yep, seems Python 3 is explicitly needed now. This has been fixed in PORTREVISION 2. |