all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "Nguyễn Gia Phong" <cnx@loang.net>
Cc: 66699@debbugs.gnu.org
Subject: bug#66699: zig: fail to link SDL2
Date: Sat, 11 Nov 2023 13:23:33 +0000	[thread overview]
Message-ID: <VogPLQH6oApxEQbHyfSSxYEip9tSK6qWCBObn_SEM4sLgh_BTC8l3MUACnrynd8-zc4QBmZl-31mLSXtfr_goHS9eG5bi7nUtEzCrO4bXf4=@elenq.tech> (raw)
In-Reply-To: <WpV4q86pbeIZROkO_ywSnbkSq4t2_A4QIyV0iLfIC2B0BsM738sOk3HC6BJspkrHljtZjU-oe8jsB_Qq4pKdNGNzn8gcdyoh3n4iS1Y6X_U=@elenq.tech>

Hi,

I tracked this pretty far:

This is a related issue that mentions the `mepo` package:
https://github.com/ziglang/zig/issues/12170

And I realized the problem comes from `pkg-config`. It's telling zig to use the static library first.
Removing `pkg-config` from the `native-inputs` in your proposed package make it build but the `runpath` validation phase fails.

I'm not sure about what to do now.

In the issue the people working on freebsd-ports mention they did this:
https://github.com/freebsd/freebsd-ports/blob/16ada4d8d14a222bd92c4bf332d28b7c604af457/astro/mepo/Makefile#L31
But I don't know if we can replicate that.

I'll keep researching on this a little bit further.

Best,
Ekaitz




      reply	other threads:[~2023-11-11 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  7:34 bug#66699: zig: fail to link SDL2 Nguyễn Gia Phong via Bug reports for GNU Guix
2023-11-01 20:52 ` Ekaitz Zarraga
     [not found]   ` <CWUUZFWJPNL0.20MWDY132FY6E@guix>
2023-11-10  9:57     ` Ekaitz Zarraga
2023-11-11 13:23       ` Ekaitz Zarraga [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

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

  git send-email \
    --in-reply-to='VogPLQH6oApxEQbHyfSSxYEip9tSK6qWCBObn_SEM4sLgh_BTC8l3MUACnrynd8-zc4QBmZl-31mLSXtfr_goHS9eG5bi7nUtEzCrO4bXf4=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=66699@debbugs.gnu.org \
    --cc=cnx@loang.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.