Re: [poll]: has anyone built port:qt5-mac in universal or 32bit mode?

2015-03-04 Thread Ryan Schmidt
On Mar 4, 2015, at 7:45 AM, René J.V. Bertin wrote: > The question is all in the subject: has anyone built port:qt5-mac in > universal or 32bit mode, and if so, what Qt version is/was that? > > I'm most interested in success stories, though confirmation that it doesn't > work would be of inter

Re: php53 ipv6 and file_get_contents getaddrinfo failed

2015-03-04 Thread Jeremy Lavergne
On March 4, 2015 8:22:01 PM EST, Ryan Schmidt wrote: > >On Mar 4, 2015, at 9:48 AM, Jim Hu wrote: > >> New to the listserv and sorry if this is an old issue that I couldn't >find an answer to via Google. >> >> I've been running an older OSX 10.6 (Snow Leopard) XServe server for >some time. It's a

Re: php53 ipv6 and file_get_contents getaddrinfo failed

2015-03-04 Thread Ryan Schmidt
On Mar 4, 2015, at 9:48 AM, Jim Hu wrote: > New to the listserv and sorry if this is an old issue that I couldn't find an > answer to via Google. > > I've been running an older OSX 10.6 (Snow Leopard) XServe server for some > time. It's an older Mac that can't be updated further. I have MacPor

Re: Port install fails for curl, requires gcc4.2

2015-03-04 Thread Ryan Schmidt
On Mar 4, 2015, at 6:34 PM, Jeremy Lavergne wrote: > On March 4, 2015 7:04:04 PM EST, Ryan Schmidt wrote: > >> Great, glad it worked. 1 GB RAM should be ok for compiling most ports; >> my PowerPC test machine has only 512 MB. But your 500 MHz processor is >> slow. It may be the fastest G3 Apple

Re: Port install fails for curl, requires gcc4.2

2015-03-04 Thread Jeremy Lavergne
On March 4, 2015 7:04:04 PM EST, Ryan Schmidt wrote: >On Mar 4, 2015, at 11:29 AM, Tom Emmert wrote: >> >> 20+ hrs later, DONE! No swapping that I could see. I just never >imagined that it would take that long! My apologies for not digging >deeper the first time! Now, let's see how long wires

Re: Port install fails for curl, requires gcc4.2

2015-03-04 Thread Ryan Schmidt
On Mar 4, 2015, at 11:29 AM, Tom Emmert wrote: > > 20+ hrs later, DONE! No swapping that I could see. I just never imagined > that it would take that long! My apologies for not digging deeper the first > time! Now, let's see how long wireshark takes! Thank you very much for your > help, To

Re: error while "building uhd"

2015-03-04 Thread Michael Dickens
Hi Jim - I'm going to work with you off-list since this is a 32/64 bit issue & will require some programming work on my part and testing on your part. If we come up with something relevant to this list, I'll email a summary. - MLD On Wed, Mar 4, 2015, at 06:27 PM, Jim Goudie wrote: > OS X 10.6.8 >

Re: error while "building uhd"

2015-03-04 Thread Jim Goudie
Hello Rainer, OS X 10.6.8 Xcode 3.2 (I haven't found an upgrade for this, yet... 3.2.6?) Yes... it is a 32-bit Macbook Pro, 2 Ghz Intel Core Duo; 2 GB ram Jim On Mar 4, 2015, at 6:07 PM, Rainer Müller wrote: > On 2015-03-04 23:09, Jim Goudie wrote: >> Office:~ Jim$ vim >> /opt/local/var/macpor

Re: error while "building uhd"

2015-03-04 Thread Rainer Müller
On 2015-03-04 23:09, Jim Goudie wrote: > Office:~ Jim$ vim > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_uhd/uhd/main.log > > :info:build > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ta

error while "building uhd"

2015-03-04 Thread Jim Goudie
Hello... I was installing Gqrx, a software-defined radio program. The install took much longer than I expected, but then this is my first experience with Macports... I didn't know what to expect. When it finally stopped, it ended with an error while "building uhd" (see below). Any help unde

Re: Port install fails for curl, requires gcc4.2

2015-03-04 Thread Brandon Allbery
On Wed, Mar 4, 2015 at 12:29 PM, Tom Emmert wrote: > 20+ hrs later, DONE! No swapping that I could see. I just never imagined > that it would take that long! My apologies for not digging deeper the > first time! Now, let's see how long wireshark takes! Thank you very much > for your help, To

Re: Selfupdate doesn't work - solved

2015-03-04 Thread Dave Horsfall
On Wed, 4 Mar 2015, Jim Goudie wrote: > Then I got to thinking... what else would block it? I logged in to my > router and found it has a firewall as well. I turned it off, and then > the command worked! I'm finding that a lot of consumer routers have conservative firewalls by default; this

Re: Port install fails for curl, requires gcc4.2

2015-03-04 Thread Tom Emmert
20+ hrs later, DONE! No swapping that I could see. I just never imagined that it would take that long! My apologies for not digging deeper the first time! Now, let's see how long wireshark takes! Thank you very much for your help, Tom On Mar 3, 2015, at 15:40, t...@qx.net wrote: >>> On

php53 ipv6 and file_get_contents getaddrinfo failed

2015-03-04 Thread Jim Hu
New to the listserv and sorry if this is an old issue that I couldn't find an answer to via Google. I've been running an older OSX 10.6 (Snow Leopard) XServe server for some time. It's an older Mac that can't be updated further. I have MacPorts running on it, but until recently I was using the

Re: Problem configuring libcaca

2015-03-04 Thread Tom Gederberg
I’m on Yosemite. I always do a “sudo port -v selfupdate” followed by “sudo port -v upgrade outdated”. I just did a “sudo port clean libcaca” and started it again. It is again hanging up at the same place (though it has only been hung for a few minutes - I’ll let it go and see if it gets any

[poll]: has anyone built port:qt5-mac in universal or 32bit mode?

2015-03-04 Thread René J . V . Bertin
Hello, The question is all in the subject: has anyone built port:qt5-mac in universal or 32bit mode, and if so, what Qt version is/was that? I'm most interested in success stories, though confirmation that it doesn't work would be of interest too. Thanks, René _

Selfupdate doesn't work - solved

2015-03-04 Thread Jim Goudie
Hello... I tried running this command with the OS X firewall off: rsync rsync://rsync.macports.org/release/ It timed out as usual. Then I got to thinking... what else would block it? I logged in to my router and found it has a firewall as well. I turned it off, and then the command worked!