unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <bavier@cray.com>
Cc: 30879@debbugs.gnu.org
Subject: bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization
Date: Thu, 22 Mar 2018 00:04:06 +0100	[thread overview]
Message-ID: <87r2oddo9l.fsf@gnu.org> (raw)
In-Reply-To: <20180320154302.GL105827@pe06.us.cray.com>

Eric Bavier <bavier@cray.com> skribis:

[...]

> In gnu/system.scm:
>  501: 3 [operating-system-services # # #f]
>  476: 2 [essential-services # # #f]
>  576: 1 [operating-system-etc-service #]
> In gnu/system/nss.scm:
>  217: 0 [name-service-switch->string (# # # # ...)]
>
> gnu/system/nss.scm:217:19: In procedure name-service-switch->string:
> gnu/system/nss.scm:217:19: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): (#<<service> type: #<service-type login ...

This looks like another record issue: the code is accessing the
`services' field instead of the `name-service-switch' field, which is
right next to it.

So it looks like there are still stale .go files somewhere being picked
up.  This time it would mean that nss.go is up-to-date and system.go is
stale, since nss.go assumes an offset for `name-service-switch' that is
+1 compared to that of system.go.

Could you maybe try:

  rm -rf ~/.cache/guile
  make clean-go
  strace -f -o log make

and check in `log' whether .go files outside of the build tree are being
used?

Thanks,
Ludo'.

  reply	other threads:[~2018-03-21 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 15:43 bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization Eric Bavier
2018-03-20 23:12 ` Ludovic Courtès
2018-03-21 15:16   ` Eric Bavier
2018-03-21 21:04     ` Ludovic Courtès
2018-03-21 21:14       ` Eric Bavier
2018-03-21 23:04         ` Ludovic Courtès [this message]
2018-03-22 14:45           ` Eric Bavier
2018-03-22 16:19             ` Ludovic Courtès
2018-03-29 17:06               ` Eric Bavier
2018-05-15  9:20             ` Ludovic Courtès
2018-04-11 18:42 ` Eric Bavier

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=87r2oddo9l.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30879@debbugs.gnu.org \
    --cc=bavier@cray.com \
    /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).