Date: Thu, 4 Sep 2003 14:00:19 -0400 From: Robert M.Zigweid <rzigweid@securesoftware.com> To: freebsd-ports@freebsd.org Subject: Automake and Autoconf compatability issue. Message-ID: <A56869D4-DF01-11D7-9CC9-00039310484E@securesoftware.com>
next in thread | raw e-mail | index | archive | help
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 intentional. 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. Regards, Robert M. Zigweid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A56869D4-DF01-11D7-9CC9-00039310484E>