all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Tomás Ortín" <tomasortin@mailbox.org>
Cc: 43781@debbugs.gnu.org
Subject: [bug#43781] [PATCH 2/2] gnu: Add cgoban
Date: Wed, 18 Nov 2020 23:06:18 +0100	[thread overview]
Message-ID: <87eekqjp5x.fsf@gnu.org> (raw)
In-Reply-To: <87v9exb72e.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 26 Oct 2020 11:44:09 +0100")

Hi Tomás,

A friendly reminder.  :-)

  https://issues.guix.gnu.org/43781

Ludo’.

Ludovic Courtès <ludo@gnu.org> skribis:

> Hi Tomás,
>
> (Please keep the bug Cc’d.)
>
> Tomás Ortín <tomasortin@mailbox.org> skribis:
>
>> About the patch: it's taken from the Gentoo package. I first tried packaging cgoban without any package and it consistently failed at configure phase, no matter the flags I passed. I decided to check the Gentoo package to see how they built it, as I have used cgoban in that distribution before and works well, and saw they just added this patch. Tried adding it, and it works. But I won't pretend to understand why.
>
> I tested it: it builds just fine without the ‘configure.in’ patch.  :-)
>
> Could you send an updated patch?
>
> Thanks,
> Ludo’.




  reply	other threads:[~2020-11-18 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03 17:50 [bug#43781] [PATCH 0/2] gnu: Add cgoban Tomás Ortín Fernández via Guix-patches via
2020-10-03 19:05 ` [bug#43781] [PATCH 2/2] " Tomás Ortín Fernández via Guix-patches via
2020-10-22 14:55   ` Ludovic Courtès
2020-10-22 15:07     ` Tomás Ortín via Guix-patches
2020-10-26 10:44       ` Ludovic Courtès
2020-11-18 22:06         ` Ludovic Courtès [this message]
2020-11-26  8:56 ` [bug#43781] (no subject) Tomás Ortín Fernández via Guix-patches via
2020-11-29 19:19   ` bug#43781: " Efraim Flashner

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=87eekqjp5x.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43781@debbugs.gnu.org \
    --cc=tomasortin@mailbox.org \
    /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.