On Thu, Aug 04, 2005 at 10:17:03AM -0600, Li-Ta Lo wrote:
On Thu, 2005-08-04 at 16:59 +0100, Jonathan McDowell wrote:
I've been playing about with trying to autobuild all the available targets, to catch regressions, or more relevantly to convince myself that when things are broken it's not just EPIA-M that's affected.
http://the.earth.li/~noodles/lb/
is what I've got so far.
1987/ is pre gcc4 fix, so 1989/ is more interesting.
All 12 Tyan boards built, leaving 18 that didn't.
amd-quartet, amd-solo, arima-hdama & ibm-e325 all look like they'd build with elf payloads (the directories they look for the payload in aren't convenient for an enclosed build - does anyone object if I clean this up?).
Do you mean I left "payload /home/ollie/xxxx" there ?
Yes. The attached patch cleans up the payload bits (put them in targets/<vendor>/payloads like the Tyan boards do) and also fixes island-aruma to put itself in the same format of directory as everything else. With it I get PASSes for amd-quartet, amd-solo, arima-hdama, ibm-e325 & island-aruma, in addition to the Tyan boards. That brings us up to 17 images building fine and 13 failing.
embeddedplanet-ep405pc & motorola-sandpoint are both PPC so won't build anyway.
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and newisys-khepri all failed to have a config file that buildtarget was happy with.
totalimpac-briq should be PPC. technologic-ts5300 is never finished.
buildtarget can't even parse their config files, so my test rig never even tries to compile them.
via-epia, digitallogic-adl855pc, digitallogic-msm586seg, eaglelion-5bcm & emulation-qemu-i386 all have problems with udelay.
I have a quick fix to the udelay but I am not sure it is the correct way to do it.
Can you show me your quick fix even to give me an idea of where the issue is?
J.