Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Jul 2012 12:17:42 +0200
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Doug Barton <dougb@FreeBSD.org>
Cc:        Peter Jeremy <peter@rulingia.com>, freebsd-ports@FreeBSD.org, Leslie Jensen <leslie@eskk.nu>
Subject:   Re: make failed for editors/libreoffice
Message-ID:  <4FFC0146.3030005@FreeBSD.org>
In-Reply-To: <4FFBD7FB.3010002@FreeBSD.org>
References:  <4FF15A89.3000204@eskk.nu> <4FF2E349.5000202@FreeBSD.org> <20120704191351.GB70705@server.rulingia.com> <4FF49F51.8070600@FreeBSD.org> <4FFBD734.5030909@FreeBSD.org> <4FFBD7FB.3010002@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-07-10 09:21, Doug Barton wrote:
> Thanks for looking into this. Did you see my message where I reported
> that clang from ports works fine for LO on -current, but the base clang
> fails?

The lang/clang port is the same version as clang in base (3.1 release,
minus a few patches needed for building world), but the port has asserts
disabled by default, while clang in base is built with asserts enabled.

Therefore, if you build LO with the clang port at its default settings,
the assert that breaks the build is never triggered.  However, I do not
know if the resulting object code will have problems.


> How does this change compare to the code that's already in the
> clang port?

This upstream change properly fixes the assert, which should fix the LO
build with clang.  It can also be applied to the lang/clang port,
otherwise we'll have to wait until the 3.2 release to get it.

Last but not least, to answer your question about the port not
installing a clang-cpp link (or symlink): the clang installation scripts
(either autoconf-based, or CMake-based) do not include such a link,
which I think is an oversight by upstream.  I'll lobby with them to
include such a link in the future; meanwhile, maybe our port maintainer
can manually add it.

I added the clang-cpp link in the base system, because some parts of our
build system depend on having an executable behaving as "cpp", instead
of as "cc -E".  The former preprocesses any file with unknown extension
as if it were C, the latter doesn't.



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