[haiku-development] Re: *ALMOST* compiled Haiku within itself.
- From: "Urias McCullough" <umccullough@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 26 Mar 2008 19:36:53 -0700
On 26/03/2008, Bruno Albuquerque <bga@xxxxxxxxxxxxx> wrote:
> Subject says it all. I got really close to compile Haiku under itself but it
> seems I hit a weird bug. Anyway, here is what I did so others can try to and
> a
> description of the problem I hit:
>
> 1 - Compiled Haiku from Linux and installed it straight to a partition. Added
> all its sources and the jam source in the same process.
> 2 - Booted Haiku. Compiled jam in Haiku (out of the box).
> 3 - Downloaded flex source code and compiled it in Haiku. Only a one line
> change
> was required to get it compiling and working.
What was that one-line change? I was able to compile flex by fooling
the configure script into believing it was BeOS:
./configure --build=i586-pc-beos --prefix=/boot/home/config
make and make install worked fine for me after that.
But if there's a better way, I'm curious. I figured someone would
eventually need to update config.guess and add Haiku to the supported
platforms or something.
> 4 - Configured the Haiku source code and did jam -q haiku-image
> 5 - It stopped when compiling the usb bus manager. The compilation seems to
> happen ok. Also links without problems. xres is ran on it without problems.
> So
> does settype. But when mimeset is called on it, the file simply disappeared
> and
> is not found anymore so the build fails. This is 100% reproducible here and
> always with the usb bus manager. Really weird.
I ran into the exact same failure... WTF? I tried deleting various
things and recompiling to no avail. So I guess it's not just a fluke
:)
Exciting times!
- Urias
Other related posts:
