Migrating to X.org with portupgrade

kstewart kstewart at owt.com
Tue Aug 17 23:37:10 PDT 2004

On Tuesday 17 August 2004 11:27 pm, Daniel O'Connor wrote:
> Hash: SHA1
> On Wed, 18 Aug 2004 14:43, kstewart wrote:
> > One more point. When you build a new library, the only safe thing to do
> > is rebuild everything that uses that library. You don't know if they
> > changed an element of a structure or not. If they didn't and you rebuild
> > everything, all you did is lose some cpu time. If they modified
> > something, and you don't rebuild everything, then, you have introduced
> > the possiblity for massive offset errors that you won't know about until
> > someone breaks into your system.
> I am pretty sure that things like Xlib have quite a fixed ABI which means
> you shouldn't have to rebuild apps that use it.

I didn't know about that end :).

> The most likely outcome of a broken ABI is a coredump and I don't see any
> of those, all the applications I've tried work fine too.

Mine did to. Around that time they also made a number of changes to 3.2.3 and 
changed the gcc compiler. There were a number of ports that had to be rebuilt 
because of the upgrade in the gcc compiler. I think at some point, I just 
rebuilt everything.


> Don't forget that even if there was a static binary the X wire protocol is
> well defined so it wouldn't affect things.
> - --

Kent Stewart
Richland, WA

Support the Bison at http://www.buffalofieldcampaign.org/

More information about the freebsd-current mailing list