[openbeos] Re: Misc. problems building Haiku on Linux
- From: Geoff Sallee <geoff.sallee@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 15 Nov 2005 09:11:21 -0800
Yeah, I found that out through looking through the older messages. So it
seems to be a problem building the resource parser, as the first error that
comes up after running 'jam -q haiku-image' is:
InitScript1 generated/haiku.image-init-vars
Yacc1 generated/objects/linux/x86/common/tools/rc/parser.cpp
generated/object/linux/x86/common/tools/rc/parser.hpp
crc/tools/rc/parser.y:117 parser name defined to default :"parse"
C++ generated/objects/linux/x86/release/tools/rc/compile.o
src/tools/rc/compile.cpp:36:22: parser.hpp: No such file or directory
I'm thinking this might be a result of using the wrong version of
bison/yacc, so I'll look into that first.
-Geoff
On 11/15/05, Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
>
>
> On 2005-11-14 at 23:08:02 [+0100], Geoff Sallee wrote:
> >
> > Longtime lurker, first time poster. I used the instructions given by
> Vegard
> > and did not run into the problem that most people have run into (gas). I
> > used gcc-3.3 on ubuntu 5.10 and the build tools compiled perfectly fine
> > (AFAIK), so that may be the issue you all are running into. However,
> haiku
> > does not build because libbe.so does not build in linux. The problem
> seems
> > to be missing resource files (e.g. ...skipped <src!apps!terminal>
> > Terminal.rsrc for lack of <build>rc...). I can provide full log files if
> > necessary, but I don't want to post a huge file to the listserv.
>
> "<build>rc" is actually built by the build system, so its lack quite
> likely
> means, that it failed to build earlier. If you run jam with the "-q"
> option
> (e.g. "jam -q haiku-image") it bails out as soon as it encounters an
> error.
> The messages produced when you run it a second time should only reproduce
> the error without the earlier noise. Feel free to post that here.
>
> CU, Ingo
>
>
Other related posts:
