[haiku-development] Re: Build under Linux seems to be busted.
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 30 Nov 2007 00:21:46 +0100
On 2007-11-29 at 23:22:22 [+0100], Bruno G. Albuquerque <bga@xxxxxxxxxxxxx>
wrote:
> On Thu, 29 Nov 2007 22:06:45 +0100, Ingo Weinhold said:
>
> > > Tried both with GCC2.95 and GCC4 (the output bellow is from GCC4)
> > > after
> > > completely removing the generated dir and running configure. Here
> > > is
> > > what i got when trying to compile:
> > [...]
> >
> > Apparently your build system is in update mode. My guess is that you
> > invoke
> > "SetUpdateHaikuImageOnly 1" in your UserBuildConfig. There's usually
> > no need
> > to do that, since one can use the rather convenient update-image,
> > update-vmware-image, and update-install pseudo-targets (e.g. "jam -q
> > update-image kernel" to update the kernel on the image only).
>
> Could be, I will have to check tomorrow. But considering the image was
> also inside the generated dir and it was also erased, shouldn't it be
> able to detect that and do a normal build then?
It probably could, but it's pretty unnecessary. The SetUpdateHaikuImageOnly
rule is kind of a build system power user feature, i.e. you're supposed to
know what you're doing, if you use it manually.
Running e.g. "jam -q update-image kernel" without an existing image does
also fail, but given that this line explicitly requests only to update the
kernel file, that's just what should happen.
CU, Ingo
Other related posts:
