Summary: | editors/Openoffice.org-2.0 build WITH_GNUGCJ fails | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Heino Tiedemann <rotkaps_spam_trap> |
Component: | Individual Port(s) | Assignee: | freebsd-openoffice (Nobody) <openoffice> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | ||
Priority: | Normal | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Heino Tiedemann
2006-04-17 18:30:15 UTC
Responsible Changed From-To: freebsd-ports-bugs->openoffice Over to maintainer(s). ----- Forwarded message from Bartosz Fabianowski <freebsd@chillt.de> ----- From: Bartosz Fabianowski <freebsd@chillt.de> To: Mark Linimon <linimon@FreeBSD.org> Cc: freebsd-ports-bugs@FreeBSD.org, openoffice@FreeBSD.org Subject: Re: ports/95951: editors/Openoffice.org-2.0 build WITH_GNUGCJ fails X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on pancho.soaustin.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.1 tests=AWL,BAYES_00 autolearn=ham version=3.0.3 This is actually a problem with libtool while building lang/gcc41-withgcjawt. There are three possible causes for this: a) The lang/gcc41 port (master port of lang/gcc41-withgcjawt) comes with an outdated libtool version and needs "USE_AUTOTOOLS=libtool:15" in order to use the system-provided libtool 1.5. This is highly unlikely as others would certainly have noticed that lang/gcc41 does not compile before. b) AWT, as bundled with gcc 4.1, uses its own private copy of libtool which happens to be outdated. I don't know whether lang/gcc41 compiles AWT as well. If it doesn't, then it's possible that this somehow got missed so far - but it is also very unlikely (Maho would have noticed this while testing his own port). c) By far the most likely explanation: You have not correctly updated the ports installed on your system when libtool handling was redone in February. Short of "portupgrade -af", this is hard to fix. There is a port that was compiled with an old version of libtool somewhere on your machine and it needs to be reinstalled; finding this port won't be easy. You can try "portupgrade -a" of course to see whether there aren't any obviously stale ports. - Bartosz ----- End forwarded message ----- State Changed From-To: open->closed This is not an issue of OpenOffice.org port, as Bartosz told. |