From owner-freebsd-ports@freebsd.org Mon Nov 27 21:16:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E726DE8B50 for ; Mon, 27 Nov 2017 21:16:25 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 07F5E64F73 for ; Mon, 27 Nov 2017 21:16:25 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by mailman.ysv.freebsd.org (Postfix) id 0745FDE8B4F; Mon, 27 Nov 2017 21:16:25 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06E51DE8B4C for ; Mon, 27 Nov 2017 21:16:25 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA1FA64F72; Mon, 27 Nov 2017 21:16:24 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id E20945A9F15; Mon, 27 Nov 2017 21:16:16 +0000 (UTC) Date: Mon, 27 Nov 2017 21:16:16 +0000 From: Brooks Davis To: Alexey Dokuchaev Cc: Brooks Davis , ports@freebsd.org Subject: Re: RTTI support in devel/llvm40 (and maybe other llvm ports) Message-ID: <20171127211616.GA16368@spindle.one-eyed-alien.net> References: <20171110070748.GA27570@regency.nsu.ru> <20171112080319.GB76223@spindle.one-eyed-alien.net> <20171112124104.GA25053@regency.nsu.ru> <20171126161553.GA85450@regency.nsu.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <20171126161553.GA85450@regency.nsu.ru> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2017 21:16:25 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 26, 2017 at 11:15:53PM +0700, Alexey Dokuchaev wrote: > On Sun, Nov 12, 2017 at 07:41:04PM +0700, Alexey Dokuchaev wrote: > > On Sun, Nov 12, 2017 at 08:03:19AM +0000, Brooks Davis wrote: > > > On Fri, Nov 10, 2017 at 02:07:48PM +0700, Alexey Dokuchaev wrote: > > > > I've just found out that our `devel/llvm40' port comes without > > > > -DLLVM_ENABLE_RTTI=3DON on the CMAKE_ARGS. This is a regression > > > > from e.g. 3.4 times when it was enabled by default. > > > >=20 > > > > The problem is that RTTI support is required by some consumers, > > > > e.g. `graphics/openshadinglanguage' and `graphics/appleseed' > > > > (cf. https://github.com/appleseedhq/appleseed/issues/1625), > > > > but I cannot enable RTTI in those ports unless I enable it in > > > > LLVM port(s) first. > > >=20 > > > It's been a few years since we disabled it so I don't remember the > > > details of the decision. I'll look into it, but am not in a position > > > to test for breakage to other ports. > >=20 > > Well it's probably OK to expect users or maintainers of those ports > > would speak up if enabling RTTI breaks their software. :-) > >=20 > > > IIRC there were once ports that failed to build both with and > > > without so it may be that we need to wait for flavors to make this > > > change. > >=20 > > Hmm, that's weird: I'd expect it is easier to *not* use RTTI when > > one does not need it than try to find the way around when it is not > > available (which might not be possible). I also don't see why we > > should wait for FLAVORS: if needed, we can always make it optional > > (cf. existing EXTRAS LIT LLD LLDB options) but enabled by default. >=20 > Did you have a chance to make up your mind on this? (If you worry > that enabling RTTI might break some ports we can always ask portmgr@ > for an exp-run). Between travel and US holidays I've had no time for this. I'll take a look at it soon. -- Brooks --gKMricLos+KVdGMg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaHICfAAoJEKzQXbSebgfAJ24H/3Uppp2S3kDfPGq7eraOz+fH TupB8k1GSYsZgp/LXvEhgHJgGSc35H6AouPlZ7RcOaJdJ8MAiS8YZFvC0+52RnYQ yhcB2chILLbqbiFuHVVxTYGWgd20NlDFUvsNsLQoE7IFntyqCMrQGeFQ1M85y4qQ PDG1TH9DJupIZZW0sXUJcoA/ECmKSSoWcMZJ1j+AqIa3R271H7aggE4CAQWe6/IR fWLn1cxjo4YBvzFVphtXeRfeKm+L9TxocCcTyB30KOcchk5bGyjZeMnqiU/abkMh SA80bxf8P2V27GgpYrlTS22EJ+/dF0qjvzFNEMZqaF/HR/Rd3ZgEYfDDzHxlgdg= =ausL -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--