From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 29186@debbugs.gnu.org
Subject: bug#29186: building guile-emacs fails: required libaries not found: libjpeg
Date: Thu, 16 Nov 2017 09:37:53 +0100 [thread overview]
Message-ID: <87a7zmliu6.fsf@gnu.org> (raw)
In-Reply-To: <87bmk4v6p6.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 14 Nov 2017 23:25:25 +0100")
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> Ludovic Courtès writes:
>
>>> Subject: [PATCH] gnu: guile-emacs: Resurrect, fixes #29186.
>>>
>>> * gnu/packages/patches/guile-emacs-fix-configure.patch: New file.
>
>> I’m fine with this patch. I’m a bit concerned about the risk of
>> accumulating patches that should really be in guile-emacs proper,
>> though. IMO it would be better if this patch were pushed to
>> guile-emacs, or if an alternate guile-emacs repo were set up if the
>> current one is inactive. If that’s too cumbersome though, feel free to
>> push this patch!
>
> Meanwhile, I sent this patch 6 days ago to Robin Templeton <robin@igalia.com>.
> They were the most recent committer from where we're pulling. They haven't
> responded yet. Let me know if you know a better address/can we do better?
>
> I can wait a bit more and push if I don't hear anything the coming week.
Yes, that sounds like the best approach.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-11-16 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 22:22 bug#29186: building guile-emacs fails: required libaries not found: libjpeg Jan Nieuwenhuizen
2017-11-07 5:53 ` Mark H Weaver
2017-11-07 17:06 ` Jan Nieuwenhuizen
2017-11-07 19:06 ` Jan Nieuwenhuizen
2017-11-08 10:11 ` Efraim Flashner
2017-11-08 14:44 ` Jan Nieuwenhuizen
2017-11-08 10:12 ` Efraim Flashner
2017-11-08 14:46 ` Jan Nieuwenhuizen
2017-11-14 22:09 ` Ludovic Courtès
2017-11-14 22:25 ` Jan Nieuwenhuizen
2017-11-16 8:37 ` Ludovic Courtès [this message]
2017-11-24 17:25 ` Ludovic Courtès
2017-11-25 19:51 ` Jan Nieuwenhuizen
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=87a7zmliu6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29186@debbugs.gnu.org \
--cc=janneke@gnu.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).