On 3/6/2018 7:47 AM, Stuart Henderson wrote:
> On 2018/03/06 21:32, Jonathan Gray wrote:
>> On Sat, Feb 17, 2018 at 11:12:44PM +1100, Jonathan Gray wrote:
>>> On Thu, Feb 15, 2018 at 05:08:56PM +, Stuart Henderson wrote:
On 2018/02/15 11:19, Brian Callahan wrote:
> On 02/15/18 10:02,
On 2018/03/06 21:32, Jonathan Gray wrote:
> On Sat, Feb 17, 2018 at 11:12:44PM +1100, Jonathan Gray wrote:
> > On Thu, Feb 15, 2018 at 05:08:56PM +, Stuart Henderson wrote:
> > > On 2018/02/15 11:19, Brian Callahan wrote:
> > > >
> > > > On 02/15/18 10:02, Jonathan Gray wrote:
> > > > > Build
On Sat, Feb 17, 2018 at 11:12:44PM +1100, Jonathan Gray wrote:
> On Thu, Feb 15, 2018 at 05:08:56PM +, Stuart Henderson wrote:
> > On 2018/02/15 11:19, Brian Callahan wrote:
> > >
> > > On 02/15/18 10:02, Jonathan Gray wrote:
> > > > Build libLLVM.so and link tools with it.
> > > >
> > > > Th
On Thu, Feb 15, 2018 at 05:08:56PM +, Stuart Henderson wrote:
> On 2018/02/15 11:19, Brian Callahan wrote:
> >
> > On 02/15/18 10:02, Jonathan Gray wrote:
> > > Build libLLVM.so and link tools with it.
> > >
> > > This seems to be the way almost all Linux distributions and BSDs
> > > ship LLV
On 2018/02/15 11:19, Brian Callahan wrote:
>
> On 02/15/18 10:02, Jonathan Gray wrote:
> > Build libLLVM.so and link tools with it.
> >
> > This seems to be the way almost all Linux distributions and BSDs
> > ship LLVM and is what Mesa expects.
> >
> > Use the documented cmake var for RTTI while
On 02/15/18 10:02, Jonathan Gray wrote:
Build libLLVM.so and link tools with it.
This seems to be the way almost all Linux distributions and BSDs
ship LLVM and is what Mesa expects.
Use the documented cmake var for RTTI while here.
Any reason not to use the SHARED_LIBS facility of ports for