[haiku-development] Re: Can't build Haiku in BeOS R5 PE again...

  • From: "Rene Gollent" <anevilyak@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 23 Apr 2008 20:11:44 -0500

-q tells jam to stop on first error. -a tells it to try and recompile
even stuff that doesn't need to be updated. Thus if you don't include
-q it will try and build as much as it can and skip over anything that
causes an error. It's not a problem of -q per se, it's doing exactly
what's expected.

On Wed, Apr 23, 2008 at 8:04 PM, Luposian <luposian@xxxxxxx> wrote:
> Now, this is interesting...
>  If I type "jam -q haiku-image", it spews and quits in about 1 second, with
> the same stuff as before.
>  If I type "jam -a -q haiku-image", it does the exact same thing.
>  If I type "jam haiku-image", it skips a bunch of stuff, but it continues on
> doing the things it can.
>  If I type "jam -a haiku-image", it skips over a TON of things, but
> continues on things it can.
>  The -q parameter seems to be causing/invoking the problem.  But why?  And
> why is Jam skipping stuff now?  In every incident where it started skipping
> stuff, it ended up never finishing the JAM and the Haiku image was never
> done.  Is "skipping..." now acceptable or will I likely see the same result
> and no image of Haiku in the end?
>  Should I just try deleting the whole /trunk directory and starting over?
>  Luposian

Other related posts: