On Thu, Nov 5, 2015 at 6:25 AM, René J.V. wrote:
> Out of pure curiosity, does anyone know what happens when an application
> links to ncurses6 and one of its dependencies to a (runtime) library from
> ncurses5?
If it's using terminfo level stuff only and doesn't share it
On Thursday November 05 2015 06:37:04 Brandon Allbery wrote:
[sorry, should have gone to the list immediately]
> If it's using terminfo level stuff only and doesn't share it around (e.g.
> most uses of readline, which doesn't expose any curses/terminfo
> interfaces), it should work fine if it
Hi,
Out of pure curiosity, does anyone know what happens when an application links
to ncurses6 and one of its dependencies to a (runtime) library from ncurses5?
R.
___
macports-users mailing list
macports-users@lists.macosforge.org
> I got tired of seeing that bloody spinning beach-ball…
This spinning beach ball seems to be a FEATURE of El Capitan — having nothing
to do with Mac Ports.
Everything causes it to happen.
T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.11.1
# Macmini6,1
The actual update itself was more or less seamless; details can be found
over on //horsfall.org/capitan .
Now, did Macports really feel the need to re-compile the world, over three
days? I got tired of seeing that bloody spinning beach-ball... Why did
it not merely retrieve pre-built
On 2015-11-05 21:00, Dave Horsfall wrote:
> Now, did Macports really feel the need to re-compile the world, over three
> days? I got tired of seeing that bloody spinning beach-ball... Why did
> it not merely retrieve pre-built binaries, as usual?
As of now, we do not have a buildbot instance
On Thu, Nov 5, 2015 at 3:00 PM, Dave Horsfall wrote:
> Why did
> it not merely retrieve pre-built binaries, as usual?
Apple hasn't yet provisioned the build environment required for El
Capitan binaries. There's a ticket somewhere tracking this issue, but
I haven't seen any