Date: Thu, 19 Jul 2012 12:32:56 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: ports@freebsd.org, Robert Huff <roberthuff@rcn.com>, office@freebsd.org, Kevin Oberman <kob6558@gmail.com> Subject: Re: libreoffice fails to build Message-ID: <500860E8.5040403@FreeBSD.org> In-Reply-To: <50085D4C.60901@FreeBSD.org> References: <20486.55903.34769.952614@jerusalem.litteratus.org> <500729B3.1050208@FreeBSD.org> <20487.20506.88401.623249@jerusalem.litteratus.org> <CADLo83-0gak%2B8kBpmg6jUdeHcrYC65CEqCg1SciFe5TXiceM6g@mail.gmail.com> <CAN6yY1sPkuPTt0BtWNoavA-o2FRbEPjwRL88bzR_pC5qyNJenw@mail.gmail.com> <20488.23232.578561.75939@jerusalem.litteratus.org> <50085D4C.60901@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/19/2012 12:17, Dimitry Andric wrote:
> On 2012-07-19 21:06, Robert Huff wrote:
> ...
>> Let me be clear:
>> There is at least one person out there who has successfully
>> built LibreOffice 3.5.5 using (system) clang 3.2?
>
> The version of clang in base is 3.1. I have successfully compiled
> LibreOffice with it, and it even seemed to run OK, though I didn't test
> it very thoroughly. There were several other posters which confirmed
> the same.
... including me.
> Apparently in r301038, jkim updated the libreoffice port to use the
> lang/clang-devel port instead, which is built from a very recent 3.2
> snapshot. I have no idea if LO compiles successfully with that. Maybe
> you found a problem with the clang-devel port. :)
I'm currently building on 8-stable with clang-devel, so we'll see how
that goes.
... and while we're on that topic, IMO it would have been a *lot* better
for jkim to have coordinated with brooks to get lang/clang updated to
the same level as clang in HEAD (i.e., including the fix for the bug
that affects LO) prior to releasing the update for 3.5.5. As it stands
right now, this is the sequence for a user on 8-stable:
1. install lang/clang (+ llvm, in all clang steps below)
2. build/install LO 3.5.2
3. uninstall lang/clang
4. install lang/clang-devel
5. build/install LO 3.5.5
... then assuming lang/clang is fixed down the road ...
6. uninstall lang/clang-devel
7. install lang/clang
8. build/install LO 3.5.N
This is exactly the kind of thing that makes people look at the way the
ports tree is managed and shake their head in disbelief.
Even if lang/clang needed to be upgraded at every new LO release (as it
would have this time) tools like portmaster can handle that upgrade "in
line" without any intervention from the user. The procedure above
requires at least 2 manual steps that cannot be automated.
Doug
--
Change is hard.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?500860E8.5040403>