From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Qt
Date: Tue, 08 Oct 2013 23:05:04 +0200 [thread overview]
Message-ID: <87mwmjxym7.fsf@gnu.org> (raw)
In-Reply-To: <20131008190520.GA31264@debian> (Andreas Enge's message of "Tue, 8 Oct 2013 21:05:20 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> I just pushed a patch for Qt 5.1.1.
Good, congratulations!
> It builds on my machine, but as there is no application using it so
> far, it may or may not work. Also, the build uses
> sse/sse2/... instructions according to what is available on the
> processor; we might wish to disable all or at least the most advanced
> of them in the long run.
Yes, as for GMP and FFTW. Otherwise, when using substitutes from Hydra,
one could end up with binaries that raise SIGILL on their machine.
> For the time being, I would leave them in, and once we have a qt
> application, check whether it works on different processors.
If it’s a matter of adding the right configure flag, I’d do it before
it bites.
> A next step would be to add qt 4.8.5, as I think this version is still
> used more widely so far.
OK.
Thanks for daring to dive into that!
Ludo’.
next prev parent reply other threads:[~2013-10-08 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 19:05 Qt Andreas Enge
2013-10-08 21:05 ` Ludovic Courtès [this message]
2013-10-10 12:59 ` Qt Andreas Enge
2013-10-10 13:09 ` Qt Ludovic Courtès
2013-10-10 20:00 ` Qt Andreas Enge
2013-10-10 22:19 ` Qt Mark H Weaver
2013-10-31 15:35 ` Qt Andreas Enge
2013-10-12 13:08 ` Qt Andreas Enge
2013-10-12 19:38 ` Qt Ludovic Courtès
2013-10-12 21:25 ` Qt Andreas Enge
2013-10-12 21:39 ` Qt Andreas Enge
2013-10-13 13:54 ` Qt Ludovic Courtès
2013-10-13 14:18 ` Qt Andreas Enge
2013-10-13 20:46 ` Qt Ludovic Courtès
2013-11-11 20:19 ` Qt Andreas Enge
2013-11-11 20:36 ` Qt Ludovic Courtès
2014-09-29 8:06 ` Qt Andreas Enge
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=87mwmjxym7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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.