From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) From: yoann padioleau In-Reply-To: <5f8906f3cd22fe88bbdd8fc8a29e1bd8@mule> Date: Mon, 16 Jan 2017 12:58:09 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <98136872-0209-4836-B147-4926629CD573@gmail.com> <5f8906f3cd22fe88bbdd8fc8a29e1bd8@mule> To: erik quanstrom Cc: 9fans@9fans.net Subject: Re: [9fans] fail to crosscompile Rasperry Pi Miller's kernel Topicbox-Message-UUID: b1d2a36e-ead9-11e9-9d60-3106f5b1d025 Without -f I was able to get something on the screen. The code in libdraw and libmemdraw does not use floats. But I was having weird failures in malloc. I updated my kencc fork to the latest version and now everything works! The problem apparently was more related to 5c than 5l. I updated 5l to support -f but I still had the problem. After updating 5c then everything worked. > On Jan 15, 2017, at 4:11 PM, erik quanstrom = wrote: >=20 >> Does any of you have any idea what could be the cause of the problem? >> The linker 5l in kencc does not support the -f linking option, but I = think none >> of the code in pool.c or libmemdraw use float/double at this point. >> Is there some important patches to 5l or 5c I am missing in kencc/?=20= >=20 > i think your source is out-of-sync: >=20 > -f (5l only) Generate VFP hardware floating-point > instructions. Without this option, 5l generates > arm7500 floating-point instructions which are emu- > lated in the kernel. >=20 > i would imagine that your machine may have booted (the kernel does not = use floating point), > but you can't see the screen. if you set up a cpu server, there's a = good chance it will be > accessable. >=20 > - erik