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.
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
Do you mean I left "payload /home/ollie/xxxx" there ?
embeddedplanet-ep405pc & motorola-sandpoint are
both PPC so won't build
via-epia-m, Iwill-dk8s2, totalimpact-briq, technologic-ts5300 and
newisys-khepri all failed to have a config file that buildtarget was
totalimpac-briq should be PPC. technologic-ts5300 is never finished.
& 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.
amd-serenade has an error I don't quite
island-aruma has a non-standard build dir so it doesn't get picked up.
Again this is something I'll fix up in the config file unless I hear
I've got my EPIA-M code to the point where it's hitting the udelay
problem various other ports have. I haven't quite tracked down what
other change has made this happen though. EPIA was certainly building a
month or so ago from the tree when I tried it.
Li-Ta Lo <ollie(a)lanl.gov>
Los Alamos National Lab