Bug 285869 - devel/glib20: build broken, cannot find iconv
Summary: devel/glib20: build broken, cannot find iconv
Status: Closed DUPLICATE of bug 285863
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-03 17:11 UTC by Helge Oldach
Modified: 2025-04-04 06:38 UTC (History)
3 users (show)

See Also:
freebsd: maintainer-feedback? (desktop)


Attachments
/usr/obj/usr/ports/devel/gobject-introspection/work-bootstrap/gobject-introspection-1.82.0/_build/meson-logs/meson-log.txt (429.32 KB, text/plain)
2025-04-03 17:12 UTC, Helge Oldach
no flags Details
typescript (48.60 KB, text/plain)
2025-04-03 17:27 UTC, Helge Oldach
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helge Oldach 2025-04-03 17:11:30 UTC
Doesn't build since today's update to 2.82.4 (commit 7b5824485cbe25c20d59fb0f82e043aced6a3fd2). The error message is the same as the old bug #271758.


[...]
glib| Run-time dependency threads found: YES
glib| Header "pthread.h" has symbol "pthread_attr_setstacksize" : YES
glib| Header "pthread.h" has symbol "pthread_attr_setinheritsched" : YES
glib| Header "pthread.h" has symbol "pthread_condattr_setclock" : YES
glib| Header "pthread.h" has symbol "pthread_cond_timedwait_relative_np" : NO
glib| Header "pthread.h" has symbol "pthread_getname_np" : YES
glib| Header "pthread.h" has symbol "pthread_getaffinity_np" : NO
glib| Checking if "pthread_setname_np(const char*)" with dependency threads links: NO
glib| Checking if "pthread_setname_np(pthread_t, const char*)" with dependency threads links: YES
glib| Checking if "stack grows check" runs: NO (1)
glib| Run-time dependency iconv found: NO (tried builtin and system)

subprojects/glib/meson.build:2200:13: ERROR: Dependency "iconv" not found, tried builtin and system

A full log can be found at /usr/obj/usr/ports/devel/gobject-introspection/work-bootstrap/gobject-introspection-1.82.0/_build/meson-logs/meson-log.txt
WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
===>  Script "configure" failed unexpectedly.
Please report the problem to desktop@FreeBSD.org [maintainer] and attach the
"/usr/obj/usr/ports/devel/gobject-introspection/work-bootstrap/gobject-introspection-1.82.0/_build/meson-logs/meson-log.txt"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/devel/gobject-introspection
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/devel/gobject-introspection
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/devel/glib20
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/glib20
Comment 1 Helge Oldach 2025-04-03 17:12:56 UTC
Created attachment 259302 [details]
/usr/obj/usr/ports/devel/gobject-introspection/work-bootstrap/gobject-introspection-1.82.0/_build/meson-logs/meson-log.txt
Comment 2 Gleb Popov freebsd_committer freebsd_triage 2025-04-03 17:13:20 UTC
The log says that it is devel/gobject-introspection that fails?
Comment 3 Helge Oldach 2025-04-03 17:17:10 UTC
(In reply to Gleb Popov from comment #2)
Looks like it: Both glib20 and gobject-introspection were update in the same commit today.
Comment 4 Gleb Popov freebsd_committer freebsd_triage 2025-04-03 17:17:49 UTC
Please post the command you're running to build the port and full log that gets produced by this command.
Comment 5 Helge Oldach 2025-04-03 17:27:43 UTC
Created attachment 259303 [details]
typescript
Comment 6 Helge Oldach 2025-04-03 17:30:01 UTC
OPTIONS:

root@latitude /usr/ports/devel/glib20 # cat /var/db/ports/devel_gobject-introspection/options
# This file is auto-generated by 'make config'.
# Options for gobject-introspection-1.82.0,1
_OPTIONS_READ=gobject-introspection-1.82.0,1
_FILE_COMPLETE_OPTIONS_LIST=TEST
OPTIONS_FILE_UNSET+=TEST
root@latitude /usr/ports/devel/glib20 # cat /var/db/ports/devel_glib20/options
# This file is auto-generated by 'make config'.
# Options for glib-2.82.4,2
_OPTIONS_READ=glib-2.82.4,2
_FILE_COMPLETE_OPTIONS_LIST=DOCS FAM_ALTBACKEND MANPAGES NLS TEST
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_UNSET+=FAM_ALTBACKEND
OPTIONS_FILE_SET+=MANPAGES
OPTIONS_FILE_UNSET+=NLS
OPTIONS_FILE_UNSET+=TEST
Comment 7 Helge Oldach 2025-04-03 17:31:30 UTC
I suspect that the newly introduced FLAVORization is broken. gobject-introspection builds with FLAVOR=bootstrap in the first place, but then also seems to build as default? I'm kind of lost here...
Comment 8 Gleb Popov freebsd_committer freebsd_triage 2025-04-03 17:32:51 UTC
I see the problem now. Run

make clean deinstall reinstall

for the devel/glib20 port. This will build and install glib-bootstrap and gobject-introspection-bootstrap ports first, and then fail due a conflict before the install stage. Once you bump into a conflict run

pkg remove glib-bootstrap gobject-introspection-bootstrap

and then

make install

again. This should conclude your upgrade.
Comment 9 Helge Oldach 2025-04-04 06:24:40 UTC
(In reply to Gleb Popov from comment #8)
Thanks, this procedure worked.

Would that be needed upon every future glib upgrade?
Comment 10 Gleb Popov freebsd_committer freebsd_triage 2025-04-04 06:33:22 UTC
This will be required if upstream make a breaking change which would require bumping the glib dependency version. Until then all further upgrades should go smoothly.

I still looking a way to make this easier for ports users. Let's close this for now, there is another PR that can serve as a tracking one: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285863

*** This bug has been marked as a duplicate of bug 285863 ***
Comment 11 Helge Oldach 2025-04-04 06:37:08 UTC
Oh - I just noticed the UPDATING comment. The story is clear; thank you for providing guidance.
Comment 12 Helge Oldach 2025-04-04 06:38:18 UTC
*** This bug has been marked as a duplicate of bug 285863 ***