In an environment with slibtool enabled it forces GNU libtool by hardcoding it in a generated ltcompile script. Reproducible: Always
How badly do you want this? Not only is "libtool" echoed into ltcompile, it's also hard-coded in one (*.c) source file. This isn't an autotools project, so rlibtool doesn't work. And while most libraries are shared, there's ONE lib that needs to be static. So if you are guessing what to put in LIBTOOL, it's a headache. The ebuild depends on GNU libtool, so while it will use the "wrong" tool, it should still build and function on a system where slibtool is used globally.
I don't use this package and only reported it because its a problem concerning slibtool. This was when I was actively working on slibtool integration in Gentoo which unfortunately has been stalled for reasons entirely out of my hands...
