Date: Mon, 27 Nov 2017 21:16:16 +0000 From: Brooks Davis <brooks@freebsd.org> To: Alexey Dokuchaev <danfe@nsu.ru> Cc: Brooks Davis <brooks@freebsd.org>, ports@freebsd.org Subject: Re: RTTI support in devel/llvm40 (and maybe other llvm ports) Message-ID: <20171127211616.GA16368@spindle.one-eyed-alien.net> In-Reply-To: <20171126161553.GA85450@regency.nsu.ru> References: <20171110070748.GA27570@regency.nsu.ru> <20171112080319.GB76223@spindle.one-eyed-alien.net> <20171112124104.GA25053@regency.nsu.ru> <20171126161553.GA85450@regency.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171127211616.GA16368>