libreoffice fails to build

[Jung-uk Kim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2012-07-19 15:32:56 -0400, Doug Barton wrote:
> 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.

Please don't bother.  I *know* it is broken there.

> ... 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.

I admit that it was my mistake and assumed clang-devel would be good
enough for LibreOffice on 7 & 8.  Sorry for that.  Working on fixing it.

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAIZG0ACgkQmlay1b9qnVOzSQCcDvPkR6W5ODT0zKdSr+QwJd20
IVgAoM5vSR//zN3LIWC0+RsHdkdGF1QI
=AogE
-----END PGP SIGNATURE-----