[haiku-development] Re: Build native gcc 4.1.2 for Haiku, but it's buggy.
- From: "Rene Gollent" <anevilyak@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 27 Dec 2007 14:21:33 -0600
For what it's worth, as far as I'm aware chkbfs mostly just frees
stray blocks that were lost due to edge cases in the journaling
mechanism ; I don't think it tries to correct any more serious errors,
though I might be wrong. On Dano in any case, there is also a tool
called forcerm that lets you remove files that can't be deleted
otherwise, but that's a good sign that you have more serious FS issues
and might want to reformat/recreate that partition.
Rene
On Dec 27, 2007 2:07 PM, Anthony Lee <don.anthony.lee@xxxxxxxxx> wrote:
> Hi,
>
> I guess the only way to make more applications or others running on Haiku
> seemed like this, I must placing the codes to Haiku source tree then
> create Jamfile, etc.
> In order to avoid those things, I find a way to create
> i586-pc-haiku-g++ can work
> with autoconf, etc on Linux, then use it to build a native gcc for Haiku.
>
> But when I compile applications on Haiku, I just notice that gcc 4.x
> is buggy likes François said,
>
> Sometimes, gcc print a message "received system's interrupt call" and
> quit when compiling.
> Second, I can't delete the files (except on Dano) after perl's
> "./Configure -d" or "./configure.gnu" run.
> I doubt the disk issue cause that, but nothing wrong to use "chkbfs
> /Haiku" on Dano.
>
> The procedures of that attached to this mail, hope the team could find
> out what's the problem.
> Thanks you for bringing Haiku to be a modern & powerful system.
>
> A.L.
>
Other related posts:
