From: Vivien Kraus via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 63077@debbugs.gnu.org
Subject: bug#63077: [PATCH] gnu: gnutls: skip examples on mingw.
Date: Mon, 11 Mar 2024 18:47:44 +0100 [thread overview]
Message-ID: <69c6d353db2442006b34eb12fe9428b5f69935d1.camel@planete-kraus.eu> (raw)
In-Reply-To: <878r2s8wqb.fsf@gmail.com>
Hello,
Le vendredi 08 mars 2024 à 18:22 +0100, Simon Tournier a écrit :
> > > + #$@(if (target-mingw?)
> > > + #~((add-after 'unpack 'skip-doc-examples
> > > + ;; The examples in doc do not link to
> > > correct
> > > + ;; gnulib modules.
> > > + (lambda _
> > > + (substitute* "doc/Makefile.in"
> > > + (("SUBDIRS = examples")
> > > + "SUBDIRS =")))))
> > > + #~())
> >
> > Did you report it upstream? Perhaps they'd know how to properly
> > fix it.
>
> Digging all bugs, what about this?
>
> It could be nice if it is fixed upstream. On the other, we could
> also
> apply a fix waiting such fix.
I reported it, and I believe upstream fixed it:
https://gitlab.com/gnutls/gnutls/-/merge_requests/1761/diffs?commit_id=5db0db2e83da54d799f55984dc33039d6b22c933
However it’s difficult to check because libidn2 fails (maybe the more
recent 2.3.7 does not). This libidn2 failure seems to have been
reported here:
https://gitlab.com/libidn/libidn2/-/issues/113
I notice that libidn2 uses its own libunistring instead of the guix’
one, because libunistring is not an input of libidn2. Is this intended
to avoid a cycle?
Best regards,
Vivien
prev parent reply other threads:[~2024-03-11 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 21:26 bug#63077: [PATCH] gnu: gnutls: skip examples on mingw Vivien Kraus via Bug reports for GNU Guix
2024-01-05 18:06 ` Maxim Cournoyer
2024-03-08 17:22 ` Simon Tournier
2024-03-11 17:47 ` Vivien Kraus via Bug reports for GNU Guix [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=69c6d353db2442006b34eb12fe9428b5f69935d1.camel@planete-kraus.eu \
--to=bug-guix@gnu.org \
--cc=63077@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
--cc=zimon.toutoune@gmail.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).