[haiku-development] Re: self hosting: svn? headers? gcc?

  • From: "scott mc" <scottmc2@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Fri, 27 Jun 2008 12:10:59 -0700

On Sat, Jun 21, 2008 at 10:51 PM, Donn Cave <donn@xxxxxxxxxxx> wrote:
> I'm trying to build from scratch on Haiku, from a raw
> hard disk install, and some parts seem to be missing.
> Am I just looking in the wrong place, or is the whole
> tool set not really there yet?
> 1.  No svn for Haiku.  I understand this is indeed not
>    100% there yet, but maybe I can build one that's
>    good enough for read access only, so I got the source
>    and started the configure, when ...
> 2.  gcc fails, because I don't have C headers.  All right,
>    I probably just need to get them out of the source tree ...
>    oops, no svn yet.
> 3.  Now if I had headers, would gcc work?  Evidently not:
>    a simple test program with no headers fails to link
>    when ld can't find crti.o.  Is that file supposed to
>    exist somewhere, or is gcc misconfigured?
> Thanks!  I'm running a fairly recent build now (which is very
> exciting, it's really sweet to see this) and there's a hardware
> configuration problem I might be able to help out with a little
> more if I could build from source.
> --
> Donn Cave <donn@xxxxxxxxxxx>

Here's a quick update on this one.  I provided Donn a Haiku Dev image,
from there he was then able to build haiku on haiku, that is after bug
#1991 was fixed (thanks Ingo).  I've been trying for a couple of days
now to do the same thing but was finally successful today.  I attached
a screenshot to ticket 1991:
My troubles were the vfork memory issue (ticket
http://dev.haiku-os.org/ticket/2046), in which I then replaced my 512M
ram with 1GB.  Then I was running into the r8139 driver issues
reported on 1641
With the r8139 issue you can restart and eventually get everything
downloaded.  So it seems at this time 512M is not enough, but 1GB
seems to be enough to build haiku on haiku.  I may have hit the vfork
issue once with the 1GB, but if you reboot and try again the next time
it should go.  I think this probably points to a memory leak

Other related posts: