Re: portupgrade, automake14 -> automake19
On 2005-06-09 11:27, Dan Nelson <[EMAIL PROTECTED]> wrote: >In the last episode (Jun 09), Giorgos Keramidas said: >> On 2005-06-09 11:01, Tony Shadwick <[EMAIL PROTECTED]> 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 guess. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, automake14 -> automake19
In the last episode (Jun 09), Giorgos Keramidas said: > On 2005-06-09 11:01, Tony Shadwick <[EMAIL PROTECTED]> 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. AC= for i in 259 -2.59 258 -2.58 257 -2.57 256 -2.56 255 -2.55 2.55 254 -2.54 2.54 253 -2.53 2.53 ; do if type autoconf$i >/dev/null 2>&1 ; then AC=$i ; echo detected autoconf$AC ; break fi done AM= for i in 19 -1.9 18 -1.8 17 -1.7 1.6 -1.6 15 -1.5 ; do if type automake$i >/dev/null 2>&1 ; then AM=$i ; echo detected automake$AM ; break fi done # export these because all 5 need to know the exact name of the other ones AUTOCONF=autoconf$AC ; export AUTOCONF AUTOHEADER=autoheader$AC ; export AUTOHEADER AUTOM4TE=autom4te$AC ; export AUTOM4TE ACLOCAL=aclocal$AM ; export ACLOCAL AUTOMAKE=automake$AM ; export AUTOMAKE rm -rf autom4te* $ACLOCAL -I . $AUTOHEADER $AUTOMAKE --add-missing $AUTOCONF -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, automake14 -> automake19
On 2005-06-09 11:14, Tony Shadwick <[EMAIL PROTECTED]> wrote: > No, I was referring to the fact that I ran portupgrade on automake14 > and it complains and says that it is deprecated and strongly > encourages using automake19 instead. I was curious if I just deleted > the automake14 port and installed automake19 if I would be wreaking > havoc on my dependencies in other ports. That's not a good idea either. The autotools are infamous for their tendency to be very incompatible with previous releases of the same software. The best thing to do would be to contact the respective port maintainers and see if they have plans to test with automake19. They may have already investigated the transition to automake19, but stopped for: - lack of time - waiting for a newer version of the distfile any time now - etc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, automake14 -> automake19
No, I was referring to the fact that I ran portupgrade on automake14 and it complains and says that it is deprecated and strongly encourages using automake19 instead. I was curious if I just deleted the automake14 port and installed automake19 if I would be wreaking havoc on my dependencies in other ports. On Thu, 9 Jun 2005, Giorgos Keramidas wrote: On 2005-06-09 11:01, Tony Shadwick <[EMAIL PROTECTED]> 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: http://www.freebsd.org/cgi/query-pr.cgi?pr=81558 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, automake14 -> automake19
On 2005-06-09 11:01, Tony Shadwick <[EMAIL PROTECTED]> 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: http://www.freebsd.org/cgi/query-pr.cgi?pr=81558 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, automake14 -> automake19
In the last episode (Jun 09), Tony Shadwick said: > Could someone give me a quick hint on switching from automake14 to > automake19 using the ports tree without wreaking total havock on > dependencies? :) The numbered auto* ports install into separate directories, so there is nothing to be done. Install the automake19 port and start running "automake19" instead of "automake14". Both ports will live happily side by side. If you are talking about updating a port to use a different version of automake, just edit the WANT_AUTOMAKE_VER line in the Makefile. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade, automake14 -> automake19
Could someone give me a quick hint on switching from automake14 to automake19 using the ports tree without wreaking total havock on dependencies? :) Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
