Re: Upgrading autoconf
On Fri, Oct 1, 2010 at 5:11 PM, Daniel Bye < freebsd-questi...@slightlystrange.org> wrote: > On Fri, Oct 01, 2010 at 03:02:10PM +0300, Odhiambo Washington wrote: > > > > Will migrate it to 8.x soon, by doing a new installation and > migrating. > > > > > > > > Or should I wait for FreeBSD-9 ?? > > > > > > I'd go for 8.x as soon as possible. It'll be a while before 9 is ready > for > > > production, and when it is released, it should be pretty straight > forward > > > to > > > upgrade from 8.x using the standard buildworld cycle, provided your > setup > > > isn't too outlandish! > > > > > > > > Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and > then > > migrate services?:-) > > Since you're crossing two major versions, I'd go for a clean install. You > could conceivably go straight to 8 using buildworld, but I think the safest > and simplest course of action is to take good backups and start from > scratch. As for going from 8.x to 9.x, that should be pretty easy, if, as I > said, your setup isn't too far from the default. But of course, only you > can > make that call. > > My servers are pretty easy to migrate. It's just a case of a fresh install, install the applications, migrate the configs and data/databases since I try and keep up to date with the application versions as much as possible. The only thing that changes significantly is the base system. I will go for a clean install. Sometimes back I saw some instructions to upgrade upwards (6.x ->7.x ->8.x) but I cannot find them anymore, although the only time to do those are when the system is in the room next:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading autoconf
On Fri, Oct 01, 2010 at 03:02:10PM +0300, Odhiambo Washington wrote: > > > Will migrate it to 8.x soon, by doing a new installation and migrating. > > > > > > Or should I wait for FreeBSD-9 ?? > > > > I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for > > production, and when it is released, it should be pretty straight forward > > to > > upgrade from 8.x using the standard buildworld cycle, provided your setup > > isn't too outlandish! > > > > > Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and then > migrate services?:-) Since you're crossing two major versions, I'd go for a clean install. You could conceivably go straight to 8 using buildworld, but I think the safest and simplest course of action is to take good backups and start from scratch. As for going from 8.x to 9.x, that should be pretty easy, if, as I said, your setup isn't too far from the default. But of course, only you can make that call. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpH6dN2QDWf5.pgp Description: PGP signature
Re: Upgrading autoconf
On Fri, Oct 1, 2010 at 12:36 PM, Daniel Bye < freebsd-questi...@slightlystrange.org> wrote: > On Fri, Oct 01, 2010 at 12:13:28PM +0300, Odhiambo Washington wrote: > > On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye < > > freebsd-questi...@slightlystrange.org> wrote: > > > > > On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: > > > > I am trying this out: > > > > > > > > #portupgrade -f 'autoconf*' 'automake*' > > > > > > Try upgrading the failing ports by hand. portupgrade tends to suppress > full > > > error output, making it difficult to ascertain exactly what's gone > wrong. > > > > > > Alternatively, I would be tempted to just uninstall autoconf* and > > > automake*, > > > since they will get pulled in as dependencies whenever you come to > build > > > another port that requires them. > > > > > > > > Hi Dan, > > > > Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, > > everything now compiled fine. The box is running FreeBSD 6.4-STABLE which > I > > was ashamed to mention:-) > > Glad you fixed it! > > > Will migrate it to 8.x soon, by doing a new installation and migrating. > > > > Or should I wait for FreeBSD-9 ?? > > I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for > production, and when it is released, it should be pretty straight forward > to > upgrade from 8.x using the standard buildworld cycle, provided your setup > isn't too outlandish! > > Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and then migrate services?:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading autoconf
On Fri, 1 Oct 2010 12:13:28 +0300 Odhiambo Washington articulated: > Or should I wait for FreeBSD-9 ?? Or Freebsd-10.x perhaps! -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading autoconf
On Fri, Oct 01, 2010 at 12:13:28PM +0300, Odhiambo Washington wrote: > On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye < > freebsd-questi...@slightlystrange.org> wrote: > > > On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: > > > I am trying this out: > > > > > > #portupgrade -f 'autoconf*' 'automake*' > > > > Try upgrading the failing ports by hand. portupgrade tends to suppress full > > error output, making it difficult to ascertain exactly what's gone wrong. > > > > Alternatively, I would be tempted to just uninstall autoconf* and > > automake*, > > since they will get pulled in as dependencies whenever you come to build > > another port that requires them. > > > > > Hi Dan, > > Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, > everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I > was ashamed to mention:-) Glad you fixed it! > Will migrate it to 8.x soon, by doing a new installation and migrating. > > Or should I wait for FreeBSD-9 ?? I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for production, and when it is released, it should be pretty straight forward to upgrade from 8.x using the standard buildworld cycle, provided your setup isn't too outlandish! Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp7nxygb4Lhw.pgp Description: PGP signature
Re: Upgrading autoconf
On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye < freebsd-questi...@slightlystrange.org> wrote: > On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: > > I am trying this out: > > > > #portupgrade -f 'autoconf*' 'automake*' > > Try upgrading the failing ports by hand. portupgrade tends to suppress full > error output, making it difficult to ascertain exactly what's gone wrong. > > Alternatively, I would be tempted to just uninstall autoconf* and > automake*, > since they will get pulled in as dependencies whenever you come to build > another port that requires them. > > Hi Dan, Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I was ashamed to mention:-) Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading autoconf
On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: > I am trying this out: > > #portupgrade -f 'autoconf*' 'automake*' Try upgrading the failing ports by hand. portupgrade tends to suppress full error output, making it difficult to ascertain exactly what's gone wrong. Alternatively, I would be tempted to just uninstall autoconf* and automake*, since they will get pulled in as dependencies whenever you come to build another port that requires them. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpR3Lo2vM9Gt.pgp Description: PGP signature
Upgrading autoconf
I am trying this out:
#portupgrade -f 'autoconf*' 'automake*'
and I end up with:
===> Building for autoconf-2.67
gmake all-recursive
gmake[1]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67'
Making all in bin
gmake[2]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/bin'
rm -f autom4te autom4te.tmp
srcdir=''; \
test -f ./autom4te.in || srcdir=./; \
sed -e 's|@she...@]|/bin/sh|g' -e 's|@pe...@]|/usr/bin/perl|g' -e
's|@perl_flo...@]|yes|g' -e 's|@bind...@]|/usr/local/bin|g' -e 's|@pk
gdatad...@]|/usr/local/share/autoconf-2.67|g' -e 's|@pref...@]|/usr/local|g'
-e 's|@autoconf-na...@]|'`echo autoconf | sed 's&$&-2.67&'`'|g' -e '
s|@autoheader-na...@]|'`echo autoheader | sed 's&$&-2.67&'`'|g' -e
's|@autom4te-na...@]|'`echo autom4te | sed 's&$&-2.67&'`'|g' -e
's|@m...@]|/usr
/local/bin/gm4|g' -e 's|@m4_debugfi...@]|--error-output|g' -e
's|@m4_g...@]||g' -e 's|@a...@]|/usr/bin/awk|g' -e 's|@release_ye...@]|'`sed
's/^\(
[0-9][0-9][0-9][0-9]\).*/\1/;q' ../ChangeLog`'|g' -e 's|@versi...@]|2.67|g'
-e 's|@package_na...@]|GNU Autoconf|g' -e 's|@configure_inp...@]|Gene
rated from autom4te.in; do not edit by hand.|g'
${srcdir}autom4te.in>autom4te.tmp
chmod +x autom4te.tmp
chmod a-w autom4te.tmp
mv autom4te.tmp autom4te
cd ../lib && gmake autom4te.cfg
gmake[3]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib'
rm -f autom4te.cfg autom4te.tmp
sed -e 's|@she...@]|/bin/sh|g' -e 's|@pe...@]|/usr/bin/perl|g' -e
's|@bind...@]|/usr/local/bin|g' -e
's|@pkgdatad...@]|/usr/local/share/autoconf-
2.67|g' -e 's|@pref...@]|/usr/local|g' -e 's|@autoconf-na...@]|'`echo
autoconf | sed 's&$&-2.67&'`'|g' -e 's|@autoheader-na...@]|'`echo autoheade
r | sed 's&$&-2.67&'`'|g' -e 's|@autom4te-na...@]|'`echo autom4te | sed
's&$&-2.67&'`'|g' -e 's|@m...@]|/usr/local/bin/gm4|g' -e 's|@a...@]|/usr/b
in/awk|g' -e 's|@versi...@]|2.67|g' -e 's|@package_na...@]|GNU Autoconf|g'
./autom4te.in >autom4te.tmp
chmod a-w autom4te.tmp
mv autom4te.tmp autom4te.cfg
gmake[3]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib'
cd ../lib/m4sugar && gmake version.m4
gmake[3]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib/m4sugar'
:;{ \
echo '# This file is part of -*- Autoconf -*-.' && \
echo '# Version of Autoconf.' && \
echo '# Copyright (C) 1999, 2000, 2001, 2002, 2006, 2007, 2009' &&
\
echo '# Free Software Foundation, Inc.' && \
echo &&\
echo 'm4_define([m4_PACKAGE_NAME], [GNU Autoconf])' && \
echo 'm4_define([m4_PACKAGE_TARNAME], [autoconf])' && \
echo 'm4_define([m4_PACKAGE_VERSION], [2.67])' && \
echo 'm4_define([m4_PACKAGE_STRING],[GNU Autoconf 2.67])' && \
echo 'm4_define([m4_PACKAGE_BUGREPORT], [bug-autoc...@gnu.org])'
&& \
echo 'm4_define([m4_PACKAGE_URL], [
http://www.gnu.org/software/autoconf/])' && \
echo 'm4_define([m4_PACKAGE_YEAR], ['`sed
's/^\([0-9][0-9][0-9][0-9]\).*/\1/;q' ../../ChangeLog`'])'; \
} > version.m4-t
mv version.m4-t version.m4
gmake[3]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib/m4sugar'
autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg'
../bin/autom4te -B '..'/lib -B '..'/lib --language M4sh --cache '
' --melt ./autoconf.as -o autoconf.in
autoconf.as:1: /usr/local/bin/gm4: Warning: Excess arguments to built-in
`_m4_popdef' ignored
autom4te: /usr/local/bin/gm4 failed with exit status: 1
gmake[2]: *** [autoconf.in] Error 1
gmake[2]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/bin'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/devel/autoconf267.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade.11621.2 env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=autoconf-2.62 UPGRADE_POR
T_VER=2.62 make
** Fix the problem and try again.
---> Skipping 'devel/automake19' (automake-1.9.6_3) because a requisite
package 'autoconf-2.62' (devel/autoconf267) failed (specify -k to force)
** Package 'automake' has been removed from ports tree.
---> Skipping 'devel/automake19' (automake-1.9.6) because it has already
been skipped
** Listing the failed packages (*:skipped / !:failed)
! devel/autoconf267 (autoconf-2.62) (unknown build error)
* devel/automake19 (automake-1.9.6_3)
* devel/automake19 (automake-1.9.6)
---> Packages processed: 2 done, 1 ignored, 2 skipped and 1 failed
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"If you have nothing good to say about someone, just shut up!."
-- Lucky Dube
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
