Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#6444 closed bug (invalid)

Wont build gcc2 alternative libs ...skipped kernel_core.o for lack of <src!system!kernel>sem.o

Reported by: HAL Owned by: bonefish
Priority: normal Milestone: R1
Component: Build System Version: R1/alpha2
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


I was trying to build hrev38075 gcc4 hybrid from hrev37730 gcc4 hybrid but build stopped at /boot/home/develop/haiku/haiku/generated.x86gcc2/objects/haiku/x86/release/system/kernel/sem.o, with a lot of errors.

Attachments (1)

...skipped kernel_core.o for lack of <src!system!kernel>sem.o....txt (48.9 KB ) - added by HAL 10 years ago.
Terminal build output

Download all attachments as: .zip

Change History (4)

comment:1 by anevilyak, 10 years ago

Component: System/KernelBuild System
Owner: changed from axeld to bonefish

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 anevilyak, 10 years ago

Resolution: invalid
Status: newclosed

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 HAL, 10 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.

Note: See TracTickets for help on using tickets.