Re: broken autoconf upgrade
Michael P. Soulier [EMAIL PROTECTED] writes: While running portupgrade -ai, I noticed this else \ rc=$?; \ cd . \ $restore $backupdir/* `echo ./autoconf-2.62.info | sed 's|[^/]*$||'` ; \ fi; \ rm -rf $backupdir; exit $rc autoconf-2.62.texi:1723: Unknown command `'. autoconf-2.62.texi:3353: Unknown command `'. autoconf-2.62.texi:3920: Unknown command `'. autoconf-2.62.texi:3935: Unknown command `'. autoconf-2.62.texi:3947: Unknown command `'. autoconf-2.62.texi:3965: Unknown command `'. autoconf-2.62.texi:3986: Unknown command `'. autoconf-2.62.texi:4001: Unknown command `'. autoconf-2.62.texi:4019: Unknown command `'. autoconf-2.62.texi:4027: Unknown command `'. So, this won't upgrade. Anyone else see that? Nope. And that port doesn't do anything different with the texinfo files, either. Try just cleaning things up and making another attempt. Or remove all of the auto* ports and try to upgrade everything remaining; I've never had problems with those ports interfering with each other, but for some reason I worry about it anyway. And you may not need any of them for your upgrade run anyway. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: broken autoconf upgrade
On Sat, Sep 6, 2008 at 10:17 AM, Lowell Gilbert [EMAIL PROTECTED] wrote: Nope. And that port doesn't do anything different with the texinfo files, either. Try just cleaning things up and making another attempt. Or remove all of the auto* ports and try to upgrade everything remaining; I've never had problems with those ports interfering with each other, but for some reason I worry about it anyway. And you may not need any of them for your upgrade run anyway. Someone else responded saying that the port is no longer maintained on 5.5. I hadn't upgraded since everything was working fine, and new releases sometimes leave old hardware behind. But, I'll try upgrading anyway. 5.5 - 6.3 - 7.0 seems to be the right route... Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
broken autoconf upgrade
While running portupgrade -ai, I noticed this else \ rc=$?; \ cd . \ $restore $backupdir/* `echo ./autoconf-2.62.info | sed 's|[^/]*$||'` ; \ fi; \ rm -rf $backupdir; exit $rc autoconf-2.62.texi:1723: Unknown command `'. autoconf-2.62.texi:3353: Unknown command `'. autoconf-2.62.texi:3920: Unknown command `'. autoconf-2.62.texi:3935: Unknown command `'. autoconf-2.62.texi:3947: Unknown command `'. autoconf-2.62.texi:3965: Unknown command `'. autoconf-2.62.texi:3986: Unknown command `'. autoconf-2.62.texi:4001: Unknown command `'. autoconf-2.62.texi:4019: Unknown command `'. autoconf-2.62.texi:4027: Unknown command `'. So, this won't upgrade. Anyone else see that? Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
