[haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 06 Nov 2007 14:34:41 +0100
On 2007-11-06 at 10:37:37 [+0100], Stephan Assmus <superstippi@xxxxxx> wrote:
> > So, it was apparently something wrong with my haiku install - i wiped the
> > partition and re-installed fresh (instead of using the usual jam
> > install-haiku over my existing rev) and it seemed to work after that.
>
> Yes, sometimes one needs to check for errors from that direction. Another
> thing I experienced was when I did the last change on the icon renderer (to
> fix the problem in Vision's app menu), ever since than Tracker wouldn't
> display the internal icons correctly anymore (on one of my installs). After
> simply wiping all objects, it works great again. The icon code gets built
> as a static library, and though this seems to work well now for most of the
> time, appearantly sometimes something can still go wrong. (No worries
> though, Ingo, happens seldomly enough. I only mention it so that one has
> this in mind when going hunting for obscure bugs...)
I've seen static libraries in a weird state on one of Axel's Dano machines.
Something was wrong with the archive member names (IIRC, of the ".o"
extension the "o" was missing), which caused jam not to be able to match the
targets correctly and would not update them, even if needed. I've never seen
this on my BeOS R5 machine.
Another possible cause for jam not updating things correctly is when the
StatCacheServer missed a node monitoring message.
Other than that, "jam install-haiku" does indeed only copy the new over the
old file, thus leaving obsolete files and attributes. It wouldn't be a
problem to "rm -rf" at least the beos/ directory, though it would cost
additional time.
CU, Ingo
Other related posts:
