[openbeos] Re: bash build fails
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 01 Sep 2004 00:58:22 +0200
On 2004-08-31 at 18:41:38 [+0200], Ingo Weinhold wrote:
> On Tue, 31 Aug 2004, Ingo Weinhold wrote:
> > On Tue, 31 Aug 2004, Ingo Weinhold wrote:
> >> On Tue, 31 Aug 2004, Axel Dörfler wrote:
> >>
> >>> is the bash version in our repository supposed to build correctly?
> >>>
> >>> That's what I get here:
> >>>
> >>> Yacc1 ../../../../objects/x86.R1/apps/bin/bash/parse.c ../../../../
> >>> objects/x86.R1/apps/bin/flex/parse.h
> >>> conflicts: 1 shift/reduce
> >>> YaccMv ../../../../objects/x86.R1/apps/bin/bash/parse.c ../../../../
> >>> objects/x86.R1/apps/bin/flex/parse.h
> >>> warning: using independent target <src!apps!bin!flex>parse.c
> >>> Yacc1 ../../../../objects/x86.R1/apps/bin/flex/parse.c ../../../../
> >>> objects/x86.R1/apps/bin/flex/parse.h
> >>> YaccMv ../../../../objects/x86.R1/apps/bin/flex/parse.c ../../../../
> >>> objects/x86.R1/apps/bin/flex/parse.h
> >>> Cc ../../../../objects/x86.R1/apps/bin/bash/parse.o
> >>> Cc ../../../../objects/x86.R1/apps/bin/bash/print_cmd.o
> >>> In file included from /System.R5/home/develop/openbeos/current/src/apps
> >>> /bin/bash/print_cmd.c:41:
> >>> /System.R5/home/develop/openbeos/current/src/apps/bin/bash/include/
> >>> y.tab.h:1: error: parse.h: No such file or directory
> >>
> >> As it looks, a few lines above a parse.h is created. Since you're not
> >> building from the root directory (current/), you certainly use the OBOS
> >> jam, don't you?
> >
> > Though upon a second look, it doesn't seem to be the right parse.h. I hope
> > whoever wrote the Jamfiles for flex and bash knew what he was doing.
>
> I fear this is going to be a monolog. ;-)
... but who care... as long as I entertain myself. ;-)
> The Jamfiles for bash and flex actually look OK. There must be another
> problem. I don't see where though -- the involved low-level rules
> (Objects, Object) seem to do the right thing, too. This requires some
> further analysis, I'm afraid.
The simple fact is, that I cannot reproduce this. So there's little I can
investigate. I'm using Jam 2.5rc3, the version from the HEAD of our CVS, BTW.
CU, Ingo
- References:
- [openbeos] bash build fails
- From: Axel Dörfler
- [openbeos] Re: bash build fails
- From: Ingo Weinhold
- [openbeos] Re: bash build fails
- From: Ingo Weinhold
- [openbeos] Re: bash build fails
- From: Ingo Weinhold
Other related posts:
- » [openbeos] bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- » [openbeos] Re: bash build fails
- [openbeos] bash build fails
- From: Axel Dörfler
- [openbeos] Re: bash build fails
- From: Ingo Weinhold
- [openbeos] Re: bash build fails
- From: Ingo Weinhold
- [openbeos] Re: bash build fails
- From: Ingo Weinhold