#68074 closed defect (fixed)

nyxt @3.5.0: The value NIL is not of type GOBJECT:GTYPE

Reported by: tylerwolf35 (Tyler Wolf) Owned by: catap (Kirill A. Korinsky)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: arm64 Cc:
Port: nyxt

Description

I get the following error while trying to build the 'nyxt' port on a Macbook Pro M1 Max: 'Error: Failed to build nyxt: command execution failed'

Attached is the build log.

Thank you.

Attachments (1)

main.log (4.3 MB) - added by tylerwolf35 (Tyler Wolf) 15 months ago.
'nyxt' build log

Change History (11)

comment:1 Changed 15 months ago by ryandesign (Ryan Carsten Schmidt)

Keywords: arm64 added; arm removed
Owner: set to catap
Status: newassigned
Summary: Cannot build 'nyxt' on M1 maxnyxt @3.5.0: The value NIL is not of type GOBJECT:GTYPE

Log says:

:info:build Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING
:info:build                                   {700F387633}>:
:info:build   The value
:info:build     NIL
:info:build   is not of type
:info:build     GOBJECT:GTYPE

Version 3.6.1 was released today; maybe updating the port would help.

comment:2 in reply to:  1 Changed 15 months ago by tylerwolf35 (Tyler Wolf)

Replying to ryandesign:

Log says:

:info:build Unhandled TYPE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING
:info:build                                   {700F387633}>:
:info:build   The value
:info:build     NIL
:info:build   is not of type
:info:build     GOBJECT:GTYPE

Version 3.6.1 was released today; maybe updating the port would help.

That could be an issue, however based on the error I doubt that would resolve this, as it seems to be an issue with cl-cffi-gtk and not the nyxt port.

comment:3 Changed 15 months ago by catap (Kirill A. Korinsky)

Upgrade isn't possible until webkit2-gtk is upgraded :(

I've tried to upgrade to 3.6.0 and reported a regression here https://github.com/atlas-engineer/nyxt/issues/3131 and upstream confirmed that we're using too old webkit2-gtk.

I'm continue my effort to upgrade it to the last version: https://github.com/catap/macports-ports/tree/webkit2-gtk-devel, but it need some work before I can finish it.

https://github.com/macports/macports-ports/pull/19914 should make my work a bit easier, but it also quite huge.

So, we're stuck a bit her with update.

Regarding your issue: I'll take a look a bit later today.

comment:4 Changed 15 months ago by catap (Kirill A. Korinsky)

As part of https://github.com/macports/macports-ports/pull/20198 I've updated cl-trivial-utf-8 from 20220223 20220828 and fixes https://trac.macports.org/ticket/68061 which seems like a duplicated of this one.

Inside your build log I see:

:debug:main cl-trivial-utf-8 20220223_0 exists in the ports tree
:debug:main cl-trivial-utf-8 20220223_0  is the latest installed
:debug:main cl-trivial-utf-8 20220223_0  is active

What means that you are using ports before that fix. This fix was merged 4 days ago and I think that port sync should fix your issue.

Last edited 15 months ago by catap (Kirill A. Korinsky) (previous) (diff)

Changed 15 months ago by tylerwolf35 (Tyler Wolf)

Attachment: main.log added

'nyxt' build log

comment:5 in reply to:  4 Changed 15 months ago by tylerwolf35 (Tyler Wolf)

Replying to catap:

As part of https://github.com/macports/macports-ports/pull/20198 I've updated cl-trivial-utf-8 from 20220223 20220828 and fixes https://trac.macports.org/ticket/68061 which seems like a duplicated of this one.

Inside your build log I see:

:debug:main cl-trivial-utf-8 20220223_0 exists in the ports tree
:debug:main cl-trivial-utf-8 20220223_0  is the latest installed
:debug:main cl-trivial-utf-8 20220223_0  is active

What means that you are using ports before that fix. This fix was merged 4 days ago and I think that port sync should fix your issue.

I still appear to get the same error. I have updated the build log, which now reads the same debug statements except for "cl-trivial-utf-8 20220828_0".

comment:6 Changed 15 months ago by catap (Kirill A. Korinsky)

You last log contains:

:info:build objc[14005]: Class GNotificationCenterDelegate is implemented in both /opt/homebrew/Cellar/glib/2.76.4/lib/libgio-2.0.0.dylib (0x105dd86b0) and /opt/local/lib/libgio-2.0.0.dylib (0x106d28690). One of the two will be used. Which one is undefined.

=> it mixes up libraries from different package systems. I never thought that someone may have MacPorts and homebrew or flink at the same system... well.. I'll try to go througth all lisp ports and switch it to MacPorts stricly. But I need some time.

comment:7 Changed 15 months ago by catap (Kirill A. Korinsky)

PR is opened https://github.com/macports/macports-ports/pull/20292

This issue should be fixed by https://github.com/macports/macports-ports/pull/20292/commits/b3aae5148695409ecd42d0f36b3f48e4da40cd93

You may "fix" it on your system without waiting until it is merged by editing /opt/local/share/common-lisp/source/cl-cffi/src/libraries.lisp and redefine darwin-fallback-library-path function into:

(defun darwin-fallback-library-path ()
  (or (explode-path-environment-variable "DYLD_FALLBACK_LIBRARY_PATH")
      (list (merge-pathnames #p"lib/" (user-homedir-pathname))
            ;; #+arm64 #p"/opt/homebrew/lib/"
            #p"/opt/local/lib/"
            ;; #p"/usr/local/lib/"
            #p"/usr/lib/")))

Here I simple removes Homebrews paths by commenting them.

If you may test it, I'll be very appricieted because I made my best blind shot here.

comment:8 Changed 15 months ago by catap (Kirill A. Korinsky)

In 6df448ed0cb7b1f9c95adadbc6495b43d03b3a65/macports-ports (master):

cl-async: enforce use MacPorts OpenSSL

See: #68074

comment:9 Changed 15 months ago by catap (Kirill A. Korinsky)

In 75efafd53832274209c0457f34dd8ed51f36aeec/macports-ports (master):

cl-plus-ssl: enforce use MacPorts OpenSSL

See: #68074

comment:10 Changed 15 months ago by catap (Kirill A. Korinsky)

Resolution: fixed
Status: assignedclosed

In c3be0cb19b26f88d2d507a6d73594b48cde7ca8c/macports-ports (master):

cl-cffi: enforce use MacPorts libs only

Closes: #68074

Note: See TracTickets for help on using tickets.