Attachments (1)
Change History (4)
by , 14 years ago
Attachment: | ...skipped kernel_core.o for lack of <src!system!kernel>sem.o....txt added |
---|
comment:1 by , 14 years ago
Component: | System/Kernel → Build System |
---|---|
Owner: | changed from | to
If anything this looks more like some kind of misconfiguration, otherwise you wouldn't be able to build the gcc4 portion either. How did you configure the build?
comment:2 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Builds without issue here, misconfigured build or disk corruption seems likely, especially given the error message:
/boot/home/develop/haiku/haiku/src/system/kernel/sem.cpp:1: parse error before character 0331 /boot/home/develop/haiku/haiku/src/system/kernel/sem.cpp:2: syntax error at null character
Which implies file corruption since no such data exists in the on-disk file.
comment:3 by , 14 years ago
The UserBuildConfig I use, has been used before successfully. As you say it is probably file system corruption. I have had several crashes where the only thing I can do is a hard reset. I was also getting errors like malformed svn when I tried to do a svn update before my last build. That forced me to empty out all the haiku develop directories and get all the source from beginning. I thought that might have stopped any more errors from file corruption but I think I have had to do another hard reset since then. I also had other email settings files corruption. Their seems no easy way at the moment to fix fs corruption with fscheck because it also crashes on trying to fix any corruption.
Terminal build output