[haiku-development] HaikuPorts build failure when on ramdisk?

  • From: waddlesplash <waddlesplash@xxxxxxxxx>
  • To: Haiku Development ML <haiku-development@xxxxxxxxxxxxx>, HaikuPorts ML <haikuports@xxxxxxxxxxxxx>
  • Date: Thu, 15 Jun 2017 21:31:33 -0400

Hi,

So, the Kitchen is up, running, and building things. Most of the
compile errors it's hitting are legitimate ones that need fixing, but
I've also seen a bunch of really weird intermittent ones I've never
seen before.

The only configuration difference between my development VM and
arfonzo's slave is that arfonzo's slave VM has *really* slow disk
access -- and I mean *really* slow: building ~30pkgs took 14hrs on the
first run, so to work around this the HaikuPorts tree is inside a 9GB
ramdisk (with a BFS partition on the top of that.) (The same run of
packages took ~1.25hrs with this setup.)

However, with this setup there are also some odd failures that I don't
know how to account for, such as this one encountered while building
glib2:

/bin/grep: 
/packages/gettext-0.19.8.1-2/devel~libiconv/develop/lib/libiconv.la: No such 
file or directory
/bin/sed: can't read 
/packages/gettext-0.19.8.1-2/devel~libiconv/develop/lib/libiconv.la: No such 
file or directory
libtool: link: 
`/packages/gettext-0.19.8.1-2/devel~libiconv/develop/lib/libiconv.la' is not 
a valid libtool archive
(Full log at http://vmpkg.haiku-os.org/kitchen/#/build/39 if anyone wants it.)

I SSH'd into the builder manually and confirmed that
/packages/gettext-0.19.8.1-2/devel~libiconv/develop/lib/libiconv.la as
well as 
haikuports/dev-libs/glib/work-2.48.2/packages/gettext-0.19.8.1-2/devel~libiconv/develop/lib/libiconv.la
both exist and are valid libtool files (but this was some time after
the build had failed.)

Anyone have a clue as to what's going on here?
-waddlesplash

Other related posts:

  • » [haiku-development] HaikuPorts build failure when on ramdisk? - waddlesplash