From: Eric Bavier <ericbavier@openmailbox.org>
To: Leo Famulari <leo@famulari.name>
Cc: 24290@debbugs.gnu.org
Subject: bug#24290: [PATCH 1/1] gnu: imagemagick: Don't build with processor-specific optimizations.
Date: Mon, 22 Aug 2016 23:53:52 -0500 [thread overview]
Message-ID: <20160822235352.53074b86@openmailbox.org> (raw)
In-Reply-To: <a28d79f86285db9d6c737aad86cdb5db42420097.1471919858.git.leo@famulari.name>
On Mon, 22 Aug 2016 22:40:02 -0400
Leo Famulari <leo@famulari.name> wrote:
> * gnu/packages/imagemagick.scm (imagemagick)[arguments]: Pass --without-gcc-arch
> to #:configure-flags.
> ---
> gnu/packages/imagemagick.scm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gnu/packages/imagemagick.scm b/gnu/packages/imagemagick.scm
> index b7054c8..a554b73 100644
> --- a/gnu/packages/imagemagick.scm
> +++ b/gnu/packages/imagemagick.scm
> @@ -51,7 +51,7 @@
> "00arcvyhsy9i5gp3b0lhfvs04qwhxpmq0bfsv4ipllinb6mjgxf5"))))
> (build-system gnu-build-system)
> (arguments
> - `(#:configure-flags '("--with-frozenpaths")
> + `(#:configure-flags '("--with-frozenpaths" "--without-gcc-arch")
> #:phases (modify-phases %standard-phases
> (add-before
> 'build 'pre-build
This seems like a good solution to me. We commonly target SSE2 as a
lcd. Can we make sure that ImageMagick compiles for SSE2 at least?
`~Eric
next prev parent reply other threads:[~2016-08-23 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 2:00 bug#24290: ImageMagick optimized for the host processor type on x86_64 and i686 Leo Famulari
2016-08-23 2:40 ` bug#24290: [PATCH 0/1] Potential solution Leo Famulari
2016-08-23 2:40 ` bug#24290: [PATCH 1/1] gnu: imagemagick: Don't build with processor-specific optimizations Leo Famulari
2016-08-23 4:53 ` Eric Bavier [this message]
2016-08-23 16:45 ` Leo Famulari
2016-08-24 20:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160822235352.53074b86@openmailbox.org \
--to=ericbavier@openmailbox.org \
--cc=24290@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.