[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] XaAES working ?
- To: mint@lists.fishpool.fi
- Subject: Re: [MiNT] XaAES working ?
- From: Vincent Rivière <vincent.riviere@freesbee.fr>
- Date: Wed, 30 Mar 2011 11:01:02 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LswfgoxqW7+NwDMTY8emmqXV7nRgMQG4hesKYwJFlPs=; b=bq+Jb6BFIxpk/s7VohyiTGxpIRRGzT1bBNaUcc3m03L0o9q6H3Md+1BU+gG9GfUC92 8MJfeggFdbLzDqerHMTLq+khYCYAzoBR8xqMIVGHvGhY9ZItDiULFIgsE0tc2t3d3Apm jvbhP1gv9aGM/LuROM7vMi7oqCzpDJefoRdW4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=K8MUrXYbWzqsf7wv5LsQtMTV3XagMPuPemX/bK4yvk1LcUfAAUuriAV4cxID7d2v/L e1OuQ8Si+l7F/uoqEIPgLkX2l3J2hh7nUFY64buYvO8NTo+Kn3I8RB7RWopucObQe2pA mv+o8DBi+S25OVho1GpVYE0Q2p+DOkoHVMgzE=
- In-reply-to: <1301469442.1988.24.camel@sterkenils>
- List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
- List-id: <mint.lists.fishpool.fi>
- List-owner: <mailto:tjhukkan@fishpool.fi>
- List-post: <mailto:mint@lists.fishpool.fi>
- List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
- List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
- References: <741725.649076642-sendEmail@descaro> <1301469442.1988.24.camel@sterkenils>
- Sender: mint-bounce@lists.fishpool.fi
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
Jo Even Skarstein wrote:
I get this on my Firebee with a trunk XaAES from a few days ago and the
kernel I checked out yesterday. The XaAES worked fine with previous
kernels.
I have not tried XaAES on FireTOS/FireBee yet.
However I got that error on ARAnyM 2 days ago.
I hope I have not introduced some regression with my last patches.
Probably not, since my build from yesterday worked perfectly on ARAnyM...
Alan, I don't know which compiler you use for your daily builds. I have
reintroduced the usage of the m68020-60/mshort multilib in
gcc-4.4.3-mint-20100123 and later. If your GCC is older, -lgem will link
the wrong GemLib. The -lgem16 trick still have to be used in that case.
However we have absolutely no clue the problem comes from the GemLib.
Also, better traces from XaAES would be welcome when something crashes.
--
Vincent Rivière