Re: pkg/40206 (www/nvu w pkgsrc modular xorg compile errors (NetBSD 4))

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/40206; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/40206 (www/nvu w pkgsrc modular xorg compile errors (NetBSD
 4))
Date: Tue, 16 Aug 2011 01:10:07 +0000

 On Mon, Aug 15, 2011 at 02:15:03PM +0000, Robert Elz wrote:
  >    | Synopsis: www/nvu w pkgsrc modular xorg compile errors (NetBSD 4)
  >    | 
  >    | State-Changed-From-To: open->feedback
  >    | State-Changed-By: dholland%NetBSD.org@localhost
  >    | State-Changed-When: Sat, 13 Aug 2011 19:10:32 +0000
  >    | State-Changed-Why:
  >    | It looks like obache fixed it in March, give it another try...
  >  
  >  The errors from the PR (from 2 1/2 years ago) seem to have gone, but
  >  they're just replaced by a different set ...
  >  [...]
  >  nsHttpConnectionMgr.cpp:837: error: 'uintptr_t' was not declared in this 
scope
 
 Hmm... I put that uintptr_t there but it built for me. That was on
 amd64 -current though. Maybe -current is (improperly?) including
 stdint.h into some other header...
 
  >  I'll include them here, but if it is better, we could close this PR, and
  >  I can submit a new one with the current error set (as below).
 
 Doesn't really matter.
 
  >  The dereferencing type-punned pointer at the end is just for
  > completeness, there are zillions of that kind of warning throughout
  > (this file and others), I assume they're not all that important.
 
 Probably not; they may lead to gcc miscompiling things but I wouldn't
 worry about it unless/until a visible problem appears. And at that
 point the best approach is to just add -fno-strict-aliasing.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost