The openoffice-1.1 port build fails early (just after completing the contained build of mozilla). When building with WITHOUT_MOZILLA, it fails almost immediately, ending with this line:
You may now run /backups/ports-work/usr/ports/editors/openoffice-1.1/work/OOo_1.1.3_src/bootstrap in /backups/ports-work/usr/ports/editors/openoffice-1.1/work/OOo_1.1.3_src
===> Building for openoffice-1.1.3_1
dmake: makefile.mk: line 251: Error -- Include file target.mk, not found
*** Error code 255
This is the case when building the port manually or via portupgrade.
Sure enough, the top-level dmake makefile.mk refers to a "target.mk" that doesn't exist; and isn't on dmake's include path, for some reason.
This build error has persisted for several months now. There's nothing particularly unusual about this system; it's most perplexing :-( I've removed and re-updated the ports directory, checked the various tarballs and everything else seems ok.
How-To-Repeat: cd /usr/ports/editors/openoffice-1.1 && make
Over to maintainer(s).
As a followup, I note that someone else appears to have had a similar
issue back in October:
However, I can't make head nor tail of the problem description there :-/
The problem here is that the user had the devel/dmake installed
already and OpenOffice's configure has decided to use it.
Unfortunately, our devel/dmake (4.1) is too old to understand the
DMAKEROOT environment variable, which OpenOffice's boostrap script is
The work-around is to uninstall the dmake port prior to building
OOo. The immediate fix is to mark OOo as conflicting with dmake.
The proper fix is to update the devel/dmake and make OOo properly
depend on it instead of building its own. Working on this one...
Confirmed Mikhail's workaround; many thanks.
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287864 or +44 (0)117 9287088 http://ioctl.org/jan/
"Impact of vulnerability: Run code of an attacker's choice
Maximum Severity Rating: Moderate" -- M$ security bulletin
dmake was upgraded several times since this PR and
understands DMAKEROOT now. Feel free to reopen this
PR if the problem still occurs.