portupgrade, automake14 -> automake19

Giorgos Keramidas keramida at ceid.upatras.gr
Thu Jun 9 16:38:31 GMT 2005

On 2005-06-09 11:27, Dan Nelson <dnelson at allantgroup.com> wrote:
>In the last episode (Jun 09), Giorgos Keramidas said:
>> On 2005-06-09 11:01, Tony Shadwick <tshadwick at goinet.com> wrote:
>> > Could someone give me a quick hint on switching from automake14 to
>> > automake19 using the ports tree without wreaking total havock on
>> > dependencies? :)
>> If you are asking what portupgrade will do with the installed ports,
>> then there's nothing to worry about.  Just run portupgrade -a and it
>> will take care of building the necessary auto* ports too.
>> If you are using automake14 in software you write or build yourself
>> outside of the Ports tree, don't.  For an example of what may go
>> wrong, see the misc/81558 problem report:
> I have never had problems using the numbered auto* ports when building
> programs from CVS trees.  Here's the bootstrap script I use: it also
> works great on Debian and RedHat, which ship numbered auto* binaries as
> well.
> #!/bin/sh -e
> # Run this to update & generate all the automatic things
> #
> # Some OSes (RedHat) symlink 'autoconf' to 2.13 even though a perfectly
> # good 2.5x is available.  If a numbered version is not found, the
> # non-numbered executable will be used, and we hope for the best.

API versioning was introduced in automake-1.6.x, so this may or may not
work as expected.  I usually just update to the latest automake version
available and install a common set of the autotools (i.e. same versions)
with --prefix=/opt/autotools in Linux, BSD and Solaris.  This way all
three systems (which may be used as development workstations by people
here at work), have the same version and autogen.sh doesn't have to

More information about the freebsd-questions mailing list