[haiku] Re: build failure from source

  • From: Jessica Hamilton <jessica.l.hamilton@xxxxxxxxx>
  • To: "haiku@xxxxxxxxxxxxx" <haiku@xxxxxxxxxxxxx>
  • Date: Thu, 30 Apr 2015 16:05:21 +1200

On Thursday, 30 April 2015, Michael Mounteney <gate03@xxxxxxxxxxxxxxx>

On Tue, 28 Apr 2015 22:00:21 +0200
Axel Dörfler <axeld@xxxxxxxxxxxxxxxx <javascript:;>> wrote:

Am 24/04/2015 um 22:45 schrieb Michael Mounteney:
Building from git master ends with:

I recently had a similar problem building Haiku when a package got
downgraded. The solution was to delete the problematic packages (or
just all of them for simplicity), and build again.
Could help you as well -- at least the build bots don't seem to have
a problem compiling the thing.

Thanks for the suggestion but it didn't work for me:

$ rm download/pe-2.4.5-1-x86.hpkg download/vision-0.9.7.r949-3-x86.hpkg
$ jam @nightly-Wyse-Jupiter
Encountered problems:
problem 1: nothing provides haiku>=r1~alpha4_pm_hrev49036-1 needed by
pe-2.4.5-1 solution 1:
- allow deinstallation of pe-2.4.5-1
problem 2: nothing provides haiku>=r1~alpha4_pm_hrev49036-1 needed by
vision-0.9.7.r949-3 solution 1:
- allow deinstallation of vision-0.9.7.r949-3

export imagePath="/dev/sda2"
export isImage="1"
export isVMwareImage=""

...failed BuildHaikuImage1 /dev/sda2 ...

...failed updating 1 target(s)...
...updated 935 target(s)...

Run git describe --tags, and ensure the hrev it prints is higher than what
is mentioned in the output above.

If you manually set it in your UserBuildConfig file, then you need to
update the value there. Also check the haiku revision files under
generated/build to ensure they're correct there as well.

Other related posts: