Date: Sat, 29 Nov 2008 12:26:33 +0200 (EET) From: jau@iki.fi (Jukka A. Ukkonen) To: bug-followup@freebsd.org, openoffice@freebsd.org Subject: Re: ports/129122: Building OpenOffice.org-3.0.0 fails Message-ID: <200811291026.mATAQXun013656@jau.iki.fi> In-Reply-To: <200811240850.mAO8o1F1012897@freefall.freebsd.org> from "FreeBSD-gnats-submit@FreeBSD.org" at Nov 24, 8 08:50:01 am
next in thread | previous in thread | raw e-mail | index | archive | help
The root cause seems to be quite obvious in this case.
GNU cp (gcp) still fails miserably when ACLs are enabled.
It assumes that it can set default ACLs for files other than
directories. Linux quietly accepts and ignores a default ACL
for files other than directories. FreeBSD OTOH quite correctly
returns an error.
This leaves some intermediate targets non-existent during the
build when ACLs are enable.
The correct solution would be fixing gcp of course.
To make the ports build successful on ACL enabled systems
while waiting for the real fix you can...
1) either make the build phase use the native cp in place of
gcp (labour intensive),
2) or emulate gcp on top of the native cp (simple),
*) and remove the stupid test for the real gcp being used
during the configure phase, because it is a guaranteed way
to make the build process fail.
With that pointless test in place it becomes hard to emulate
gcp on top of the native cp.
Even better would be simply turning the ACLs on in the FreeBSD
ports build environments to make this sort of problems stick
out in a way that they just have to be fixed.
Cheers,
// jau
.--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -.
/ Jukka A. Ukkonen, Oxit Ltd, Finland
/__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671
/ Internet: Jukka.Ukkonen(a)Oxit.Fi (Home) +358-9-6215-280
/ Internet: jau(a)iki.fi
v
.--- .- ..- ...-.- .. -.- .. .-.-.- ..-. ..
+ + + + My opinions are mine and mine alone, not my employers. + + + +
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811291026.mATAQXun013656>