[okl4-developer] Elfweaver Failure (was Re: OKL4 3.0: What about hardware drivers?)
Malcolm Purvis
malcolmp at ok-labs.com
Fri Nov 14 10:01:39 EST 2008
>>>>> "Robert" == Robert Wetzel <robert.wetzel at opensynergy.com> writes:
Robert> After messing around with the source tarball and failing to get
Robert> a proper 2.1-style build done thanks to a failing elfweaver
Robert> (exits with EINVAL in a seek() operation during a modify &
Robert> physical+_entry, looked like the segment-in-section offset
Robert> calculation went bonkers)
That's very strange behaviour for elfweaver. Would it be possible for
you to post more details so that we can hunt down the bug?
In particular, the output of 'readelf -e' on all of your input files,
and the results of:
$ elfweaver --traceback merge -o <image.elf> <weaver.xml>
would be very useful
Malcolm
--
Malcolm Purvis <malcolmp at ok-labs.com>
More information about the Developer
mailing list