On Sunday March 16 2014 18:42:53 you wrote:
> Hi René - Are you saying that you removed the linking with "-framework
> Carbon" from when QtGui is linked and that worked? Or, are you talking
No, unfortunately I didn't test that.
> about for some project that's using QtGui via QMake, for which rem
Hi,
> On 16 Mar 2014, at 10:34 pm, René J.V. Bertin wrote:
>
>> On Sunday March 16 2014 19:44:14 Christopher Jones wrote:
>>
>>> On 16 Mar 2014, at 7:14pm, René J.V. Bertin wrote:
>>
>>
>> Its different because Apple, because of the above GPL3+ issue, will not
>> provide either gcc release
Hi René - Are you saying that you removed the linking with "-framework
Carbon" from when QtGui is linked and that worked? Or, are you talking
about for some project that's using QtGui via QMake, for which removing
the linking with Carbon worked? I've never tried the former, and the
latter could e
On Sunday March 16 2014 19:44:14 Christopher Jones wrote:
>
> On 16 Mar 2014, at 7:14pm, René J.V. Bertin 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++. Linux, being GP
Yeah, that was all I meant by saying "on Mountain Lion and higher" was that
it was conditionally declared like that; I did *not* mean to imply that I
was on Mountain Lion myself... (I am actually still on Snow Leopard so
`port notes gdb-apple` says the same thing for me as it did for Ian; I only
kn
On Mar 16, 2014, at 13:43, René J.V. Bertin wrote:
> Before I first installed MacPorts, I created a symlink
> ln -s /Volumes/WorkDisk/MacPorts /opt/local
>
> and then let the installer do its thing. Or maybe I installed normally and
> then moved /opt/local to WorkDisk/MacPorts before creating
On 16 Mar 2014, at 7:14pm, René J.V. Bertin 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 the older ru
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 swi
You might consider checking that the destination of your symlink has
appropriate permissions. My guess is something over there no longer matches up.
Also, like many programs started as root, MacPorts drops root permissions when
they aren’t needed.
On Mar 16, 2014, at 14:43, René J.V. Bertin wr
On Sun, Mar 16, 2014 at 11:33 AM, René J.V. 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 Mavericks or late
Before I first installed MacPorts, I created a symlink
ln -s /Volumes/WorkDisk/MacPorts /opt/local
and then let the installer do its thing. Or maybe I installed normally and then
moved /opt/local to WorkDisk/MacPorts before creating the symlink, I cannot
remember.
Anyway, there came a moment wh
Hi,
> On 16 Mar 2014, at 04:55 pm, "René J.V. Bertin" 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
> providing a gm
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 ;)
An
> 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 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 kno
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 i
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 gr
Hi,
On 16 Mar 2014, at 11:03am, René J.V. Bertin 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, 3.3 was the on
On Sun, Mar 16, 2014 at 7:41 AM, wrote:
> On 16 Mar 2014, at 12:12 , Ian Wadham wrote:> No. I
> have never had anything to do with gdb-apple before.
> > I did a "port selfupdate" about 14 hours ago. Followed by a
> > "port upgrade outdated". After that I tried to find the notes, but
> > failed.
I see that Qt4-mac links against Carbon.framework (in QtGui.dylib) and even
exports the dependency via qmake. But the times I tried to link without
-framework Carbon everything worked just fine.
Is this dependency still valid, and is it really one that needs to be promoted
from the Qt frameworks
On 16 Mar 2014, at 12:12 , Ian Wadham wrote:
> Thanks, Marko. Before I go ahead and try it, should that second
> last line say "-p", not "sp"? I am new to plists … :-)
If it says so it wants it like that.
> No. I have never had anything to do with gdb-apple before.
> I did a "port selfupdate" a
On 16/03/2014, at 7:28 PM, mk-macpo...@techno.ms wrote:
> On 16 Mar 2014, at 09:00 , Ian Wadham wrote:
>> Thanks, Eric, but I could not find any notes on gdb-apple. I tried
>> installing
>> it first, but still got:
>
> here on my install I see this:
> ---
> $ port notes gdb-apple
> gdb-apple h
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 10:14am, René J.V. Bertin 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, like Vc and
> lib
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 (https://git.reviewboard.kde.or
Hi Ian,
On 16 Mar 2014, at 09:00 , Ian Wadham wrote:
> Thanks, Eric, but I could not find any notes on gdb-apple. I tried installing
> it first, but still got:
here on my install I see this:
---
$ port notes gdb-apple
gdb-apple has the following notes:
You will need to make sure
/System/Libr
On 16/03/2014, at 12:05 AM, Eric Gallager wrote:
> The only thing I know about taskgated is that you have to modify its launchd
> plist (by adding the '-p' option) to allow gdb to control other processes (on
> Mountain Lion and higher you can see this with `port notes gdb-apple`)...
> Have you d
27 matches
Mail list logo
