Illegal instruction on m68k nommu (solved. C and C++ now work.)
Lennart Sorensen
lsorense at csclub.uwaterloo.ca
Wed Apr 22 00:20:14 UTC 2009
On Wed, Apr 22, 2009 at 09:01:48AM +1000, David McCullough wrote:
> Originally we had thought about having ld-elf2flt remove the mostly
> likely offending .o's from the link line so that elf2flt's CTOR/DTOR
> support would always work whether the toolchain included working
> CTOR/DTOR support or not.
>
> Somehow this never eventuated.
>
> We could add a '-old-ctor-dtor-support' option to ld-elf2flt to enable
> adding the support in and mark it in elf2flt.ld like SINGLE_LINK or the
> various *DAT options.
>
> Yep, and I would be happy with a configure option to enable the old
> behaviour and have the new behaviour be the default.
>
> Really, most solutions I can think of would be ok. How different is
> the bfin version ?
Well diff -ruN seems to come to 8000 lines or so, which isn't actually
that much given there is some changelog for the bfin, the zlib code
has been split out to seperate files, then there are bug fixes for the
dtor/ctor stuff which is pretty small, some bug fixes for c++ handling
with 4.3, lots of typo fixes in comments and such, general cleanup in
the handling of the different architectures and how include files are
handled, the .ld files has become .ld.in and gets configure handling it
seems, and quite a bit of bfin bug fixes it seems.
> Thats fair enough, I don't expect it to be tested, as long as it
> passes the "looks ok test" it's usually close enough,
--
Len Sorensen
More information about the uClibc
mailing list