On Monday, September 30, 2002, at 12:30 AM, Joel Hacker wrote:
> Actually, he didn't say he wasn't using ANY Norton tools, just that he
> wasn't using SystemWorks specifically. I tend to take people at their
> literal word and endevour not to draw too many inferences. My
> thought is that if auto-protect can cause probs then it is possible
> that there may be some other "always on" processes that can cause
> similar probs. I would be deeply interested in knowing about any and
> all of them, if indeed more than just NAV auto-protect can cause this
> phenomenon.
>
Right, I just wasn't aware of other tools that might destabilize your
system in a similar way, for a virus scanner it's somewhat
conceivable, though I would not want anything like this on my system...
My main point anyway was that this was not a case of a system-crashing
compile failure.
>> Steve, the symbols ld is missing in your installation belong to
>> libslang, not to ncurses, so I'd suggest to check if slang is
>> installed, and possibly rebuilt under 10.2.
>
> Would "fink selfupdate-cvs" fix this? If not, are there any other
> probs that may arise as a result of non-updated libraries that you
> know of that the rest of us should know about?
>
Well, this case was apparently a problem of linking to an internal
library of the package, not of another package, but it happened to me
in a few instances. I assume these problems partly occurred because I
had the experimental 10.2 tree installed before the official upgrade
recipe was around, but it's possible this could happen to someone else
too, as the upgrade script might not be tested for every possible
configuration.
As I understand it, fink update will not automatically recognize if a
package needs to be recompiled for Jaguar -- selfupdate will install
the package descriptions into the 10.2 tree, but if the version number
did not increase, an update-all or 'update package' will not rebuild
the package if it is already installed. This is why the update-fink.sh
script needs to be executed before other packages are updated to 10.2.
So, whenever I found a package that would not build under Jaguar, I
looked up the Dependencies and checked if they had already been rebuilt
since the system upgrade, and if not, an explicit 'rebuild package'
would often fix the problem.
Again, if you have upgraded fink through the regular path, you probably
should not see such problems.
Derek
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
