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 10:03:18 +0200
Message-ID: <20131001080318.GW1965@vicerveza.homeunix.net>
References: <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>
	<20131001070942.GV1965@vicerveza.homeunix.net>
	<87li2dv3bz.fsf@karetnikov.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37516)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQuvb-0000kx-KY
	for guix-devel@gnu.org; Tue, 01 Oct 2013 04:03:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <viric@viric.name>) id 1VQuvU-0002kj-8v
	for guix-devel@gnu.org; Tue, 01 Oct 2013 04:03:31 -0400
Content-Disposition: inline
In-Reply-To: <87li2dv3bz.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 11:48:48AM +0400, Nikita Karetnikov wrote:
> > 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 recent
> > kernel, first?
> 
> Linux-libre 3.5.3 from gNewSense.  Which version would you recommend?
> 
> Also, I remember that it was necessary to disable CONFIG_EXT4_FS and
> CONFIG_EXT4_USE_FOR_EXT23.  Is it fixed now?  Do you have a working
> config for Linux-libre?

In fact I was reluctant to raise again the ext4 topic ;) But I think 3.5.3 has a
broken readdir() syscall in ext4. I think it's not a problem of kernel options
active. You simply have to avoid using ext4 (or even ext3, I can't recall).