Re: Is any clang version known to work in PPC/Tiger?

2016-04-03 Thread Mojca Miklavec
On 4 April 2016 at 00:44, César wrote: > On 3 de April 2016, Mojca Miklavec wrote: >> On 3 April 2016 at 22:13, César wrote: >> > I've read that clang/llvm have been improving their PPC support over the >> > years. But, is any version known to build? >> >> I have clang-3.4 installed on 10.5 PPC.

Re: About mozjs24 being built

2016-04-03 Thread Eneko Gotzon
On Sun, Apr 3, 2016 at 4:53 PM, Brandon Allbery wrote: > xorg-server and xinit ports If I recall correctly xinit is already included inside the xorg-server port. -- Eneko Gotzon Ares enekogot...@gmail.com ___ macports-users

Re: Is any clang version known to work in PPC/Tiger?

2016-04-03 Thread César
On 3 de April 2016, Mojca Miklavec wrote: > On 3 April 2016 at 22:13, César wrote: > > I've read that clang/llvm have been improving their PPC support over the > > years. But, is any version known to build? > > I have clang-3.4 installed on 10.5 PPC. Installing the latest

Re: Is any clang version known to work in PPC/Tiger?

2016-04-03 Thread Mojca Miklavec
On 3 April 2016 at 22:13, César wrote: > I've read that clang/llvm have been improving their PPC support over the > years. But, is any version known to build? I have clang-3.4 installed on 10.5 PPC. Installing the latest versions requires quite a bit of bootstrapping headaches:

Is any clang version known to work in PPC/Tiger?

2016-04-03 Thread César
I've read that clang/llvm have been improving their PPC support over the years. But, is any version known to build? And, can it be used in production, or there's the risk of getting corrupted/nonworking binaries? Thanks! César ___ macports-users

Re: About mozjs24 being built

2016-04-03 Thread Joshua Root
On 2016-4-4 01:46 , Clemens Lang wrote: Hi Josh, On Mon, Apr 04, 2016 at 01:06:50AM +1000, Joshua Root wrote: MPL 2.0 is GPL compatible only by way of an optional clause that allows relicensing under the GPL. Some software is under MPL-2 but has an "Incompatible With Secondary Licenses"

Re: About mozjs24 being built

2016-04-03 Thread Clemens Lang
Hi Josh, On Mon, Apr 04, 2016 at 01:06:50AM +1000, Joshua Root wrote: > MPL 2.0 is GPL compatible only by way of an optional clause that > allows relicensing under the GPL. Some software is under MPL-2 but has > an "Incompatible With Secondary Licenses" notice. If a port uses the > version of

Re: About mozjs24 being built

2016-04-03 Thread Andrea Giammarchi
It looks like installing `xorg-server` and `xinit` won't solve the problem; I had to install XQuartz a part. Since that's the default backend for macports Gtk3, wouldn't make sense to have it installed as Gtk3 dependency? Or, at least, as `gjs` one. Anyway, thanks for the hint. Best Regards On

Re: About mozjs24 being built

2016-04-03 Thread Joshua Root
On 2016-4-4 00:45 , Clemens Lang wrote: Hi, On Sun, Apr 03, 2016 at 04:05:02PM +0200, Clemens Lang wrote: Doesn't seem like it will: $ port_binary_distributable.tcl -v mozjs24 "mozjs24" is not distributable because its license "mpl" conflicts with license "GPL-3+" of dependency "gdbm"

Re: About mozjs24 being built

2016-04-03 Thread Brandon Allbery
On Sun, Apr 3, 2016 at 10:53 AM, Brandon Allbery wrote: > Install XQuartz I should mention that MacPorts defaults to building gtk with +x11 because many gtk-using programs either do not build or do not work properly with gtk +quartz. If you want to try it anyway, you would

Re: About mozjs24 being built

2016-04-03 Thread Clemens Lang
Hi, On Sun, Apr 03, 2016 at 03:49:01PM +0100, Andrea Giammarchi wrote: > ``` > gjs -c 'imports.gi.Gtk.init(null);' > > (gjs 999): Gtk-WARNING **: cannot open display: > ``` That looks like you don't have XQuartz installed. MacPorts' copy of Gtk uses an X11 backend, which requires that you have

Re: About mozjs24 being built

2016-04-03 Thread Brandon Allbery
On Sun, Apr 3, 2016 at 10:49 AM, Andrea Giammarchi < andrea.giammar...@gmail.com> wrote: > I've also noticed, after successfully installing `gjs`, that it doesn't > work anyway. > > ``` > gjs -c 'imports.gi.Gtk.init(null);' > > (gjs 999): Gtk-WARNING **: cannot open display: > ``` > Install

Re: About mozjs24 being built

2016-04-03 Thread Andrea Giammarchi
Thanks! I've also noticed, after successfully installing `gjs`, that it doesn't work anyway. ``` gjs -c 'imports.gi.Gtk.init(null);' (gjs 999): Gtk-WARNING **: cannot open display: ``` This one also works on homebrew (I'm trying to test Gtk+ configuration through both installers) Any idea how

Re: About mozjs24 being built

2016-04-03 Thread Clemens Lang
Hi, On Sun, Apr 03, 2016 at 04:05:02PM +0200, Clemens Lang wrote: > Doesn't seem like it will: > > $ port_binary_distributable.tcl -v mozjs24 > "mozjs24" is not distributable because its license "mpl" conflicts with > license "GPL-3+" of dependency "gdbm" Actually, mozjs24's license is

Re: About mozjs24 being built

2016-04-03 Thread Clemens Lang
Hi, On Sun, Apr 03, 2016 at 02:24:28PM +0100, Andrea Giammarchi wrote: > Installing `gjs` brings in a lot of modules and `mozjs24` is one of > these. > > There are pre-built binaries via homebrew and `mozjs24` has been > around for very long time so it surprises me it needs to be built via >

About mozjs24 being built

2016-04-03 Thread Andrea Giammarchi
Hi everyone! Installing `gjs` brings in a lot of modules and `mozjs24` is one of these. There are pre-built binaries via homebrew and `mozjs24` has been around for very long time so it surprises me it needs to be built via macports. It's also actually the only one that needs this step,

Re: Unable to read CDs

2016-04-03 Thread Paul Rands
Thanks to everyone who has helped so far. A fix for this does sound way over my head at the moment. Might just have to stick with a VM and use flow thru settings to access the drive. Paul Rands paul00...@gmail.com On 3/04/2016 03:21 , Brandon Allbery wrote: On Sat, Apr 2, 2016 at 12:52 PM,

Re: Checksum fail for ghostscript update

2016-04-03 Thread Kurt Pfeifle
On Sun, Apr 3, 2016 at 3:17 AM, Clemens Lang wrote: > > On Sat, Apr 02, 2016 at 10:59:11PM +0200, Kurt Pfeifle wrote: > > Maybe I can convince MacPorts developers to change where they fetch > > their own sources? > > I'm not sure if it indeed is so -- but the last sentence