mduft, With the most recent libtool being out of p.mask, freetype needs to be elibtoolized to configure on x86-linux. Can you please evaluate r19104 and see what the current status is with interix and this package? If I revert r19104, this package will build fine (with libtool-2). If I downgrade to libtool-1.5* then the current revision will build fine. I'm not sure what needs to be done. ?? Thanks!
urgh... new libtool? i'm far from 2.2, so i can't look at that one, until i get me a shiny new prefix... in general elibtoolize is not enough on interix, i need a full eautoreconf at least if the included libtool is older than 1.5.22. if the "${BASH}" ./autogen.sh || die "autogen.sh failed" fails on freetype with libtool 2.2, than it is simply not libtool 2.2 ready. isn't there a tracker bug for this?
(In reply to comment #1) > urgh... new libtool? i'm far from 2.2, so i can't look at that one, until i get > me a shiny new prefix... > > in general elibtoolize is not enough on interix, i need a full eautoreconf at > least if the included libtool is older than 1.5.22. > > if the "${BASH}" ./autogen.sh || die "autogen.sh failed" fails on freetype with > libtool 2.2, than it is simply not libtool 2.2 ready. isn't there a tracker bug > for this? It isn't libtool 2.2 ready then, or perhaps bug 220879 affects this one..? I'm not sure and not around my prefix to test it ATM.
I've no hard feeling against masking libtool 2.{2,4} again. Upstream thought it should work (but they don't bootstrap so often I guess), I'm affraid that this other bug by this ieee guy is also a libtool related bug, though I'm not sure what stage he is (I think post emerge --sync).
mask++; i think libiconv has problems too, not sure yet though if its libtool-2 related.
I just masked it because of the other bug where it appeared to be the culprit. I think the interix patch still needs to be fixed for libtool-2.2, in the meanwhile we can close this bug as we worked around it?
there is no interix patch.... the interix thing here is the eautoreconf which i needed and now - or course - triggeres libtool-2 problems...
The package in question works with libtool-1.5.* so if libtool-2.2 is masked then this can bug can be closed.
closeit!
