Hi
On Tuesday March 18 2014 08:54:04 James Linder wrote:
Somewhat OT so would you mind mailing me directly (unless of interest here)
I think it is (for any developer ...)
So … what did you do and how?
I don't have the exact URLs at hand, but there is a description out there on
how to get
Hi,
On Mar 16, 2014, at 18:05, Chris Jones wrote:
Well yes, of course. I was thinking as much as a test, to see if its the
optimisations that are the issue, as it is for me, than as a solution. In my
case i simply could not compile at all without -O0... without it, the memory
usage hit
On 18 Mar 2014, at 3:00 am, macports-users-requ...@lists.macosforge.org wrote:
Well yes, of course. I was thinking as much as a test, to see if its the
optimisations that are the issue, as it is for me, than as a solution. In my
case i simply could not compile at all without -O0... without
As mentioned elsewhere, I've just spent several days trying to get the Calligra
suite to build against KDE (and other dependencies) through MacPorts (and into
/opt/local for those ports not available via MacPorts, like Vc and libetonyek).
I've file a review request
Hi,
On 16 Mar 2014, at 10:14am, René J.V. Bertin rjvber...@gmail.com wrote:
As mentioned elsewhere, I've just spent several days trying to get the
Calligra suite to build against KDE (and other dependencies) through MacPorts
(and into /opt/local for those ports not available via MacPorts,
On Mar 16, 2014, at 11:51, Christopher Jones wrote:
Any reason you are using clang 3.3 though ? Have you tried a newer clang
version. Macports Clang 3.4 or 3.5 compilers ? I was unable to do this for my
issue, 3.3 was the only compiler I had available, but I would be very
interested to
Hi,
On 16 Mar 2014, at 11:03am, René J.V. Bertin rjvber...@gmail.com wrote:
On Mar 16, 2014, at 11:51, Christopher Jones wrote:
Any reason you are using clang 3.3 though ? Have you tried a newer clang
version. Macports Clang 3.4 or 3.5 compilers ? I was unable to do this for
my issue,
On Mar 16, 2014, at 05:14, René J.V. Bertin wrote:
I use clang to avoid C++ lib clashes on recent OS X versions, MacPort's own
3.3 (because 3.0 has known issues), and it is apparently not quite efficient
in its memory usage. There's 1 file in particular, gmic.cpp, that sees VM
usage grow
On Sunday March 16 2014 14:34:00 Christopher Jones wrote:
What OSX version are you running ? 3.4 and 3.5 install just fine for me on
OSX 10.9… No idea if clang 3.4 or 3.5 are supposed to work on older OSX
releases (I know the converse has problems, clang versions older than 3.3 do
not
On Sunday March 16 2014 09:56:47 Ryan Schmidt wrote:
This was an older version of clang, on older hardware with limited memory; I
haven’t noticed any such problems on my new machine which has gobs of memory
and the current versions of things.
Not even when compiling the gmic port? I don't know
I tried -O instead of -O2, didn't help. And not very surprising if indeed
it's the use of templates that's the cause of it all…
Try -O0 instead of just -O. Not quite the same and the former worked for me…
Chris
smime.p7s
Description: S/MIME cryptographic signature
On Mar 16, 2014, at 17:23, Christopher Jones wrote:
Try -O0 instead of just -O. Not quite the same and the former worked for me…
But that can also make a huge difference on performance ... rather than
providing a gmic extension that's unbearably slow, just as well not provide it
at all ;)
Hi,
On 16 Mar 2014, at 04:55 pm, René J.V. Bertin rjvber...@gmail.com wrote:
On Mar 16, 2014, at 17:23, Christopher Jones wrote:
Try -O0 instead of just -O. Not quite the same and the former worked for me…
But that can also make a huge difference on performance ... rather than
On Sun, Mar 16, 2014 at 11:33 AM, René J.V. rjvber...@gmail.com wrote:
On Sunday March 16 2014 09:56:47 Ryan Schmidt wrote: clang 3.5 and later
require C++11, and will say so if you try to install them on a system
without C++11. Effectively, this means clang 3.5 and later require OS X
10.9
On Mar 16, 2014, at 19:49, Brandon Allbery wrote:
http://trac.macports.org/wiki/FAQ#libcpp
Linux gets around this by forcing everything to the new runtime; Apple will
not ship GPL3 stuff so stuck to older gcc with the older runtime, until they
moved to clang completely in 10.9 and
On 16 Mar 2014, at 7:14pm, René J.V. Bertin rjvber...@gmail.com wrote:
On Mar 16, 2014, at 19:49, Brandon Allbery wrote:
http://trac.macports.org/wiki/FAQ#libcpp
Linux gets around this by forcing everything to the new runtime; Apple will
not ship GPL3 stuff so stuck to older gcc with
On Sunday March 16 2014 19:44:14 Christopher Jones wrote:
On 16 Mar 2014, at 7:14pm, René J.V. Bertin rjvber...@gmail.com wrote:
Its different because Apple, because of the above GPL3+ issue, will not
provide either gcc release that uses libc++, or a clang release that uses
libstdc++.
Hi,
On 16 Mar 2014, at 10:34 pm, René J.V. Bertin rjvber...@gmail.com wrote:
On Sunday March 16 2014 19:44:14 Christopher Jones wrote:
On 16 Mar 2014, at 7:14pm, René J.V. Bertin rjvber...@gmail.com wrote:
Its different because Apple, because of the above GPL3+ issue, will not
18 matches
Mail list logo
