On 01-Nov-2002 Conrad Sabatier wrote:
> I just upgraded a 4.7-STABLE box to current over the weekend. Went off
> very well, thanks to the great documentation in UPDATING.
>
> It's odd, though, that after upgrading again just a few days later,
> suddenly X (or perhaps just xdm) failed to start due to an unresolved
> symbol. I had already upgraded X, as well as many other ports, after
> upgrading to -current, btw.
>
> It seems very peculiar that a cvsup just a few days apart from the
> previous one would require X to be rebuilt.
OK, turned out it was a mismatched gtk/glib combination.
> On another note, can someone clue me in as to why I'm getting all these
> "duplicate script" errors when building both ports and world? I've
> looked high and low and can't find the reason for this. Seems harmless
> enough, but it *is* just slightly annoying.
And these seem to have pretty much disappeared as well. Still no idea what
was causing them.
> And finally, is there a simple way to ensure that none of the debugging
> code (including INVARIANTS stuff) is included during a buildworld?
> It would be nice if there were a simple switch or environment variable to
> control this.
Now *this* I would still be interested to know about.
--
Conrad Sabatier <[EMAIL PROTECTED]>
Liar, n.:
A lawyer with a roving commission.
-- Ambrose Bierce, "The Devil's Dictionary"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
