On Thu, 13 Nov 2008 15:55:31 -0600, John Hein <[EMAIL PROTECTED]> wrote:
Lowell Gilbert wrote at 16:35 -0500 on Nov 13, 2008:
> John Hein <[EMAIL PROTECTED]> writes:
> > So my question is: is this documented and/or widely known? A full
> > portupgrade wouldn't help if you were up to date on
John Hein <[EMAIL PROTECTED]> writes:
> I often don't rebuild everything right away and live with the compat
> libs for a while.
>
> That has worked fine in the past (probably had some hiccups that I've
> long since forgotten about). But I understand why the official
> position is to rebuild ever
Lowell Gilbert wrote at 16:35 -0500 on Nov 13, 2008:
> John Hein <[EMAIL PROTECTED]> writes:
> > So my question is: is this documented and/or widely known? A full
> > portupgrade wouldn't help if you were up to date on libtool in 6.x
> > before updating (unless portupgrade -f is used).
>
>
John Hein <[EMAIL PROTECTED]> writes:
> So my question is: is this documented and/or widely known? A full
> portupgrade wouldn't help if you were up to date on libtool in 6.x
> before updating (unless portupgrade -f is used).
But you've *always* needed to rebuild *all* your ports when system
lib
On Thu, 13 Nov 2008 11:06:04 -0600, John Hein <[EMAIL PROTECTED]> wrote:
I updated from 6-stable to 7-stable and got the following error
when portupgrading graphics/tiff...
.
.
/bin/sh /usr/local/bin/libtool --tag=CXX --mode=link c++ -O2
-fno-strict-aliasing -pipe -L/usr/local/lib -o li
I updated from 6-stable to 7-stable and got the following error
when portupgrading graphics/tiff...
.
.
/bin/sh /usr/local/bin/libtool --tag=CXX --mode=link c++ -O2
-fno-strict-aliasing -pipe -L/usr/local/lib -o libtiffxx.la -rpath
/usr/local/lib -no-undefined -version-number 4:0:0 tif_s