Automake and Autoconf compatability issue.
rzigweid at securesoftware.com
Thu Sep 4 11:00:25 PDT 2003
I was installing automake, autoconf and family on a clean 5.1 box with
a freshly cvsup'd ports and ran into something that really baffles me.
The binary names of the produced are mangled, and it looks to be
Using automake as an example, the binary produced is automake17. Now,
if you install the package manually this is completely different.
Instead of automake17, the binary is automake-1.7. In addition to
this, the 'automake' script that is installed from the normal package
is not installed at all from the ports. This would not be a problem if
existing packages would compile cleanly.
Why is this cross-platform set of tools, being made less compatable
than the origainal package? This certainly seems to be a step
backwards to me. If there is a good and valid reason for FreeBSD being
made different, I would certainly appreciate knowing what it is.
Robert M. Zigweid
More information about the freebsd-ports