Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Feb 2004 00:10:56 -0500
From:      Adam Weinberger <adamw@FreeBSD.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        openoffice@freebsd.org
Subject:   Re: Openoffice 1.1 not building
Message-ID:  <20040221051056.GR13847@toxic.magnesium.net>
In-Reply-To: <20040221045413.GA42180@xor.obsecurity.org>
References:  <20040221030343.1f0ce596.gautam@inspired.net.au> <20040220171144.GA33739@xor.obsecurity.org> <20040221134822.60862fc2.gautam@inspired.net.au> <20040221031220.GA41039@xor.obsecurity.org> <20040221143825.4ec73b52.gautam@inspired.net.au> <20040221035340.GA41491@xor.obsecurity.org> <20040221153954.556f3c40.gautam@inspired.net.au> <20040221045413.GA42180@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
>> (02.20.2004 @ 2354 PST): Kris Kennaway said, in 1.6K: <<
> On Sat, Feb 21, 2004 at 03:39:54PM +1100, Gautam Gopalakrishnan wrote:
> > On Fri, 20 Feb 2004 19:53:40 -0800
> > Kris Kennaway <kris@obsecurity.org> wrote:
> > > 
> > > That's completely wrong, USE_GCC is not to be set by the user.
> > > 
> > > Unfortunately for your problem, I think the Openffice maintainers are
> > > inactive at the moment (at least, I haven't heard from them in several
> > > weeks about an unrelated problem with the ports).
> > 
> > Well, bento seems to build openoffice fine (at least it's not reported
> > as a broken build)
> > http://bento.freebsd.org/errorlogs/i386-5-failure.html
> 
> Nope, it doesn't build on bento because dependencies (jdk) currently
> do not build.  The last time I was able to attempt it (sometime last
> year) the OO build itself was broken.
>> end of "Re: Openoffice 1.1 not building" from Kris Kennaway <<

I just feel that it's worth reiterating that I have identified the cause
of the build failure. One of the patches in files/ (patch-config_office)
tells the build to link against -lc_r on 5.X. Changing that behaviour to
-lpthread fixes the problem.

I've been unable to make any headway on getting openoffice@ to agree to
fix this problem, with something about it would have to go to the
openoffice authors..... to fix a FreeBSD-supplied patch.......

I gave up. But, the OO build *is* fixable, but it's up to the users to
apply the fix themselves, I guess.

# Adam


--
Adam Weinberger
adam@vectors.cx // adamw@FreeBSD.org // adamw@magnesium.net
http://www.vectors.cx



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040221051056.GR13847>