Ticket #2458 (new bug)

Opened 5 months ago

Last modified 5 months ago

gcc4 build fails on haiku

Reported by: mt Owned by: axeld
Priority: normal Milestone: R1
Component: File Systems/BFS Version: R1 development
Cc: andreas.faerber@… Blocked By:
Platform: x86 Blocking:

Description

I tried building native gcc4 (source from haiku tree) on Haiku. (r26134) But Build stops after fixinclude. From syslog, I thing file system issue has occur at fixinclude.

Attachments

syslog.txt (77.2 kB) - added by mt 5 months ago.
syslog file
gcclog.txt (245.2 kB) - added by mt 5 months ago.
gcc build log
gdb.txt (1.1 kB) - added by mt 5 months ago.
syslog2.txt (78.6 kB) - added by mt 5 months ago.
gcclog2.txt (245.0 kB) - added by mt 5 months ago.

Change History

Changed 5 months ago by mt

syslog file

Changed 5 months ago by mt

gcc build log

Changed 5 months ago by andreasf

  • cc andreas.faerber@… added

Changed 5 months ago by mmlr

The "KERN: bfs: inode at 2621836 is corrupt!" line would indicate that said inode is in fact corrupt. The could easily be from a damage filesystem because of crashes probably. Can you reproduce the same issue with a freshly initialized filesystem as well? I will try to do a GCC4 build and check if the same issues arise here.

Changed 5 months ago by mt

Hi, mmlr.
I freshly initialize haiku's partition by DriveSetup (bone). and tried with r26144 (build on bone). In r26144, fixincl crashes and file system corrupts.

Changed 5 months ago by mt

Changed 5 months ago by mt

Changed 5 months ago by mt

Note: See TracTickets for help on using tickets.