glib2: Type mismatch, gint64 does not match int64_t

[Dave-Allured (Dave Allured)]

Upstream developer said:

... int64_t is aliased to long long while gint64 is aliased to long. Those should never mismatch, and it means that GLib is misconfigured. That would seem to be caused by ​this patch (2023 May 13).

I guess you can work around it by ..., but it would be better to fix that patch; it's likely to break all sorts of assumptions down the line.

Upstream ticket: ​https://gitlab.gnome.org/GNOME/gjs/-/issues/608#note_2056862

This breaks updates for the latest upstream versions of port gjs.

[kencu (Ken)]

AFAICT, this goes back to ancient times

​https://github.com/macports/macports-ports/blob/ca3bacb8c5e7f35c5f71a9b3ca811691aa51836a/devel/glib2/files/patch-configure.in.diff

and has been continued ever since.

There have been times when gnome builds failed for me due to mismatched gint64 values, and similar, and I’ve had to patch source to fix this, not really understanding why. Maybe this is why.

[Dave-Allured (Dave Allured)]

The upstream ticket is getting interesting! Please watch that. Hold off on a Macports change, until upstream figures out what is going on.

​https://gitlab.gnome.org/GNOME/gjs/-/issues/608

[Dave-Allured (Dave Allured)]

Problem solved upstream. I anticipate a quick upstream release.

[Dave-Allured (Dave Allured)]

Fixed by gjs update to 1.80.1: ​https://github.com/macports/macports-ports/pull/23172#issuecomment-2016333274

No changes are needed for port glib2.

[christophecvr (christophecvr)]

Hello. On macbookpro i7 mid 2010 10.13.6 (High Sierra). It does not build. With the message info:build ld: symbol(s) not found for architecture x86_64. Which says not very much. But I just fetched the gjs package 1.80.1 and build it with command

meson setup ./build --prefix=/opt/local -Dprofiler=disabled -Dskip_dbus_tests=true -Dskip_gtk_tests=true -Dbsymbolic_functions=false
cd build
ninja install

as info meson detects self if gobject_introspection is needed . and uses it. It tried for the rest with and without the patch LD/ DYLID .Then I could trace the reason of that message. It is this :

dyld: Symbol not found: __cg_jpeg_resync_to_restart
  Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /opt/local/lib/libJPEG.dylib
 in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO

Yes I could do very dirty work around by temporary removing the /opt/local/lib/libjpeg.dylib (it is a link to jpeg8 or 9 in /opt/local/lib/) And then set a link to the macos /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO/Resources/libJPEG.dylib in /opt/local/lib . But the macos is a older version and then again will give new problems later on. Of course same will happen for libPng libGIF and libTIFF . Is there a way to avoid that unneeded mac test /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO . The builded software is using normally the gnu version of libjpeg and ...

[Dave-Allured (Dave Allured)]

@christophecvr you are describing a very different issue. For best results, please open a new ticket! Also you said "It does not build". WHAT PORT? This ticket discusses several different ports. Please be specific! In your new ticket, please attach a complete build log that includes the build failure. Good luck!

[Dave-Allured (Dave Allured)]

Any committers, please close this ticket as completed. It was supposed to auto-close on one of the above merges, but I guess I fumbled something in the commits. Thank you.

[christophecvr (christophecvr)]

ok yes I will open a new ticket. The gjs package doen not build on macos 10.13.6

[mascguy (Christopher Nielsen)]

Replying to Dave-Allured:

Any committers, please close this ticket as completed. It was supposed to auto-close on one of the above merges, but I guess I fumbled something in the commits. Thank you.

No worries, thanks for the heads-up!