unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add MOSAIK.
Date: Tue, 27 Oct 2015 13:51:08 +0100	[thread overview]
Message-ID: <idj611s79vn.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20151027134249.00f6d318@debian-netbook>


Efraim Flashner <efraim@flashner.co.il> writes:

> On Fri, 23 Oct 2015 10:42:49 +0200
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> wrote:
>
>> > Mosaik fails on all architectures except for x86_64. Should it be disabled
>> > or are there configure flags to make it work elsewhere?  
>> 
>> I think this is caused by ‘includes/linux.inc’, which is unconditionally
>> included by default.
>> 
>> Disabling the line
>> 
>>     include includes/$(BLD_PLATFORM).inc
>> 
>> should be sufficient to fix this.
>> 
>> Alternatively, we could set BLD_PLATFORM (to something other than just
>> “linux” on non-x86_64) and patch “include” to read “-include”, so that
>> it doesn’t cause an error when the file does not exist.
>> 
>> That’s what the attached patch does.
>> 
>
> I ran `./pre-inst-env guix build -s i686-linux mosaik` and the build failed for me.

I can confirm this.  Too bad.  The reason is that “ssw.c” uses macros
from emmintrin.h that are always inlined.  Inlining fails here due to
“target specific option mismatch”.

Does this only happen when cross-compiling or will this also happen if
it’s built natively on i686?

~~ Ricardo

  reply	other threads:[~2015-10-27 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 15:43 [PATCH] Add MOSAIK Ricardo Wurmus
2015-10-19 15:51 ` Ludovic Courtès
2015-10-23  8:02   ` Andreas Enge
2015-10-23  8:42     ` Ricardo Wurmus
2015-10-27 11:42       ` Efraim Flashner
2015-10-27 12:51         ` Ricardo Wurmus [this message]
2015-10-27 15:50           ` 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=idj611s79vn.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=efraim@flashner.co.il \
    --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 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).