[haiku-development] gcc4 failure
- From: pete.goodeve@xxxxxxxxxxxx
- To: Haiku Development <haiku-development@xxxxxxxxxxxxx>
- Date: Sun, 17 Jul 2011 16:20:20 -0700
Somehow I seem to keep running into these baffling problems!
I just picked up patch r42441 and decided I might as well do a hybrid build,
so I'd have a nicely updated image. The gcc2-build part went through fine
(so I have the libtracker.so I needed), but when it went to the gcc4 part,
it died:
C++
/BFS_User/haiku/haiku/generated.x86gcc4/objects/haiku/x86/release/kits/tracker/ContainerWindow.o
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:159:14: error: null
character(s) ignored
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp: In function
'filter_result BPrivate::ActivateWindowFilter(BMessage*, BHandler**,
BMessageFilter*)':
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:159: error: 'class
BView' has no member named 'Wi'
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:159: error: expected
')' before 'lse'
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:164: error: expected
primary-expression before '}' token
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:164: error: expected
';' before '}' token
cc1plus: warnings being treated as errors
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:164: error: no
return statement in function returning non-void
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp: At global scope:
/BFS_User/haiku/haiku/src/kits/tracker/ContainerWindow.cpp:351: error: expected
'}' at end of input
... everything seeming to follow from that "null character".
However, I scanned the file for a null, even did od -c and looked at the
line in question. There *is* no null character!
Even odder, the patch was a minor one to r42415 (and in fact didn't change
anything near that line) which built perfectly succesfully last week!
I tried copying the file, in case there was a filesystem glitch or something,
but it made no difference, and the file reads with no problem.
Any clues?
-- Pete --
Other related posts:
