unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Dariqq <dariqq@posteo.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 75157@debbugs.gnu.org
Subject: bug#75157: Grafting inconsistency with multiple outputs is causing problems
Date: Sun, 29 Dec 2024 09:30:54 +0000	[thread overview]
Message-ID: <bf6c3172-132b-4290-b023-38a68652411c@posteo.net> (raw)
In-Reply-To: <87o70vxrna.fsf@pelzflorian.de>

Hello FLorian,


I think you are experiencing a different (related) issue because the 
problem I seems to vanish by linking to the glib that is used by g-golf 
instead (the --no-grafts options ensures that only one glib is in my 
guix shell)

On 29.12.24 01:24, pelzflorian (Florian Pelz) wrote:
> 
> 
> Both my GLibs have one output only.  I still believe above guix commit
> is the first bad commit for you, as well, and
> 
> guix time-machine -q --commit=78c4d00ab02ab41a22058cdbec0329752e47580f
> 
> will show the error and parent commit
> 
> guix time-machine -q --commit=08e0144d2338c8fb51e52e74274554583d0faa69
> 
> will be fine.  Is it?
> 



The problem i am seeing is still available in 
08e0144d2338c8fb51e52e74274554583d0faa69.


Here is what I've been playing around with:
a simple c file that just loads a scm file.
a simple scm file that just tries to instantiate a gobject class (in 
this example from json-glib but that is irrelevant, using something 
small and simple)

--8<---------------cut here---------------start------------->8---
main.c:
#include <libguile.h>

int
main (int argc, char **argv)
{
     scm_init_guile();
     scm_c_primitive_load("foo.scm");
}

foo.scm:
(use-modules (g-golf))

(gi-import "Json")

(describe (make <json-parser>
	    #:immutable #t))


Build with
gcc -o main main.c \
     `pkg-config --cflags --libs guile-3.0` \
     `pkg-config --cflags --libs gobject-2.0`

Running this with grafts:
  ./main

(process:3071): GLib-GObject-CRITICAL **: 08:50:36.946: 
g_object_new_is_valid_property: object class 'JsonParser' has no 
property named 'immutable'
#<<json-parser> 7f186b2f56d0> is an instance of class <json-parser>
Slots are:
      g-inst = #<pointer 0x1445e900>

(process:3071): GLib-GObject-CRITICAL **: 08:50:36.947: 
g_object_get_is_valid_property: object class 'JsonParser' has no 
property named 'immutable'

(process:3071): GLib-GObject-CRITICAL **: 08:50:36.947: 
g_object_get_is_valid_property: object class 'JsonParser' has no 
property named 'immutable'
      immutable = #f

When not linking to gobject , using no-grafts or running directly from 
guile repl things work as I would expect:
./main
#<<json-parser> 7ff2471f1d20> is an instance of class <json-parser>
Slots are:
      g-inst = #<pointer 0x2bbbe920>
      immutable = #t
--8<---------------cut here---------------end--------------->8---

On 08e0144d2338c8fb51e52e74274554583d0faa69 a similar problem exists:
g-golf depends on the ungrafted out output of hidden glib
but full glib is getting grafted (because of other other outputs)



If I prepend the glib with the single output graft to pkgconfig path and 
rebuild (s.t. my c prgram is linked to the same glib that is used by 
g-golf) things start magically working again.


> I believe what we describe here is yet another symptom of old bug
> <https://issues.guix.gnu.org/48907>, but if we have a first bad commit,
> and if it is the first bad commit for you, too,
> it might help solve it.  Or perhaps this bug can be solved separately if
> really the loading through typelib vs. not through typelib is the cause.
> 

There might be an even bigger issue here?


However regardless of it causing issues I think having 2 different 
grafted glibs (or rather anything) is not really great.

> Regards,
> Florian

Have nice day,
Dariqq




      reply	other threads:[~2024-12-29  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28  8:52 bug#75157: Grafting inconsistency with multiple outputs is causing problems Dariqq
2024-12-29  0:24 ` pelzflorian (Florian Pelz)
2024-12-29  9:30   ` Dariqq [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf6c3172-132b-4290-b023-38a68652411c@posteo.net \
    --to=dariqq@posteo.net \
    --cc=75157@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).