i know, it's masked. Anyway my CFLAGS="-mcpu=athlon-tbird -march=athlon-tbird
-O3 -pipe" had to be changed, removing -march=XX.
Then it emerged.
glad you tested it, to be honest :) it's masked so we can catch this kinda stuff.
Now try to rebuild gnome-vfs (1.x) ... or any other package that actually needs
a working libiconv. You'll most probably find you have a rather strange and
semi-broken system. :/
why do we keep the package around if it break stuff or is this against the
metadistribution idea ?
it did fix some troubles for certain PPC users, and was -supposed- to be a
perfect plugin for the glibc version of iconv... And so we believed, until we
found a few packages that suddenly broke on iconv.h having the wrong format.
it is around as a reference, marked broken in package.mask, and could well be
removed as cruft, although some architectures might just need it since glibc
doesn't support all the things that the extra libiconv supports (though glibc
2.3 will fix this, probably )
Not much use in fixing this one, as most ppl shouldnt use it anyway.
closing, unsupported pack