On Fri, Sep 5, 2014 at 9:05 PM, Ryan Schmidt wrote:
On Sep 5, 2014, at 1:45 PM, René J.V. Bertin wrote:
Starting with kdevelop 4.7, C++11 is going to be required
Currently, that means the port will have require OS X 10.9 and later. Support
for 10.7 and 10.8 would involve moving all of
BTW, René,
I think I forgot to ask where you had found the iconutil utility...
Greets,
Marko
On 28 Jul 2014, at 19:37 , René J.V. Bertin rjvber...@gmail.com wrote:
Well mystère et boules de gomme as we say here ... it seems all of a
sudden my little script started having the hoped-for
Before I start, I should make something clear: Given that this mixed runtime
problem is definitively a problem on Lion and newer, I do not think MacPorts
should jump through hoops to cater to Snow Leopard. We technically do not
support Snow Leopard. In a month or two, Snow Leopard will be two
On Sep 6, 2014, at 6:51 AM, Mojca Miklavec mojca.miklavec.li...@gmail.com
wrote:
I already argued that we really need a libc++-based buildbot for 10.6-10.8.
From what I understood all we need is a fix in binary package
signature + time and resources to set up the buildbots. Once the
On Saturday September 06 2014 18:58:17 Marko Käning wrote:
BTW, René,
I think I forgot to ask where you had found the iconutil utility...
Wrote it myself ...
Cheers,
René
___
macports-users mailing list
macports-users@lists.macosforge.org
On Sat, Sep 6, 2014 at 1:10 PM, Lawrence Velázquez lar...@macports.org
wrote:
The FSF GCC ports each used to include their own runtime and support
libraries (libstdc++, libgcc_s, etc.). This caused problems when, for
example, a port using gcc44's libraries linked against a port using
On Sat, Sep 6, 2014 at 1:21 PM, Brandon Allbery allber...@gmail.com wrote:
On 10.6 or earlier already? I just wonder, this kind of situation is not
at all uncommon on Linux, how come it doesn't bite there?
You'd have to ask someone who uses Linux and knows how Linux package
managers link up
On Saturday September 06 2014 13:10:40 Lawrence Velázquez wrote:
I do not know if anyone has tried that. You're welcome to volunteer for
guinea pig duty.
Initial impression is that it works fine (and I found a trace of having
relinked a version on 10.3 or 10.4, from a self-build gcc, though
Jesus, only now I see that it is a bash script. :)
On 06 Sep 2014, at 19:20 , René J.V. Bertin rjvber...@gmail.com wrote:
On Saturday September 06 2014 18:58:17 Marko Käning wrote:
BTW, René,
I think I forgot to ask where you had found the iconutil utility...
Wrote it myself ...
On Sat, Sep 6, 2014 at 1:37 PM, René J.V. rjvber...@gmail.com wrote:
OTOH, I just noticed that the binaries Qt5 distributes are linked against
libstdc++, which I do have in /usr/lib on my 10.9 VM. A remnant of the OS
upgrade, or is it still distributed by Apple, for older software?
Question
On Sep 6, 2014, at 1:37 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Debian/Ubuntu, there are x86_64, i386 and x32 versions of libstdc++, and
they're clearly the version belonging to the default gcc version (4.8x atm on
Ubuntu 14.04). All new packages are built with that compiler, but
On 5 Sep 2014 15:35:57 -0700, Bradley Giesbrecht pixi...@macports.org wrote:
On Sep 2, 2014, at 5:38 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 2, 2014, at 3:55 PM, Murray Eisenberg wrote:
The port of php56 was just released, along with various php56 modules,
e.g.,
On Saturday September 06 2014 13:10:40 Lawrence Velázquez wrote:
Hacking alert:
Par of me now wonders if I couldn't simply replace the system runtime(s)
with the current MacPorts one(s) (C++ and/or libgcc_s). I suppose that has
been tried?
I do not know if anyone has tried that.
On Sep 6, 2014, at 7:15 AM, René J.V. Bertin wrote:
If moving to libc++ also aids upgrading MacPorts after upgrading the OS, that
just gives an additional reason ...
I don't see why it would do anything like that. Upgrading the OS to a new major
version always requires reinstalling
On Sep 6, 2014, at 4:18 AM, René J.V. Bertin wrote:
On Friday September 05 2014 22:41:42 Lawrence Velázquez wrote:
Judging from your comments, your crashes are probably caused because you're
mixing up C++ runtime libraries. Binaries compiled with MacPorts' gcc48 use
libgcc's libraries.
On Sat, Sep 6, 2014 at 6:52 PM, Ryan Schmidt ryandes...@macports.org
wrote:
Do we already record the C++ runtime in the registry with each installed
port? If not, we should do that, in addition to getting it into the binary
filenames. And just as we do for architectures, maybe we should have
Hi,
I am trying to install “apt” using macport, but it turns out that I cannot
access the address
http://distfiles.ams.nl.eu.finkmirrors.net/“, which leads to the problem:
--- Attempting to fetch apt_0.5.27.tar.gz from
http://distfiles.ams.nl.eu.finkmirrors.net/
--- Verifying checksums for
On Sat, Sep 6, 2014 at 7:38 PM, Jerry Zhang jerryzh...@gmail.com wrote:
I am trying to install “apt” using macport, but it turns out that I cannot
access the address
I would ask why? You do know that you can't use it to install Linux
software?
http://distfiles.ams.nl.eu.finkmirrors.net/“,
We can’t use “apt” to install linux software? OK, I didn’t know that before…
Thanks for the reminder.
The error is caused by the invalid link, maybe it’s because of the gfw in
China, but it doesn’t make sense to block this website…
Is there any way to install linux software in mac by the way?
On Sat, Sep 6, 2014 at 7:49 PM, Jerry Zhang jerryzh...@gmail.com wrote:
The error is caused by the invalid link, maybe it’s because of the gfw in
China, but it doesn’t make sense to block this website…
The host name is no longer registered with DNS. finkmirrors.net itself
still exists but
OK, thanks. I guess I need to setup a virtual machine...
On Sep 7, 2014, at 7:54, Brandon Allbery allber...@gmail.com wrote:
On Sat, Sep 6, 2014 at 7:49 PM, Jerry Zhang jerryzh...@gmail.com wrote:
The error is caused by the invalid link, maybe it’s because of the gfw in
China, but it doesn’t
On Sep 6, 2014, at 6:43 PM, Brandon Allbery allber...@gmail.com wrote:
http://distfiles.ams.nl.eu.finkmirrors.net/“, which leads to the problem:
I get a DNS error (NXDOMAIN) from gDNS. My guess is you're using a broken DNS
which responds to failed DNS lookups with a redirection to a
22 matches
Mail list logo
