From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?iso-8859-1?Q?Llu=EDs?= Batlle i Rossell <viric@viric.name>
Subject: Re: MIPS64/N64 support
Date: Tue, 1 Oct 2013 09:09:42 +0200
Message-ID: <20131001070942.GV1965@vicerveza.homeunix.net>
References: <87k3iqa71l.fsf@karetnikov.org> <87k3iqhrh5.fsf@gnu.org>
	<877ge3c8lf.fsf@karetnikov.org> <874n96qed3.fsf@gnu.org>
	<878uyfiwr1.fsf@karetnikov.org> <87siwniwka.fsf@gnu.org>
	<8738onkyi9.fsf@karetnikov.org> <87bo3asfx6.fsf@karetnikov.org>
	<87fvsmgtsm.fsf@gnu.org> <87mwmuhtb3.fsf@karetnikov.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45729)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQu5k-00085X-PS
	for guix-devel@gnu.org; Tue, 01 Oct 2013 03:10:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQu5d-0004wP-Rk
	for guix-devel@gnu.org; Tue, 01 Oct 2013 03:09:56 -0400
Content-Disposition: inline
In-Reply-To: <87mwmuhtb3.fsf@karetnikov.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org

On Tue, Oct 01, 2013 at 01:51:28AM +0400, Nikita Karetnikov wrote:
> > Could you try running the statically-linked bash from
> > =E2=80=98static-binaries.tar.xz=E2=80=99 and see if the same error oc=
curs?  Perhaps
> > strace it so we can see where that error comes from.
>=20
> I don=E2=80=99t see anything similar.
>=20
> > Looking at
> > <http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/syscalls/?cvsroot=3D=
src>,
> > syscalls have different numbers in n64 vs. n32.  So I suppose the ker=
nel
> > needs to be compiled to support the n64 ABI?
>=20
> So, should I try this, or do you have other ideas?

Sure the kernel, needs to have n64 support enabled, to run n64 binaries. =
I
imagine it would be detected at ELF header though, and not simply getting
failing syscalls.

I'm sorry, but I don't know what problem is that. Are you running a recen=
t
kernel, first?