From: ludo@gnu.org (Ludovic Courtès)
To: taylanbayirli@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] Mupen64Plus
Date: Thu, 12 Nov 2015 17:15:41 +0100 [thread overview]
Message-ID: <87r3jvw5w2.fsf@gnu.org> (raw)
In-Reply-To: <8737wbtgz7.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Thu, 12 Nov 2015 15:44:28 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> On hydra Mupen64plus-core fails to build on arm and mips.
>>
>> Mips failure message:
>> starting phase `build'
>> Makefile:127: *** CPU type "mips64" not supported. Please file bug report at 'http://code.google.com/p/mupen64plus/issues'. Stop.
>> phase `build' failed after 0.3 seconds
>>
>> Arm failure message:
>> starting phase `build'
>> Makefile:116: Architecture "armv7l" not officially supported.'
[...]
> I don't have any ARM machine on which I could investigate this issue,
> so for now I'll just mark Mupen as only for i686 and x86_64.
When adding a ‘supported-systems’ field, it’s best to add a comment
above stating what evidence we have that some systems are not supported
(in that case, that the top-level Makefile has a pre-defined list of
supported architectures.)
This helps others and your future self ;-) find out why this restriction
is there and whether it still applies.
Could you add such a comment?
TIA,
Ludo’.
next prev parent reply other threads:[~2015-11-12 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 22:04 [PATCHES] Mupen64Plus Taylan Ulrich Bayırlı/Kammer
2015-11-03 5:13 ` Leo Famulari
2015-11-03 15:03 ` Eric Bavier
2015-11-03 15:49 ` Taylan Ulrich Bayırlı/Kammer
2015-11-06 16:46 ` Taylan Ulrich Bayırlı/Kammer
2015-11-12 12:49 ` Efraim Flashner
2015-11-12 14:44 ` Taylan Ulrich Bayırlı/Kammer
2015-11-12 16:15 ` Ludovic Courtès [this message]
2015-11-12 16:28 ` Taylan Ulrich Bayırlı/Kammer
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=87r3jvw5w2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.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.