Re: Problem with $DISPLAY

On Fri, 17 Oct 2014, Gregory Shenaut wrote: > touch "Ⓐ Ⓑ Ⓒ" ; touch "ⓐ ⓑ ⓒ" > > you get two files (or at least I did). Same here (Mavericks). Oh, and on my FreeBSD server too, as I'd expect. > When I first moved to Mac OS/X from Unix, I tried installing part of the > system on UFS. It claimed

Re: "Updating database of binaries" step very slow under Yosemite?

On Oct 20, 2014, at 1:22 AM, Leo Singer wrote: > I found that the "Updating database of binaries" step of installing a port > became very slow after I upgraded to Yosemite (i.e., takes many minutes on an > SSD). I am just starting to install my ports again after uninstalling all of > them, so

Re: "Updating database of binaries" step very slow under Yosemite?

Hi, - On 20 Oct, 2014, at 07:22, Leo Singer aron...@macports.org wrote: > I found that the "Updating database of binaries" step of installing a port > became very slow after I upgraded to Yosemite (i.e., takes many minutes on an > SSD). I am just starting to install my ports again after unins

"Updating database of binaries" step very slow under Yosemite?

Hi, I found that the "Updating database of binaries" step of installing a port became very slow after I upgraded to Yosemite (i.e., takes many minutes on an SSD). I am just starting to install my ports again after uninstalling all of them, so if this operation scales with the number of ports it

Re: Yosemite upgrade

My tests tonight were almost successful: the biggest pain point is "cmake", which is referenced by two dozens or so other ports on my install. That’s the infamous "CMAKE_ROOT" issue already documented. I have not tried to download XCode 6.1 yet. Jean-François Gobin http://www.gobinjf.be Le 1

Re: Setting primary executable instance

* Brandon Allbery [141019 17:20]: > On Sun, Oct 19, 2014 at 9:05 PM, Tim Johnson wrote: > > > I've installed emacs 24. > > > > If I do > > which -a emacs > > > > I get > > /opt/local/bin/emacs ## New emacs > > /usr/bin/emacs ## Old emacs > > > > 1. "which" lies a lot. use "type". > 2. Whi

Re: Setting primary executable instance

On Sun, Oct 19, 2014 at 9:05 PM, Tim Johnson wrote: > I've installed emacs 24. > > If I do > which -a emacs > > I get > /opt/local/bin/emacs ## New emacs > /usr/bin/emacs ## Old emacs > 1. "which" lies a lot. use "type". 2. Which one is found depends on a number of things: a. the order o

Setting primary executable instance

I've installed emacs 24. If I do which -a emacs I get /opt/local/bin/emacs ## New emacs /usr/bin/emacs ## Old emacs If I do which emacs I get /usr/bin/emacs ## Old emacs question : can port switch the precedence so that invoking emacs gets me the new (macports) version and without ov

Re: Yosemite upgrade

On Oct 19, 2014, at 3:33 PM, Ryan Schmidt wrote: > On Oct 19, 2014, at 1:33 PM, Carlo Tambuatco wrote: >> Supported or not...this way seemed to work for a majority of my ports and I >> was wondering whether nuking all 459 of my ports for the sake of a few that >> don't work seems like an ineffic

Re: Yosemite buildbot?

On Sun, Oct 19, 2014 at 8:52 PM, Jason Mitchell wrote: > Is there a buildbot in the works for Yosemite ports? I checked > https://build.macports.org/buildslaves but didn't see anything for > Yosemite yet. Maybe I've misunderstood the process, or am just being > greedy? > It was requested; the

Yosemite buildbot?

Hello, Is there a buildbot in the works for Yosemite ports? I checked https://build.macports.org/buildslaves but didn't see anything for Yosemite yet. Maybe I've misunderstood the process, or am just being greedy? thx, -jason ___ macports-users maili

Re: problem with build

On Oct 19, 2014, at 5:56 PM, Comer Duncan wrote: > Ryan, > > I have not idea that I really do. It has been part and parcel of the macports > installed stuff for quite some time. How do I redo the port update outdated > without apple-gcc42? Do a port unintall first? > > Comer Ok, then just

Re: problem with build

On Oct 19, 2014, at 5:49 PM, Comer Duncan wrote: > Error: apple-gcc42 is not supported on Yosemite or later. This message is correct. Why do you need apple-gcc42? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macos

problem with build

---> Fetching archive for apple-gcc42 ---> Attempting to fetch apple-gcc42-5666.3_14.darwin_14.x86_64.tbz2 from http://packages.macports.org/apple-gcc42 ---> Attempting to fetch apple-gcc42-5666.3_14.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/apple-gcc42 ---> Attempting to f

Re: Dealing with nonstandard installs

> On Oct 19, 2014, at 5:24 PM, Watson Ladd wrote: > > PARI comes with optional packages. To install them, they need to be > untared on top of the installation Macports makes. I'd like to make > this part of the usual portfile for PARI, but there is too much magic > for me to figure out how to do

Dealing with nonstandard installs

Dear all, PARI comes with optional packages. To install them, they need to be untared on top of the installation Macports makes. I'd like to make this part of the usual portfile for PARI, but there is too much magic for me to figure out how to do this. Does anyone have a resource to point to for he

Re: Yosemite, XCode 6.1?

In article <05649a1b-10b7-442e-8944-687575f33...@mac.com>, "William H. Magill" wrote: > The truly annoying thing is that 6.0.1 was released along with 10.10 -- and a > comment > that it "supported" 10.10. > Where the definition of "supported" means -- will run under 10.10; but does > NOT > pro

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Oct 19, 2014, at 1:42 PM, Carlo Tambuatco wrote: > When you upgrade a port, everything it depends on gets updated first, right? > What doesn't get upgraded should not affect what does get upgraded during the > configure/build/install/activate phase, right? So how is using -u different > fro

Re: MacPorts 2.3.2 and "port provides"

On Oct 19, 2014, at 19:22 PM, Ryan Schmidt wrote: > On Oct 18, 2014, at 5:40 PM, Greg Earle wrote: > >> I just did a selfupdate to 2.3.2, and when I try to run >> >> sudo port provides /private/opt/local/ >> >> it always says >> >> /private/opt/local/ is not provided by a MacPorts port, e.g.

Re: iStumbler update?

> On Oct 19, 2014, at 12:52 PM, William H. Magill wrote: > > Going through the "update ritual" I checked on Mac Ports iStumbler. > It launched and reported that a new version existed (100.22 vs 99). > In the resulting pop-up are instructions that the 99 version would fail to > download the upd

Re: Yosemite upgrade

On Oct 19, 2014, at 1:33 PM, Carlo Tambuatco wrote: > > Supported or not...this way seemed to work for a majority of my ports and I > was wondering whether nuking all 459 of my ports for the sake of a few that > don't work seems like an inefficient solution. It seems there are other ways > to

Re: Yosemite upgrade

Yes, I saw it. Thanks anyway for pointing it to me. I think this should be proposed as a command-line option, something like "port wishlist" which would save a ton of time to everybody. I'll look into developing this (possibly ... as a port!) J. 2014-10-19 15:27 GMT-04:00 Carlo Tambuatco : > Ha

Re: Yosemite upgrade

Have you checked out the macports migration page? There's a script you might be interested in: 1. Download and execute the restore_ports script. (If you installed MacPorts from source and put its Tcl package somewhere other than /Library/Tcl, then you'll need to use the -t option when yo

Re: Yosemite upgrade

Is there a command line switch for "port" that would dump an "install/select" script? For example, that would dump something like port install python27 > port install python34 > port select python --set python34 > port install octave > port install gcc48 > port select gcc --set gcc48 That can be

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Oct 19, 2014, at 3:00 PM, Carlo Tambuatco wrote: > So uninstalling and reinstalling as people suggested before would only > replicate those useless ports again...so functionally, how is > what I did (using sudo port -u upgrade outdated) different from > uninstall/reinstalling everything? An

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 3:02 PM, Carlo Tambuatco wrote: > ...in particular, how is it going to change the situation of pypy which is > due to a checksum error, not a build error at all? Checksum errors mean either you have a bad download (try `port clean` on the port in question) or the upstrea

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

If there's a missing dependency that's used, upgrade will pull in files from the old (possibly broken) packages to build new ones. Uninstalling everything first then building, or using trace mode for upgrade, eliminates this possibility. On Oct 19, 2014, at 3:00 PM, Carlo Tambuatco wrote: > S

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 3:00 PM, Carlo Tambuatco wrote: > > > On Sun, Oct 19, 2014 at 2:55 PM, Brandon Allbery > wrote: > >> On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco >> wrote: >> >>> Even if this process accumulates useless or redundant ports over time, >>> it should not affect the buil

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:54 PM, Carlo Tambuatco wrote: > I mean, would not a better more efficient method be to create a list of > your requested ports and just migrate those? > I think the Migration page used to hint at that. In fact I generally do, instead of listing all installed ports, limi

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:55 PM, Brandon Allbery wrote: > On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco > wrote: > >> Even if this process accumulates useless or redundant ports over time, it >> should not affect the build of the newer ports, right? > > > But they will still be installed and

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco wrote: > Even if this process accumulates useless or redundant ports over time, it > should not affect the build of the newer ports, right? But they will still be installed and will therefore be in your list of reinstalls. -- brandon s allbery

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

I mean, would not a better more efficient method be to create a list of your requested ports and just migrate those? On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco wrote: > Even if the old ports that are dependencies of the old port still exist, > the upgraded port with the new dependencies do

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

Even if the old ports that are dependencies of the old port still exist, the upgraded port with the new dependencies downloads and builds the new dependencies before it upgrades itself. Even if this process accumulates useless or redundant ports over time, it should not affect the build of the newe

Re: Yosemite upgrade

On Oct 19, 2014, at 2:33 PM, Carlo Tambuatco wrote: > Supported or not...this way seemed to work for a majority of my ports and I > was wondering whether nuking all 459 of my ports for the sake of a few that > don't work seems like an inefficient solution. It seems there are other ways > to ap

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:42 PM, Carlo Tambuatco wrote: > When you upgrade a port, everything it depends on gets updated first, > right? What doesn't get upgraded should not affect what does get upgraded > during the configure/build/install/activate phase, right? So how is using > -u different fr

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

When you upgrade a port, everything it depends on gets updated first, right? What doesn't get upgraded should not affect what does get upgraded during the configure/build/install/activate phase, right? So how is using -u different from uninstalling everything and reinstalling everything again? On

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:35 PM, Carlo Tambuatco wrote: > But the doesn't the -u option do exactly what is in the migration guide? > ie: uninstall old ports in favor of the new upgraded version? What's the > difference? -u means remove archived old versions of the port that is currently being u

Re: Yosemite upgrade

On Oct 19, 2014, at 2:30 PM, Chris Jones wrote: > My understanding though is this is not a supported way of upgrading after an > OS upgrade. Removing all ports first then reinstalling those you want is the > recommendation. Right. Joshua recently suggested that merely upgrading everything didn

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:33 PM, Carlo Tambuatco wrote: > Supported or not...this way seemed to work for a majority of my ports and > I was wondering whether nuking all 459 of my ports for the sake of a few > that don't work seems like an inefficient solution. It seems there are > other ways to a

Re: Yosemite upgrade

> On 19 Oct 2014, at 7:33 pm, Carlo Tambuatco wrote: > > Supported or not...this way seemed to work for a majority of my ports and I > was wondering whether nuking all 459 of my ports for the sake of a few that > don't work seems like an inefficient solution. It seems there are other ways >

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

But the doesn't the -u option do exactly what is in the migration guide? ie: uninstall old ports in favor of the new upgraded version? What's the difference? On Sun, Oct 19, 2014 at 2:33 PM, Chris Jones wrote: > > > > > On 19 Oct 2014, at 7:30 pm, Carlo Tambuatco wrote: > > > > On Sun, Oct 19,

Re: Yosemite upgrade

Supported or not...this way seemed to work for a majority of my ports and I was wondering whether nuking all 459 of my ports for the sake of a few that don't work seems like an inefficient solution. It seems there are other ways to approach this problem... On Sun, Oct 19, 2014 at 2:30 PM, Chris Jo

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

> On 19 Oct 2014, at 7:30 pm, Carlo Tambuatco wrote: > > > >> On Sun, Oct 19, 2014 at 2:28 PM, Chris Jones >> wrote: >> >> >>> On 19 Oct 2014, at 7:23 pm, Brandon Allbery wrote: >>> On Sun, Oct 19, 2014 at 2:21 PM, Chris Jones wrote: Well yes, you do not have to reins

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:25 PM, Lawrence Velázquez wrote: > It looks like you used `port select` to make Python 3.x your default, and > LLVM's configure is choking on it. This sounds like a bug in the port, to be honest. (And it's not the first time I've heard of ports tripping over `port sele

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:28 PM, Chris Jones wrote: > > > On 19 Oct 2014, at 7:23 pm, Brandon Allbery wrote: > > On Sun, Oct 19, 2014 at 2:21 PM, Chris Jones > wrote: > >> Well yes, you do not have to reinstall everything after removal. The >> important bit is the removal step... ;) > > > But t

Re: Yosemite upgrade

> On 19 Oct 2014, at 7:26 pm, Lawrence Velázquez wrote: > >> On Oct 19, 2014, at 12:57 PM, Chris Jones wrote: >> >> I still think something went wrong and some memory of your previous OSX 10.9 >> installations is still present. I cannot see how you would get messages >> regarding Darwin 1

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

> On 19 Oct 2014, at 7:23 pm, Brandon Allbery wrote: > >> On Sun, Oct 19, 2014 at 2:21 PM, Chris Jones >> wrote: >> Well yes, you do not have to reinstall everything after removal. The >> important bit is the removal step... ;) > > But the thing you complained about was exactly "remove or r

Re: Yosemite upgrade

On Oct 19, 2014, at 12:57 PM, Chris Jones wrote: > I still think something went wrong and some memory of your previous OSX 10.9 > installations is still present. I cannot see how you would get messages > regarding Darwin 13 otherwise. It seems that Carlo successfully upgraded all his other por

Re: Yosemite upgrade

On Oct 19, 2014, at 11:15 AM, Carlo Tambuatco wrote: > I will attach the log file for the llvm-3.3 error. >From the configure phase: :info:configure checking for python... /opt/local/bin/python :info:configure checking for python >= 2.5... File "", line 1 :info:configure impor

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:21 PM, Chris Jones wrote: > Well yes, you do not have to reinstall everything after removal. The > important bit is the removal step... ;) But the thing you complained about was exactly "remove or reinstall (...) as you see fit". It was not admitting to other possibili

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

> On 19 Oct 2014, at 7:17 pm, Brandon Allbery wrote: > >> On Sun, Oct 19, 2014 at 2:15 PM, Chris Jones >> wrote: >> ... it is not a matter of 'seeing fit'. Unless you want ongoing problems, >> the only correct thing to do is to reinstall *all* your ports... > > Uninstalling port you don't w

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:17 PM, Brandon Allbery wrote: > On Sun, Oct 19, 2014 at 2:15 PM, Chris Jones > wrote: > >> ... it is not a matter of 'seeing fit'. Unless you want ongoing problems, >> the only correct thing to do is to reinstall *all* your ports... > > > Uninstalling port you don't wan

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

On Sun, Oct 19, 2014 at 2:15 PM, Chris Jones wrote: > ... it is not a matter of 'seeing fit'. Unless you want ongoing problems, > the only correct thing to do is to reinstall *all* your ports... Uninstalling port you don't want any more is perfectly legitimate, provided it's not a dependency of

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

> On 19 Oct 2014, at 7:02 pm, Carlo Tambuatco wrote: > > Have you upgraded macports to the newest version for OS X 10.10? Do you have > your Xcode command line tools installed for OS X 10.10? Are you using the > latest available Xcode 6.1? Unless you've explicitly uninstalled all your > po

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:09 PM, Lawrence Velázquez wrote: > On Oct 19, 2014, at 12:16 PM, Carlo Tambuatco > wrote: > > > spe (Stani's Python Editor) depends on py26-wxpython-2.8. As well as > python26 and py26-checker. > > I don't know anything about spe specifically, but it'd be nice to move i

Re: Yosemite upgrade

On Oct 19, 2014, at 1:46 PM, Dave Horsfall wrote: > OK, I have to bite: can someone please tell this non-American just how > "Yosemite" is pronounced? > > Is it YOZE-mite? YOZZ-mite? YOZZY-mite? As Brandon said. Think of it as "Yo-se-mit-e". > It was many years before I learned that "Arkans

Re: Yosemite upgrade

On Oct 19, 2014, at 12:16 PM, Carlo Tambuatco wrote: > spe (Stani's Python Editor) depends on py26-wxpython-2.8. As well as python26 > and py26-checker. I don't know anything about spe specifically, but it'd be nice to move it to a newer version of wxPython. vq ___

Re: Yosemite upgrade

On Oct 19, 2014, at 11:15 AM, Carlo Tambuatco wrote: > Just upgraded to XCode 6.1. There are still a few hiccups, ports that fail to > upgrade for one reason or another: > > db46 4.6.21_9 < 4.6.21_9 (platform darwin 13 != > darwin 14) This build fine for me. > gc

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

Hi, - On 19 Oct, 2014, at 19:58, Leo Singer aron...@macports.org wrote: > I just upgraded my system to Yosemite. Unfortunately, I did not get the list > of > installed ports and uninstall them before I upgraded the OS. Now it is too > late: > > $ port -qv installed > Error: Current platform

Re: Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

Have you upgraded macports to the newest version for OS X 10.10? Do you have your Xcode command line tools installed for OS X 10.10? Are you using the latest available Xcode 6.1? Unless you've explicitly uninstalled all your ports yourself they should still be there when you install the newest vers

Migrating to Yosemite---cannot run 'port -qv installed' after OS upgrade

Hi, I just upgraded my system to Yosemite. Unfortunately, I did not get the list of installed ports and uninstall them before I upgraded the OS. Now it is too late: $ port -qv installed Error: Current platform "darwin 14" does not match expected platform "darwin 13" Error: If you upgraded your O

Re: Yosemite upgrade

You mean Mel-buhn and Bris-ben? On Sun, Oct 19, 2014 at 1:46 PM, Dave Horsfall wrote: > OK, I have to bite: can someone please tell this non-American just how > "Yosemite" is pronounced? > > Is it YOZE-mite? YOZZ-mite? YOZZY-mite? > > It was many years before I learned that "Arkansas" is prono

iStumbler update?

I am really beginning to hate the new Yosemite mail client…. it is refusing to display “to” information unless I “view Raw Source", and it defaults to sending from “icloud.com ” instead of from “mac.com ” — which is how I’ve been subscribed to the mailing lis

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 1:46 PM, Dave Horsfall wrote: > OK, I have to bite: can someone please tell this non-American just how > "Yosemite" is pronounced? > Yoh-SEH-mih-tee -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: Yosemite upgrade

OK, I have to bite: can someone please tell this non-American just how "Yosemite" is pronounced? Is it YOZE-mite? YOZZ-mite? YOZZY-mite? It was many years before I learned that "Arkansas" is pronounced ARK-cun-sor, for example. In return I'll happily teach anyone how to pronounce Australian

Re: Yosemite upgrade

> I've been using MacPorts since 10.6 abd with each new OSX it seemed to me > less painful nuking MacPorts and running some port installs over night, than > mucking endlessly with several ports, wasting time etc... > So... Nuke now! ... or forever hold your pieces :-) --- Entertaining minecraf

Re: Yosemite upgrade

I've been using MacPorts since 10.6 abd with each new OSX it seemed to me less painful nuking MacPorts and running some port installs over night, than mucking endlessly with several ports, wasting time etc... So... Nuke now! Dom > Am 19.10.2014 um 19:17 schrieb Carlo Tambuatco : > > I'll give

Re: Yosemite, XCode 6.1?

Gregory Shenaut wrote: > However, I'm also seeing this unusual (to me) message: "Warning: All > compilers are either blacklisted or unavailable; defaulting to first > fallback option". > > And I note that in the cmake log, it appears to require the > MacOSX10.10.sdk, which is a component of XCOd

Re: Yosemite upgrade

I'll give it a day or two...if no solution presents itself I'll do the nuclear option and start over. On Sunday, October 19, 2014, Brandon Allbery wrote: > On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco > wrote: > >> before I do a clean wipe of all my macports and spend the next 10 hours >> o

Re: Yosemite upgrade

> On 19 Oct 2014, at 6:00 pm, Carlo Tambuatco wrote: > > I'd like to get some feedback on those logfiles I sent first before I do a > clean wipe of all my macports and spend the next 10 hours or so downloading, > configuring, building and reinstalling 459 separate ports. There may be a > s

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco wrote: > before I do a clean wipe of all my macports and spend the next 10 hours or > so downloading, configuring, building and reinstalling 459 separate ports. > There may be a simpler solution. If there were one, someone would have found it by

Re: Yosemite upgrade

I'd like to get some feedback on those logfiles I sent first before I do a clean wipe of all my macports and spend the next 10 hours or so downloading, configuring, building and reinstalling 459 separate ports. There may be a simpler solution. On Sun, Oct 19, 2014 at 12:57 PM, Chris Jones wrote:

Re: Yosemite upgrade

Hi, > On 19 Oct 2014, at 5:50 pm, Carlo Tambuatco wrote: > > I upgraded to Xcode 6.1, installed the command line tools for 10.10, > re-installed macports using the appropriate 10.10 installer .dmg. Then > upgraded all my macports. The only thing I can think of that you may be > referring to t

Re: Yosemite upgrade

I upgraded to Xcode 6.1, installed the command line tools for 10.10, re-installed macports using the appropriate 10.10 installer .dmg. Then upgraded all my macports. The only thing I can think of that you may be referring to that I have not done so far is update the macports.conf file...? >From th

Re: Yosemite upgrade

Hi, gcc48 and libgcc installed fine for me in a OSX10.10 VM I had running with the Xcode 6.1 beta prelease. Did you correctly follow the MacPorts migration guide after upgrading your OS. https://trac.macports.org/wiki/Migration The references below to Darwin 13 (OSX 10.9) suggests to me you di

Re: Yosemite upgrade

spe (Stani's Python Editor) depends on py26-wxpython-2.8. As well as python26 and py26-checker. On Sun, Oct 19, 2014 at 12:09 PM, Wahlstedt Jyrki wrote: > > On 19 .10 .2014, at 18.15, Carlo Tambuatco wrote: > > py26-wxpython-2.8 2.8.12.1_0 < 2.8.12.1_0 (platform darwin > 13 != dar

Re: Yosemite upgrade

> On 19 .10 .2014, at 18.15, Carlo Tambuatco wrote: > > py26-wxpython-2.8 2.8.12.1_0 < 2.8.12.1_0 (platform darwin 13 > != darwin 14) > > This wxPython version is really awfully old, also limited to 32bit. Is there something tying you with this? If not, forget it and use the

Re: Yosemite, XCode 6.1?

> On 19 .10 .2014, at 16.41, James Rome wrote: > > xcode6.1 is released on the Apple Developer's site: > https://developer.apple.com/downloads/index.action# > > For me, it’s ”Available shortly” there… ! ! Jyrki _

Re: Yosemite, XCode 6.1?

> On Oct 19, 2014, at 12:50 AM, Ned Deily wrote: > > In article , > Chris Jones wrote: >> Its quite simple, you need the OSX 10.10 SDK, which is only available in >> Xcode 6.1, which for whatever reason is not released yet. You need to wait >> for it > > The reason, I think, is that Xcod

Re: Yosemite, XCode 6.1?

xcode6.1 is released on the Apple Developer's site: https://developer.apple.com/downloads/index.action# James A. Rome http://jamesrome.net On 10/18/14 5:24 PM, Brandon Allbery wrote: > On Sat, Oct 18, 2014 at 5:20 PM, Gregory Shenaut > mailto:gkshen...@ucdavis.edu>> wrote: > > And I note that

Re: Yosemite upgrade

> On 19 Oct 2014, at 10:19 am, René J.V. Bertin wrote: > >> On Saturday October 18 2014 19:16:39 Ryan Schmidt wrote: >> Remember to Reply All when you reply. >> >> >>> On Oct 18, 2014, at 7:13 PM, Carlo Tambuatco wrote: >>> >>> Yeah, just upgraded my ports yesterday after upgrading to Yose

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 5:19 AM, René J.V. wrote: > That's a really curious requirement for a FOSS utility ... doesn't it > build on earlier versions of OS X that lack the 10.10 SDK by definition? Or > doesn't a binary built on, say, 10.6, run on 10.10? If you build on 10.6, it looks for the 10

Re: MacPorts 2.3.2 and "port provides"

Hi, - On 19 Oct, 2014, at 02:22, Ryan Schmidt ryandes...@macports.org wrote: > MacPorts should be in /opt/local, not /private/opt/local. > > Is it possible that /opt is a symlink to /private/opt? Ancient versions of the > Cisco VPN installer were known to have moved /opt to /private/opt, the