From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: rennes@openmailbox.org, 22049@debbugs.gnu.org
Subject: bug#22049: libreoffice compile error
Date: Tue, 01 Mar 2016 14:36:24 +0100 [thread overview]
Message-ID: <878u22pbfr.fsf@gnu.org> (raw)
In-Reply-To: <20160229083723.GA18766@jasmine> (Leo Famulari's message of "Mon, 29 Feb 2016 03:37:23 -0500")
Leo Famulari <leo@famulari.name> skribis:
> From bf1f2a1c3621ba93ec99711ec78a79663acb6e82 Mon Sep 17 00:00:00 2001
> Message-Id: <bf1f2a1c3621ba93ec99711ec78a79663acb6e82.1456734966.git.leo@famulari.name>
> From: Leo Famulari <leo@famulari.name>
> Date: Mon, 29 Feb 2016 02:23:43 -0500
> Subject: [PATCH 1/1] gnu: ilmbase: Add patches to fix build on i686.
>
> Fixes <http://bugs.gnu.org/22049>.
>
> * gnu/packages/patches/ilmbase-testBox.patch,
> gnu/packages/patches/ilmbase-testBoxAlgo.patch: New files.
> * gnu-system.am (dist_patch_DATA): Add them.
> * gnu/packages/graphics.scm (ilmbase)[native-inputs]: Add patch/testBox
> and patch/testBoxAlgo.
> [arguments]: Add 'patch-for-i686' phase.
Cool!
I think it’d be reasonable to squash both patches in one file, and to
apply it unconditionally. WDYT?
So I gather upgrading to IlmBase 2.0.1 is not an option?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-03-01 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 3:42 bug#22049: libreoffice compile error rennes
2015-11-29 15:02 ` Ludovic Courtès
2015-11-29 16:50 ` rennes
2015-11-30 19:56 ` Leo Famulari
2015-11-30 20:14 ` Ludovic Courtès
2015-12-01 5:58 ` Leo Famulari
2015-12-03 20:01 ` Leo Famulari
2015-12-04 11:59 ` Ludovic Courtès
2016-02-28 18:06 ` Ludovic Courtès
2016-02-29 8:35 ` Leo Famulari
2016-02-29 8:37 ` Leo Famulari
2016-03-01 13:36 ` Ludovic Courtès [this message]
2016-03-01 17:24 ` Leo Famulari
2016-03-01 18:01 ` Leo Famulari
2016-03-01 20:36 ` Ludovic Courtès
2016-03-02 0:20 ` Leo Famulari
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=878u22pbfr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22049@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=rennes@openmailbox.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 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).