all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 27774@debbugs.gnu.org
Subject: [bug#27774] [PATCH] gnu: add libgeotiff
Date: Sat, 22 Jul 2017 19:18:17 +0530	[thread overview]
Message-ID: <db78d035.AEQANc_cQwwAAAAAAAAAAAPYhrkAAAACwQwAAAAAAAW9WABZc1em@mailjet.com> (raw)
In-Reply-To: <87379o63mn.fsf@fastmail.com>


>> +   (arguments
>> +    `(#:configure-flags
>> +      `( ,(string-append "--with-zlib")
>> +         ,(string-append "--with-jpeg")
>> +         ,(string-append "--with-libtiff="
>> +                         (assoc-ref %build-inputs "libtiff")))

I'm asking this out of ignorance more than anything else. Is this
(assoc-ref %build-inputs "libtiff") call required for "--with-libtiff",
when it is not required for "--with-zlib" and "--with-jpeg"?

Also, can we build this package with libjpeg-turbo, instead of libjpeg?
libjpeg-turbo claims to be faster, and many packages in Arch and
Parabola are built using libjpeg-turbo.

  reply	other threads:[~2017-07-22 13:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 15:50 [bug#27774] [PATCH] gnu: add libgeotiff Björn Höfling
2017-07-22 12:46 ` Marius Bakke
2017-07-22 13:48   ` Arun Isaac [this message]
2017-07-23 11:22   ` Björn Höfling
     [not found]   ` <0c9f175f.AEQANc_cQw0AAAAAAAAAAAPYhrgAAAACwQwAAAAAAAW9WABZc1em@mailjet.com>
2017-07-23 11:27     ` Björn Höfling
2017-07-23 15:36       ` Arun Isaac
2017-09-08 15:53       ` Ludovic Courtès
2017-09-13  6:55         ` Björn Höfling
2017-10-18 21:20           ` Ricardo Wurmus
2017-07-25  6:58 ` Arun Isaac
2018-01-03 16:55 ` [bug#27774] [PATCH 0/1] Add libgeotiff Arun Isaac
2018-01-03 16:56   ` [bug#27774] [PATCH 1/1] gnu: " Arun Isaac
2018-01-27 20:07     ` Björn Höfling
2018-01-03 18:24   ` [bug#27774] [PATCH 0/1] " Leo Famulari
2018-01-04  6:55     ` bug#27774: " Arun Isaac

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=db78d035.AEQANc_cQwwAAAAAAAAAAAPYhrkAAAACwQwAAAAAAAW9WABZc1em@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=27774@debbugs.gnu.org \
    --cc=mbakke@fastmail.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 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.