From: guy fleury iteriteka <hoonandon@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35878@debbugs.gnu.org
Subject: [bug#35878] [PATCH] gnu: Add chafa.
Date: Sat, 29 Jun 2019 17:23:48 +0200 [thread overview]
Message-ID: <CAOYpmvqaji8ZCJ7uU+QiU5Te7yDFRXLVfUZW-X9SV+U4k1FMCA@mail.gmail.com> (raw)
In-Reply-To: <CAOYpmvpMGLGquoBUfe4ju+4tW0-QmNJz5q-EEPKy0ZN=SXY7=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hello Ludovic,
Sorry for taking so long time.
I discus with the developper upstream. Here is what he tells me:
---------------------------------
Even if it builds SSE support, it will only be used at runtime if the
platform supports it. It uses CPUID internally to detect the CPU
capabilities when run.
-------------------------------
He will also add a note to clarify things in the next release!
Thanks.
Le 29 mai 2019 09:44, "guy fleury iteriteka" <hoonandon@gmail.com> a écrit :
> Hi,
>
> I will try!
> Le 27 mai 2019 16:52, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>
>> Hi,
>>
>> guy fleury iteriteka <hoonandon@gmail.com> skribis:
>>
>> > * gnu/packages/image-viewers.scm(chaffa): New variable.
>>
>> I’d suggest the changes below.
>>
>> Additionally, this code detects SSE4.1 and related instruction set
>> extensions at configuration time. As a result, I think the resulting
>> code may not run on all x86_64 machines.
>>
>> Could you investigate this and see how we can get a generic binary?
>>
>> Thanks,
>> Ludo’.
>>
>>
[-- Attachment #2: Type: text/html, Size: 1744 bytes --]
next prev parent reply other threads:[~2019-06-29 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 9:33 [bug#35878] [PATCH] gnu: Add chafa guy fleury iteriteka
2019-05-27 14:52 ` Ludovic Courtès
2019-05-29 7:44 ` guy fleury iteriteka
2019-06-29 15:23 ` guy fleury iteriteka [this message]
2019-07-02 15:19 ` bug#35878: " Ludovic Courtès
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=CAOYpmvqaji8ZCJ7uU+QiU5Te7yDFRXLVfUZW-X9SV+U4k1FMCA@mail.gmail.com \
--to=hoonandon@gmail.com \
--cc=35878@debbugs.gnu.org \
--cc=ludo@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).