Build (via portupgrade or directly) of openoffice fails. Google only finds this error reported once on a mailing list, no solutions found:
The first error occurs here:
+++ making chrome /usr/ports/editors/openoffice-1.1/work/moz.runtime/unxfbsd.pro/misc/build/mozilla/xpcom/base => ../../dist/bin/chrome/en-US.jar
Died at ../../config/make-jars.pl line 294, <STDIN> line 2.
gmake: *** [libs] Error 255
How-To-Repeat: "portupgrade openoffice"
Over to maintainer
I believe I have found the issue.
The line in question that was failing was this:
my $atime = stat($file)->atime || die $!;
The filesystem containing the ports work directory was mounted noatime.
The first file that was failing was charsetTitles.properties:
> find . -name charsetTitles.properties | xargs ls -lu
-rw-r--r-- 1 8482 wheel 4885 Aug 1 23:04 ./OOo_1.1.5/moz.runtime/unxfbsd.pro/misc/build/mozilla/intl/uconv/src/charsetTitles.properties
-rw-r--r-- 1 8482 wheel 4385 Jan 1 1970 ./OOo_1.1.5/moz.runtime/unxfbsd.pro/misc/build/mozilla/l10n/langpacks/en-DE/chrome/en-DE/global/locale/charsetTitles.properties
-rw-r--r-- 1 8482 wheel 4385 Jan 1 1970 ./OOo_1.1.5/moz.runtime/unxfbsd.pro/misc/build/mozilla/l10n/langpacks/en-GB/chrome/en-GB/global/locale/charsetTitles.properties
As you can see, two of those files have no atime set - the timestamp
therefore has a numeric value of 0. Consequently the stat call _appears_
to fail mysteriously.
There are obviously several "workarounds" - don't use noatime; get rid
of the "|| die $!", etc.
Hope this helps.
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44 (0)117 3317661 http://ioctl.org/jan/
We thought time travel was impossible. But that was now and this is then.
Is this still a problem after the recent upgrades?