Re: clang 3.4 can't be configured (part of a selfupdate)

Hey Pat, FYI, I just finished wiping my SL VM and going through the motions yesterday. clang-3.8 seems to have some issues on the older versions of OS X, so I've updated the page to recommend staying at 3.7 for now. I suggest you edit macports.conf and just remove macports-clang-3.8 from the

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 4, 2016, at 10:23, [ftp83plus] wrote: > > Thanks to all, it seems to have worked so far until Step 8. I noticed Step 9 > disappeared in the page refresh. Was it unnecessary? It was made obsolete by libcxx becoming +universal by default, so there was no need to

Re: clang 3.4 can't be configured (part of a selfupdate)

Thanks to all, it seems to have worked so far until Step 8. I noticed Step 9 disappeared in the page refresh. Was it unnecessary? Pat El 2016-08-04, a las 00:00, Jeremy Huddleston Sequoia escribió: > Ah. Reordered. > > Do this first to pick up the +llvm38 variants of cctools and ld64: > >

Re: clang 3.4 can't be configured (part of a selfupdate)

Ah. Reordered. Do this first to pick up the +llvm38 variants of cctools and ld64: sudo port -v -n upgrade --enforce-variants cctools -llvm34 sudo port -v upgrade --enforce-variants ld64 -llvm34 > On Aug 3, 2016, at 20:16, [ftp83plus] wrote: > > Thanks, > > that

Re: clang 3.4 can't be configured (part of a selfupdate)

Thanks, that worked, partly. Now, on Step 7, I get: http://pastebin.com/dNRW6g2c How to solve it? El 2016-08-03, a las 12:09, Jeremy Huddleston Sequoia escribió: > >> On Aug 3, 2016, at 07:36, [ftp83plus] wrote: >> >> Hmmm, and how would I install the +universal

Re: clang 3.4 can't be configured (part of a selfupdate)

Pat, I seemed to have none of these issues... but I installed libomp-universal on my x86_64 compatible mac. libomp @3.8.1_0-universal (active) platform='darwin 10' archs='x86_64' And so it remains. That seems to have been the main reason I didn't run into any of the issues you have run

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 3, 2016, at 07:36, [ftp83plus] wrote: > > Hmmm, and how would I install the +universal variant of libcxx wile avoiding > the python-related bug? sudo port -v -f uninstall libcxxabi libcxx sudo port -v -s install libcxx > > PAt > > El 2016-08-01, a las 22:13,

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 3, 2016, at 9:36 AM, [ftp83plus] wrote: > > Hmmm, and how would I install the +universal variant of libcxx wile avoiding > the python-related bug? Use the +readline variant. ___ macports-users mailing list

Re: clang 3.4 can't be configured (part of a selfupdate)

Hmmm, and how would I install the +universal variant of libcxx wile avoiding the python-related bug? PAt El 2016-08-01, a las 22:13, Jeremy Huddleston Sequoia escribió: > >> On Aug 1, 2016, at 4:05 PM, Ken Cunningham >> wrote: >> >> Interestingly, I just

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 1, 2016, at 4:05 PM, Ken Cunningham > wrote: > > Interestingly, I just went to update my libmacho and libunwind to the > universal variants given this conversation (already did the cxx and cxxabi > ports) -- but oddly, perhaps, this seemingly fully

Re: clang 3.4 can't be configured (part of a selfupdate)

Interestingly, I just went to update my libmacho and libunwind to the universal variants given this conversation (already did the cxx and cxxabi ports) -- but oddly, perhaps, this seemingly fully functional 10.6.8 /libc++ system with clang-3.8, all installed through macports, has neither

Re: clang 3.4 can't be configured (part of a selfupdate)

El 2016-08-01, a las 16:01, Jeremy Huddleston Sequoia escribió: > >> On Aug 1, 2016, at 11:55, [ftp83plus] wrote: >> >> >> El 2016-08-01, a las 02:49, Ryan Schmidt escribió: >> >>> On Aug 1, 2016, at 00:40, [ftp83plus] wrote: El 2016-07-31, a las 16:30, Ryan

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 1, 2016, at 11:55, [ftp83plus] wrote: > > > El 2016-08-01, a las 02:49, Ryan Schmidt escribió: > >> On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >>> >>> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: Could you also show us the CMakeOutput.log?

Re: clang 3.4 can't be configured (part of a selfupdate)

El 2016-08-01, a las 02:49, Ryan Schmidt escribió: > On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >> >> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >>> >>> Could you also show us the CMakeOutput.log? >> >> Sure, here it is: >> CMakeOutput.log >> http://pastebin.com/XZ3WHA0F > > This

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Aug 1, 2016, at 01:58, Ryan Schmidt wrote: > > > On Aug 1, 2016, at 3:07 AM, Jeremy Huddleston Sequoia wrote: >> >> On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: >>> >>> ld: warning: ignoring file /usr/lib/libc++.dylib, file was built for >>> unsupported file

Re: clang 3.4 can't be configured (part of a selfupdate)

On Aug 1, 2016, at 3:07 AM, Jeremy Huddleston Sequoia wrote: > > On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: >> >> ld: warning: ignoring file /usr/lib/libc++.dylib, file was built for >> unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 >> 0x 0 0x 0 0x 6 0x 0 0x 0

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 31, 2016, at 23:49, Ryan Schmidt wrote: > > On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >> >> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >>> >>> Could you also show us the CMakeOutput.log? >> >> Sure, here it is: >> CMakeOutput.log >>

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 31, 2016, at 23:44, Ryan Schmidt wrote: > > On Aug 1, 2016, at 00:44, Jeremy Huddleston Sequoia wrote: >> > >> On Jul 31, 2016, at 22:40, [ftp83plus] wrote: >>> >>> @Jeremy, I never explicitly selected clang-3.3, it is automatically >>> installed during

Re: clang 3.4 can't be configured (part of a selfupdate)

On Aug 1, 2016, at 00:40, [ftp83plus] wrote: > > El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >> >> Could you also show us the CMakeOutput.log? > > Sure, here it is: > CMakeOutput.log > http://pastebin.com/XZ3WHA0F This again shows: ld: warning: ignoring file /usr/lib/libc++.dylib, file

Re: clang 3.4 can't be configured (part of a selfupdate)

On Aug 1, 2016, at 00:44, Jeremy Huddleston Sequoia wrote: > > On Jul 31, 2016, at 22:40, [ftp83plus] wrote: >> >> @Jeremy, I never explicitly selected clang-3.3, it is automatically >> installed during Step 4 of >> https://trac.macports.org/wiki/LibcxxOnOlderSystems. It is a dependency of

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 31, 2016, at 22:40, [ftp83plus] wrote: > > > El 2016-07-31, a las 16:30, Ryan Schmidt escribió: > >> On Jul 31, 2016, at 14:01, [ftp83plus] wrote: >> >>> libomp still fails to build as a dependency of clang 3.8 installation as >>> shown in Step 4: >>> >>>

Re: clang 3.4 can't be configured (part of a selfupdate)

El 2016-07-31, a las 16:30, Ryan Schmidt escribió: > On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > >> libomp still fails to build as a dependency of clang 3.8 installation as >> shown in Step 4: >> >> main.log from >>

Re: clang 3.4 can't be configured (part of a selfupdate)

And why is the macports user's home directory not present: • :info:configure 2016-07-31 04:52:55.132 sw_vers[18075:903] CFPreferences: user home directory at file://localhost/opt/local/var/macports/home/ is unavailable. User domains will be volatile. Did you delete it, or was it never

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 31, 2016, at 13:30, Ryan Schmidt wrote: > > On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > >> libomp still fails to build as a dependency of clang 3.8 installation as >> shown in Step 4: >> >> main.log from >>

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 31, 2016, at 14:01, [ftp83plus] wrote: > > libomp still fails to build as a dependency of clang 3.8 installation as > shown in Step 4: > > main.log from > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/ >

Re: clang 3.4 can't be configured (part of a selfupdate)

Hello all, libomp still fails to build as a dependency of clang 3.8 installation as shown in Step 4: main.log from /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_libomp/libomp/ http://pastebin.com/9YwFQusZ This is earlier than Step

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 30, 2016, at 11:20 PM, Jeremy Huddleston Sequoia > wrote: > > >> On Jul 30, 2016, at 18:16, Ryan Schmidt wrote: >> >> >>> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >>> El 29 jul 2016, a las 16:45, Lawrence Velázquez

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 30, 2016, at 18:16, Ryan Schmidt wrote: > > >> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >> >>> El 29 jul 2016, a las 16:45, Lawrence Velázquez escribió: >>> On Jul 29, 2016, at 1:35 AM, Ken Cunningham wrote: >

Re: clang 3.4 can't be configured (part of a selfupdate)

Maybe, indeed. I just realized my package installer (and my OpenSCAD application) are x86_64 specific. And some 10.6.8 systems can't run that. I have a lot to learn. Ken On 2016-07-30, at 6:16 PM, Ryan Schmidt wrote: > >> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: >> >>> El 29 jul

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 30, 2016, at 7:58 AM, [ftp83plus] wrote: > >> El 29 jul 2016, a las 16:45, Lawrence Velázquez escribió: >> >>> On Jul 29, 2016, at 1:35 AM, Ken Cunningham wrote: >>> /opt/local/bin/clang++-mp-3.3 -pipe -Os -stdlib=libc++ -arch i386 -mmacosx-version-min=10.6

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 30, 2016, at 7:24 PM, [ftp83plus] wrote: > > Should I simply let step 2 as it was, not > sudo port -v install libcxx +universal > > but > > sudo port -v install libcxx > > like I did when it failed the first time? I doubt that has anything to do with the

Re: clang 3.4 can't be configured (part of a selfupdate)

Should I simply let step 2 as it was, not sudo port -v install libcxx +universal but sudo port -v install libcxx like I did when it failed the first time? Thanks, Pat El 2016-07-30, a las 18:01, Lawrence Velázquez escribió: > On Jul 30, 2016, at 1:57 PM, [ftp83plus]

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 30, 2016, at 1:57 PM, [ftp83plus] wrote: > Python 27 fails to build: http://pastebin.com/zJZM4vM8 and log: > http://pastebin.com/0L1rTQZP > > What is the issue this time? https://trac.macports.org/ticket/51891 vq ___

Re: clang 3.4 can't be configured (part of a selfupdate)

Thanks Lawrence, so I did: Step 1: OK as per https://guide.macports.org/chunked/installing.macports.uninstalling.html Step 2: MODIFIED: sudo port -v install libcxx +universal Python 27 fails to build: http://pastebin.com/zJZM4vM8 and log: http://pastebin.com/0L1rTQZP What is the issue this

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 30, 2016, at 8:58 AM, [ftp83plus] wrote: > So should I rebuild libcxx +universal variant first before performing > Step 4 of the LibcxxOnOlderSystems? Yes, unless you can figure out why libomp is being installed +universal and prevent that. vq

Re: clang 3.4 can't be configured (part of a selfupdate)

> El 29 jul 2016, a las 16:45, Lawrence Velázquez > escribió: > >> On Jul 29, 2016, at 1:35 AM, Ken Cunningham >> > >> wrote: >> >> Hi, >> >> There are many here smarter than me, but it would see

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 1:35 AM, Ken Cunningham > wrote: > > Hi, > > There are many here smarter than me, but it would see your error is > here: > >> /opt/local/bin/clang++-mp-3.3 -pipe -Os -stdlib=libc++ -arch i386 >> -mmacosx-version-min=10.6

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 4:05 PM, Ken Cunningham > wrote: > > I believe macports automatically sets build_arch to the proper value > depending on your hardware . > >

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 10:57 AM, [ftp83plus] wrote: > > And why would it use clang-3.3 when it's explicitly told to use clang 3.4? The build failure is in libomp, which has the following compiler whitelist: # According to documentation builds with clang >= 3.3

Re: clang 3.4 can't be configured (part of a selfupdate)

> > I followed the instructions for full uninstall: > https://guide.macports.org/chunked/installing.macports.uninstalling.html That is infinitely better, and gets all the other bits and pieces that might cause trouble. > > this is the only occurence of "build_arch" in macports.conf, and is

Re: clang 3.4 can't be configured (part of a selfupdate)

Some more: El 2016-07-29, a las 11:56, Ken Cunningham escribió: > >> 2- correct the macports.conf to replace x86 by x86_64 architecture > > No, don't think so. My macports.conf has > > build_arch x86_64 > > near the top -- I installed macports two years ago. I can't recall at the >

Re: clang 3.4 can't be configured (part of a selfupdate)

Thanks Ken, this is the only occurence of "build_arch" in macports.conf, and is commented out, so shouldn't be taken into account: #build_arch i386 Comes from the most recent install of MacPorts. Should I replace it by build_archx86_64 ? El 2016-07-29, a las

Re: clang 3.4 can't be configured (part of a selfupdate)

> > Move your opt folder out of the way > > sudo mv /opt /opt-junked > Oh dear - this step is not quite right - I'm very sorry about that. There could be (and probably are) other things in your /opt folder that you don't want to move. If you did that, please move it back ( sudo mv

Re: clang 3.4 can't be configured (part of a selfupdate)

On 2016-07-29, at 7:57 AM, [ftp83plus] wrote: > SoI would have to 0- remove said files 1- reinstall MacPorts, Yes > 2- correct the macports.conf to replace x86 by x86_64 architecture No, don't think so. My macports.conf has build_arch x86_64 near the top -- I installed macports two

Re: clang 3.4 can't be configured (part of a selfupdate)

For the architectures, I have this in macports.conf: # CPU architecture to target. Supported values are "ppc", "ppc64", # "i386", and "x86_64". Defaults to: # - OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386". # - OS X 10.6 and later: "x86_64" on Intel 64, otherwise "i386". #build_arch

Re: clang 3.4 can't be configured (part of a selfupdate)

ot wheel 431040 24 Nov 2015 libc++abi.dylib > > Move your opt folder out of the way > > sudo mv /opt /opt-junked > > reinstall macports from the package > > do a sudo port selfupdate (I think it happens anyway when you install). > > And then go straight to the lib

Re: clang 3.4 can't be configured (part of a selfupdate)

++.1.dylib lrwxr-xr-x 1 root wheel 14 28 Jul 20:36 libc++.dylib -> libc++.1.dylib -rwxr-xr-x 1 root wheel 431040 24 Nov 2015 libc++abi.dylib Move your opt folder out of the way sudo mv /opt /opt-junked reinstall macports from the package do a sudo port selfupdate (I think it happ

Re: clang 3.4 can't be configured (part of a selfupdate)

Hi, There are many here smarter than me, but it would see your error is here: /opt/local/bin/clang++-mp-3.3 -pipe -Os -stdlib=libc++ -arch i386 -mmacosx-version-min=10.6 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names

Re: clang 3.4 can't be configured (part of a selfupdate)

Thanks Ken, I am currently attempting the Install Libcxx on Older Systems procedure as it was how you solved it. However, it fails at step 4 after hours trying to compile: > -- Configuring incomplete, errors occurred! > See also >

Re: clang 3.4 can't be configured (part of a selfupdate)

ote: >> I am currently attempting a "port selfupdate" operation before installing two >> ports I'd like to test. >> >> However, it fails for a reason I don't understand: >> [...] > > Also interesting might be the output of > > `port installed 'ld64

Re: clang 3.4 can't be configured (part of a selfupdate)

On 26.07.2016 02:13 PM, [ftp83plus] wrote: > I am currently attempting a "port selfupdate" operation before installing two > ports I'd like to test. > > However, it fails for a reason I don't understand: > [...] Also interesting might be the output of `port

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 26, 2016, at 19:58, Ryan Schmidt wrote: > > > On Jul 26, 2016, at 9:55 PM, [ftp83plus] wrote: > >> El 2016-07-26, a las 12:43, Ryan Schmidt escribió: >> >>> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: Here it is:

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 26, 2016, at 9:55 PM, [ftp83plus] wrote: > El 2016-07-26, a las 12:43, Ryan Schmidt escribió: > >> >>> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: >>> >>> Here it is: >>> http://pastebin.com/3LRF0bDS >>> >>> Mac OS X 10.6.8, MacBookPro8,1 >> >> >> Ok, so according to that,

Re: clang 3.4 can't be configured (part of a selfupdate)

What's the path to this log? El 2016-07-26, a las 12:43, Ryan Schmidt escribió: > >> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: >> >> Here it is: >> http://pastebin.com/3LRF0bDS >> >> Mac OS X 10.6.8, MacBookPro8,1 > > > Ok, so according to that, MacPorts clang

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote: > > Here it is: > http://pastebin.com/3LRF0bDS > > Mac OS X 10.6.8, MacBookPro8,1 Ok, so according to that, MacPorts clang 3.7 is being used to try to configure MacPorts clang 3.4, but MacPorts clang 3.7 is crashing.

Re: clang 3.4 can't be configured (part of a selfupdate)

Here it is: http://pastebin.com/3LRF0bDS Mac OS X 10.6.8, MacBookPro8,1 El 2016-07-26, a las 09:06, Aljaž Srebrnič escribió: >> On 26 lug 2016, at 14:13, [ftp83plus] <ges...@ftp83plus.net> wrote: >> >> Hello there, >> >> I am currently attempting

Re: clang 3.4 can't be configured (part of a selfupdate)

> On 26 lug 2016, at 14:13, [ftp83plus] <ges...@ftp83plus.net> wrote: > > Hello there, > > I am currently attempting a "port selfupdate" operation before installing two > ports I'd like to test. > > However, it fails for a reason I don't underst

clang 3.4 can't be configured (part of a selfupdate)

Hello there, I am currently attempting a "port selfupdate" operation before installing two ports I'd like to test. However, it fails for a reason I don't understand: Terminal shows: ---> Verifying checksums for clang-3.4 ---> Extracting clang-3.4 ---> Applying p

Re: "sudo port -d selfupdate" command fails

ng > output : > > > debaratis-mbp:~ debaratiroy$ sudo port -d selfupdate > DEBUG: Copying > /Users/debaratiroy/Library/Preferences/com.apple.dt.Xcode.plist to > /opt/local/var/macports/home/Library/Preferences > DEBUG: MacPorts sources location: > /opt/local/var/macports/sourc

Re: "sudo port -d selfupdate" command fails

rresponding > output : > > > debaratis-mbp:~ debaratiroy$ sudo port -d selfupdate > DEBUG: Copying > /Users/debaratiroy/Library/Preferences/com.apple.dt.Xcode.plist to > /opt/local/var/macports/home/Library/Preferences > DEBUG: MacPorts sources location: > /op

Re: port selfupdate not working Yosemite 10.10.5

yan Schmidt <ryandes...@macports.org> wrote: > > 1. Make sure you have opened the Xcode application once and agreed to the > license agreement. > 2. Make sure you are using "sudo port selfupdate" and not "port selfupdate". __

Re: port selfupdate not working Yosemite 10.10.5

Might be a silly question but do you have enough disk space and or inodes available to create the required files/directories? Maybe try relaxing the permissions temporarily? The ownership and permissions are the same as mine and I have no issues running selfupdate. On Dec 17, 2015 7:58 PM, &qu

Re: port selfupdate not working Yosemite 10.10.5

> On Dec 17, 2015, at 6:08 PM, Mr. Michael Wilson <mtwilson.1...@gmail.com> > wrote: > > I had not updated my ports in a while and when I tried I got this with sudo > port -v selfupdate... > > ---> Updating MacPorts base sources using rsync > receiving file

port selfupdate not working Yosemite 10.10.5

I had not updated my ports in a while and when I tried I got this with sudo port -v selfupdate... ---> Updating MacPorts base sources using rsync receiving file list ... done sent 36 bytes received 69 bytes 19.09 bytes/sec total size is 27013120 speedup is 257267.81 receiving file l

Re: port selfupdate not working Yosemite 10.10.5

Looks good to me. I’m stumped. drwxr-xr-x 5 root admin - 170 Dec 17 18:47 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ se Mike > On Dec 17, 2015, at 7:16 PM, Brandon Allbery wrote: > > ls -ldeO@ >

port selfupdate failed because of signature

36 bytes received 76 bytes 74.67 bytes/sec total size is 512 speedup is 4.57 Error: Failed to verify signature for MacPorts source! To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Fai

Re: port selfupdate failed because of signature

512 speedup is 4.57 Error: Failed to verify signature for MacPorts source! To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source! -- Randal L. Schwa

selfupdate fails

OSX 10.10.4 port version 2.3.3 “port selfupdate” fails on connecting to rsync server, see output below. In the browser there is no problem connecting to rsync.macports.org and the connection is instant. Anything I can do / I should (not) do sudo port -d selfupdate DEBUG: Copying /Users

Re: selfupdate fails

On Monday, August 17, 2015, Ryan Schmidt ryandes...@macports.org wrote: On Aug 17, 2015, at 8:01 PM, Michael David Crawford wrote: Yes, you can change what servers MacPorts uses: https://trac.macports.org/wiki/Mirrors If you can set up an rsync server on your network, and that server can

Re: selfupdate fails

mirror servers, which I can send to you, if you want to go that route. Ideally we would put this information in the public wiki, we just haven't done that yet. If setting up an internal server is not desired, it's not necessary, you just won't be able to use the selfupdate command, because

Re: selfupdate fails

Can one configure the port command to use a local - intranet - server for selfupdate? On Monday, August 17, 2015, Ryan Schmidt ryandes...@macports.org wrote: Yes, you'll need to troubleshoot with your network administrator why you're not able to access rsync servers. If it cannot be fixed, you

Re: selfupdate fails

On Aug 17, 2015, at 8:04 AM, Fred Lahuis wrote: Seems to be a firewall issue, works on home network. Yes, you'll need to troubleshoot with your network administrator why you're not able to access rsync servers. If it cannot be fixed, you can configure MacPorts to sync using a different

Re: selfupdate fails

On Aug 17, 2015, at 8:01 PM, Michael David Crawford wrote: Can one configure the port command to use a local - intranet - server for selfupdate? Yes, you can change what servers MacPorts uses: https://trac.macports.org/wiki/Mirrors If you can set up an rsync server on your network

Re: selfupdate fails

Seems to be a firewall issue, works on home network. Fred On 17 Aug 2015, at 13:10, Fred Lahuis f.lah...@sron.nl wrote: OSX 10.10.4 port version 2.3.3 “port selfupdate” fails on connecting to rsync server, see output below. In the browser there is no problem connecting

Error in selfupdate

Yosemite 10.10.3 (updated religiously), MacPorts 2.3.3 :info:build Making all in gpsd :info:build make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_geoclue/geoclue/work/geoclue-0.12.99/providers/gpsd' :info:build

Re: Error building geoclue (was: Error in selfupdate)

On Apr 19, 2015, at 4:32 PM, Dave Horsfall wrote: Yosemite 10.10.3 (updated religiously), MacPorts 2.3.3 :info:build Making all in gpsd :info:build make[3]: Entering directory

Re: port selfupdate not working

to subversion: http://trac.macports.org/wiki/howto/SyncingWithSVN On Apr 10, 2015, at 11:07 AM, Pragati Srivastava wrote: sudo port -d selfupdate DEBUG: Copying /Users/pragati/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG

Re: port selfupdate not working

On April 11, 2015 6:31:04 AM EDT, Ryan Schmidt ryandes...@macports.org wrote: On Apr 11, 2015, at 2:50 AM, Pragati Srivastava wrote: When i m trying to sync ports tree using subversion, the following command giving error $svn co http://svn.macports.org/repository/macports/trunk/dports/ .

problem with selfupdate

Here is the response I had to sudo port -v selfupdate --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9

Re: problem with selfupdate

On Tue, 7 Apr 2015, David Epstein wrote: Here is the response I had to sudo port -v selfupdate --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) [...] One possible explanation that occurs to me is that I am

Re: problem with selfupdate

is that I am connecting to the Internet from behind some kind of firewall. However, that is just wild conjecture. But it is true that I’m not at the usual place from where I have in the past successfully run selfupdate without a problem. Maybe someone more knowledgeable than I am can say what

Re: problem with selfupdate

Hello Dave, On 08/04/2015, at 5:19 AM, Dave Horsfall wrote: Worked fine for me from Australia. Hey, you're in Australia! Whereabouts? I'm in Melbourne. Cheers, Ian W. ___ macports-users mailing list macports-users@lists.macosforge.org

Re: Selfupdate doesn't work - solved

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 is

Selfupdate doesn't work - solved

! After experimenting with the router's firewall settings, 'selfupdate' worked! My biggest problem was forgetting that there was a second firewall! Thanks for all the help I received; it helped me think more clearly... Jim ___ macports-users mailing

Re: selfupdate doesn't work

On Mon, Mar 2, 2015 at 5:53 AM, Jim Goudie wrote: Selfupdate doesn't work; any advice? ... rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-40/rsync/clientserver.c(105) [receiver=2.6.9] Command

Re: selfupdate doesn't work

On Mar 2, 2015, at 2:13 PM, Dave Horsfall wrote: On Mon, 2 Mar 2015, William H. Magill wrote: On Mar 1, 2015, at 11:53 PM, Jim Goudie jagou...@comcast.net wrote: Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD.

Re: selfupdate doesn't work

(Re-adding the list.) OK. You need to mention what exactly you have tried, or we'll probably just re-suggest all of it. :) The gist of the FAQ is very relevant though. The rsync server is working (I just tried it), so there has to be something about your computer or internet connection that is

Re: selfupdate doesn't work

On Mar 1, 2015, at 11:53 PM, Jim Goudie jagou...@comcast.net wrote: Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not find an update for it. Xcode does not update -- it is a new version you have

Re: selfupdate doesn't work

On Mar 2, 2015, at 10:15 AM, William H. Magill wrote: On Mar 1, 2015, at 11:53 PM, Jim Goudie wrote: Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not find an update for it. Xcode does not

Re: selfupdate doesn't work

On Mon, 2 Mar 2015, William H. Magill wrote: On Mar 1, 2015, at 11:53 PM, Jim Goudie jagou...@comcast.net wrote: Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not find an update for it.

Re: selfupdate doesn't work

On Mon, Mar 2, 2015 at 3:13 PM, Dave Horsfall d...@horsfall.org wrote: Jesus H Christ upon a purple pogo stick! When I bought my MacBook, she ran Snow Leopard 10.6.8, and Xcode was 5.5.1 back then. Note that newer versions of Xcode DO NOT RUN on older OS X releases, and if you force it you

selfupdate doesn't work

Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not find an update for it. Using the pkg file, I loaded Macports 2.3.3 Selfupdate doesn't work; any advice? ... Last login: Sun Mar 1 23:42:37 on ttys000

Re: selfupdate doesn't work

Hello... I'm running OS X 10.6.8 on a dual-core Macbook Pro... I've got Xcode 3.2 loaded from the snow leopard CD. Software Update did not find an update for it. Using the pkg file, I loaded Macports 2.3.3 Selfupdate doesn't work; any advice? ... Last login: Sun Mar 1 23:42:37

Re: port selfupdate 2.3.2 - 2.3.3 fails

On Nov 23, 2014, at 10:46 AM, Carlo Tambuatco wrote: Running port version 2.3.2 on Yosemite 10.10.1 The output of the command: sudo port -v selfupdate is: --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60

port selfupdate 2.3.2 - 2.3.3 fails

Running port version 2.3.2 on Yosemite 10.10.1 The output of the command: sudo port -v selfupdate is: --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync

Re: port selfupdate 2.3.2 - 2.3.3 fails

* Carlo Tambuatco oraclmas...@gmail.com |__ Sun, Nov 23, 2014 at 10:46:10AM CST: rsync: failed to connect to rsync.macports.org: Operation timed out (60) Any ideas? Yes. Seems that a few macports.org resources (rsync.|trac.|distfiles.) are

Re: questions regarding selfupdate issue

Hi, - On 16 Nov, 2014, at 09:34, René J.V. Bertin rjvber...@gmail.com wrote: If sudo port selfupdate updates the MacPorts version, then you must run sudo port selfupdate a second time to index the ports with that new version; MacPorts prints a message telling you to do this. Is that perhaps

Re: questions regarding selfupdate issue

that the field has been re-purposed and a conversion still needs to be done. The conversion is done by [2], which is called when you run make install in a MacPorts source tree (which is what selfupdate does) or when you update using the MacPorts installer. It also transparently handles the database upgrade

Re: questions regarding selfupdate issue

don't have that. I only have an NFS mount under /Volumes that shouldn't be considered by MacPorts at all. Did I mention that this is the first time that the uninstall glitch causes trouble during a selfupdate? Cheers, René ___ macports-users mailing

Re: questions regarding selfupdate issue

. Did I mention that this is the first time that the uninstall glitch causes trouble during a selfupdate? So maybe you just recently updated to the MacPorts version that has this change? Which version are you actually running? What does $ sqlite3 /opt/local/var/macports/registry/registry.db

  1   2   3   4   5   6   7   >