subject:"Re\: Yosemite upgrade"

On Sun, Oct 19, 2014 at 5:19 AM, René J.V. rjvber...@gmail.com 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.6 SDK. And Apple still ships the
runtime libraries (only; not the SDK) for things on 10.6 that are no longer
in 10.10's SDK, so that (most) programs will still run.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade





 On 19 Oct 2014, at 10:19 am, René J.V. Bertin rjvber...@gmail.com 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 Yosemite, and 
 cmake along with other ports such as pypy etc fail to upgrade properly. I 
 am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1 to be 
 released officially before upgrading these ports?
 
 Yes, to build cmake, you need the 10.10 SDK. It's in Xcode 6.1, both the 
 final version which Apple will release to everyone later and the pre-release 
 versions, if you can still find it, or the beta versions (but not the final 
 version) of Xcode 6.0.
 That's a really curious requirement for a FOSS utility

Not really. Cmake provides the means to build full native Cocoa applications, 
and to do this it needs access to an OSX SDK. 

 ... 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?

It requires the SDK for the platform it is being built for, so on OSX10.10 
needs the 10.10 SDK, on 10.9 the 10.9 SDK and so on... I guess in theory you 
could target an older OSX release, so use 10.9 SDK on 10.10, but as this is not 
needed in MacPorts, the binaries are always specific for a given OS, the system 
SDK is used to provide the most up to date features... 

So yes, it builds fine and provides binaries on older OSX releases. Its just a 
(temporary) issue with 10.10 until Xcode 6.1 is available.
 
 
 R
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

2014-10-19 Thread Wahlstedt Jyrki


 On 19 .10 .2014, at 18.15, Carlo Tambuatco oraclmas...@gmail.com 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 newer 
py27-wxpython-3.0…

!
! Jyrki Wahlstedt
!   http://www.wahlstedt.fi/jyrki/ Twitter: @jyrkiw
!
! Our life is no dream; but it ought to become one and perhaps will.
! 



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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 j...@macports.org wrote:


 On 19 .10 .2014, at 18.15, Carlo Tambuatco oraclmas...@gmail.com 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 newer
 py27-wxpython-3.0…

 !
 ! Jyrki Wahlstedt
 ! http://www.wahlstedt.fi/jyrki/ Twitter: @jyrkiw
 !
 ! Our life is no dream; but it ought to become one and perhaps will.
 !




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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 did not follow 
the migration instructions..

Chris



 On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco oraclmas...@gmail.com 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)  
 
 gcc47  4.7.4_1  4.7.4_1  (platform darwin 13 != 
 darwin 14)  
 
 gcc48  4.8.3_0  4.8.3_0  (platform darwin 13 != 
 darwin 14)  
 
 libgcc 4.9.1_0  4.9.1_0  (platform darwin 13 != 
 darwin 14)  
 
 llvm-3.3   3.3_4  3.3_4  (platform darwin 13 != darwin 
 14)  
 
 py26-wxpython-2.8  2.8.12.1_0  2.8.12.1_0  (platform darwin 13 
 != darwin 14)  
 
 pypy   2.4.0_0  2.4.0_0  (platform darwin 13 != 
 darwin 14)  
 
 v8 3.23.17.23_1  3.23.17.23_1  (platform darwin 
 13 != darwin 14) 
 
 
 
 The failure of gcc47 and gcc48 seem to be connected to the failure to 
 configure llvm-3.3
 
 Here's the specific llvm-3.3 error:
 
 Error: Failed to configure llvm-3.3, consult 
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/llvm-3.3.src/config.log
 
 
 Error: org.macports.configure for port llvm-3.3 returned: configure failure: 
 command execution failed
 
 I will attach the log file for the llvm-3.3 error.
 
 
 
 
 
 pypy fails because of a checksum mismatch:
 
 Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2
 
 Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2
 
 Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2
 
 
 Error: org.macports.checksum for port pypy returned: Unable to verify file 
 checksums
 
 
 
 I'm not sure what the problem with v8 is so I'll try to attach the log file 
 for that as well.
 
 
 On Sat, Oct 18, 2014 at 8:16 PM, Ryan Schmidt ryandes...@macports.org 
 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 Yosemite, and 
  cmake along with other ports such as pypy etc fail to upgrade properly. I 
  am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1 to be 
  released officially before upgrading these ports?
 
 Yes, to build cmake, you need the 10.10 SDK. It's in Xcode 6.1, both the 
 final version which Apple will release to everyone later and the pre-release 
 versions, if you can still find it, or the beta versions (but not the final 
 version) of Xcode 6.0.
 
 
  Ports that have failed the upgrade process after migrating to Yosemite:
 
  apple-gcc42@5666.3 lang/apple-gcc42
 
 apple-gcc42 is not supported on Yosemite for now.
 
  clisp  @2.49   lang/clisp
  cmake  @3.0.2  devel/cmake
  db46   @4.6.21 databases/db46
  gcc47  @4.7.4  lang/gcc47
 
 I haven't yet fixed gcc47 and lower for Yosemite, though I intend to. gcc48 
 and up should work.
 
  gcc48  @4.8.3  lang/gcc48
  gstreamer1-gst-plugins-base@1.4.3  
  gnome/gstreamer1-gst-plugins-base
  libgcc @4.9.1  lang/gcc49
  llvm-3.3   @3.3lang/llvm-3.3
  llvm-gcc42 @2336.11lang/llvm-gcc42
 
 llvm-gcc42 is not supported on Yosemite for now.
 
  py26-wxpython-2.8  @2.8.12.1   python/py-wxpython-2.8
  pypy   @2.4.0  lang/pypy
  v8 @3.23.17.23 lang/v8
 
 logfiles.zip
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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 the macports migration page:

If your macports.conf contains uncommented settings for universal_archs or
build_arch, you will likely want to update them, since unlike earlier OS
versions, the compiler on Snow Leopard and later will build for x86_64 by
default on systems that support it. The default values will be fine for
almost all users, so unless you know you need something different, just
comment out these two lines.

Several other settings in macports.conf have changed their defaults over
the years. Take a moment to compare each line of your macports.conf with
the corresponding line in macports.conf.default in the same directory.
Unless you know a reason why a line your settings file should be different
from the defaults, adopt the line from the defaults file.

I don't really know enough about these settings to mess with them myself.
Did you change any values in the macports.conf file or
macports.conf.default file to get it to work? Other than this I can't think
of anything I did that is different to the steps for migrating macports.




On Sun, Oct 19, 2014 at 12:34 PM, Chris Jones jon...@hep.phy.cam.ac.uk
wrote:

 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 did not
 follow the migration instructions..

 Chris



 On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco oraclmas...@gmail.com 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)

 gcc47  4.7.4_1  4.7.4_1  (platform darwin 13 !=
 darwin 14)

 gcc48  4.8.3_0  4.8.3_0  (platform darwin 13 !=
 darwin 14)

 libgcc 4.9.1_0  4.9.1_0  (platform darwin 13 !=
 darwin 14)

 llvm-3.3   3.3_4  3.3_4  (platform darwin 13 !=
 darwin 14)

 py26-wxpython-2.8  2.8.12.1_0  2.8.12.1_0  (platform darwin
 13 != darwin 14)

 pypy   2.4.0_0  2.4.0_0  (platform darwin 13 !=
 darwin 14)

 v8 3.23.17.23_1  3.23.17.23_1  (platform
 darwin 13 != darwin 14)


 The failure of gcc47 and gcc48 seem to be connected to the failure to
 configure llvm-3.3

 Here's the specific llvm-3.3 error:

 Error: Failed to configure llvm-3.3, consult
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/llvm-3.3.src/config.log

 Error: org.macports.configure for port llvm-3.3 returned: configure
 failure: command execution failed

 I will attach the log file for the llvm-3.3 error.



 pypy fails because of a checksum mismatch:

 Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2

 Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2

 Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2

 Error: org.macports.checksum for port pypy returned: Unable to verify file
 checksums


 I'm not sure what the problem with v8 is so I'll try to attach the log
 file for that as well.

 On Sat, Oct 18, 2014 at 8:16 PM, Ryan Schmidt ryandes...@macports.org
 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 Yosemite, and
 cmake along with other ports such as pypy etc fail to upgrade properly. I
 am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1 to be
 released officially before upgrading these ports?

 Yes, to build cmake, you need the 10.10 SDK. It's in Xcode 6.1, both the
 final version which Apple will release to everyone later and the
 pre-release versions, if you can still find it, or the beta versions (but
 not the final version) of Xcode 6.0.


  Ports that have failed the upgrade process after migrating to Yosemite:
 
  apple-gcc42@5666.3 lang/apple-gcc42

 apple-gcc42 is not supported on Yosemite for now.

  clisp  @2.49   lang/clisp
  cmake  @3.0.2  devel/cmake
  db46   @4.6.21 databases/db46
  gcc47  @4.7.4  lang/gcc47

 I haven't yet fixed gcc47 and lower for Yosemite, though I intend to.
 gcc48 and up should work.

  gcc48  @4.8.3  lang/gcc48
  gstreamer1-gst-plugins-base@1.4.3
 gnome/gstreamer1-gst-plugins-base
  libgcc

Re: Yosemite upgrade

Hi,

On 19 Oct 2014, at 5:50 pm, Carlo Tambuatco oraclmas...@gmail.com 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 that I have not done so far is update the macports.conf file...?

When you say you upgraded all your ports, did you do this exactly how the guide
says ? I.e. Did you first uninstall them all, then, reinstall them from scratch
?

From the macports migration page:

If your macports.conf contains uncommented settings for universal_archs or
build_arch, you will likely want to update them, since unlike earlier OS
versions, the compiler on Snow Leopard and later will build for x86_64 by
default on systems that support it. The default values will be fine for
almost all users, so unless you know you need something different, just
comment out these two lines.

Several other settings in macports.conf have changed their defaults over the
years. Take a moment to compare each line of your macports.conf with the
corresponding line in macports.conf.default in the same directory. Unless you
know a reason why a line your settings file should be different from the
defaults, adopt the line from the defaults file.

I don't really know enough about these settings to mess with them myself. Did
you change any values in the macports.conf file or macports.conf.default file
to get it to work? Other than this I can't think of anything I did that is
different to the steps for migrating macports.

I did not touch any conf files.

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. At this point i would perhaps suggest completely
wiping macports

https://guide.macports.org/chunked/installing.macports.uninstalling.html

Then reinstall from scratch.

Chris

On Sun, Oct 19, 2014 at 12:34 PM, Chris Jones jon...@hep.phy.cam.ac.uk
wrote:
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 did not
follow the migration instructions..

Chris

On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco oraclmas...@gmail.com 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)

gcc47 4.7.4_1 4.7.4_1 (platform darwin 13 !=
darwin 14)

gcc48 4.8.3_0 4.8.3_0 (platform darwin 13 !=
darwin 14)

libgcc 4.9.1_0 4.9.1_0 (platform darwin 13 !=
darwin 14)

llvm-3.3 3.3_4 3.3_4 (platform darwin 13 != darwin
14)

py26-wxpython-2.8 2.8.12.1_0 2.8.12.1_0 (platform darwin 13
!= darwin 14)

pypy 2.4.0_0 2.4.0_0 (platform darwin 13 !=
darwin 14)

v8 3.23.17.23_1 3.23.17.23_1 (platform
darwin 13 != darwin 14)

The failure of gcc47 and gcc48 seem to be connected to the failure to
configure llvm-3.3

Here's the specific llvm-3.3 error:

Error: Failed to configure llvm-3.3, consult
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/llvm-3.3.src/config.log

Error: org.macports.configure for port llvm-3.3 returned: configure
failure: command execution failed

I will attach the log file for the llvm-3.3 error.

pypy fails because of a checksum mismatch:

Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2

Error: org.macports.checksum for port pypy returned: Unable to verify file
checksums

I'm not sure what the problem with v8 is so I'll try to attach the log file
for that as well.

On Sat, Oct 18, 2014 at 8:16 PM, Ryan Schmidt ryandes...@macports.org
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 Yosemite, and
cmake along with other ports such as pypy etc fail to upgrade properly.
I am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1
to be released officially before upgrading these ports?

Yes, to build cmake, you need the 10.10 SDK. It's in Xcode 6.1, both the
final version which Apple will release to everyone later and the
pre-release versions, if you can

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 jon...@hep.phy.cam.ac.uk
wrote:

Hi,

On 19 Oct 2014, at 5:50 pm, Carlo Tambuatco oraclmas...@gmail.com wrote:

When you say you upgraded all your ports, did you do this exactly how the
guide says ? I.e. Did you first uninstall them all, then, reinstall them
from scratch ?

From the macports migration page:

If your macports.conf contains uncommented settings for universal_archs
or build_arch, you will likely want to update them, since unlike earlier OS
versions, the compiler on Snow Leopard and later will build for x86_64 by
default on systems that support it. The default values will be fine for
almost all users, so unless you know you need something different, just
comment out these two lines.

Several other settings in macports.conf have changed their defaults over
the years. Take a moment to compare each line of your macports.conf with
the corresponding line in macports.conf.default in the same directory.
Unless you know a reason why a line your settings file should be different
from the defaults, adopt the line from the defaults file.

I don't really know enough about these settings to mess with them myself.
Did you change any values in the macports.conf file or
macports.conf.default file to get it to work? Other than this I can't think
of anything I did that is different to the steps for migrating macports.

I did not touch any conf files.

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. At this point i would perhaps
suggest completely wiping macports

https://guide.macports.org/chunked/installing.macports.uninstalling.html

Then reinstall from scratch.

Chris

On Sun, Oct 19, 2014 at 12:34 PM, Chris Jones jon...@hep.phy.cam.ac.uk
wrote:

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 did not
follow the migration instructions..

Chris

On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco oraclmas...@gmail.com
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)

gcc47 4.7.4_1 4.7.4_1 (platform darwin 13 !=
darwin 14)

gcc48 4.8.3_0 4.8.3_0 (platform darwin 13 !=
darwin 14)

libgcc 4.9.1_0 4.9.1_0 (platform darwin 13 !=
darwin 14)

llvm-3.3 3.3_4 3.3_4 (platform darwin 13 !=
darwin 14)

py26-wxpython-2.8 2.8.12.1_0 2.8.12.1_0 (platform darwin
13 != darwin 14)

pypy 2.4.0_0 2.4.0_0 (platform darwin 13 !=
darwin 14)

v8 3.23.17.23_1 3.23.17.23_1 (platform
darwin 13 != darwin 14)

The failure of gcc47 and gcc48 seem to be connected to the failure to
configure llvm-3.3

Here's the specific llvm-3.3 error:

Error: org.macports.configure for port llvm-3.3 returned: configure
failure: command execution failed

I will attach the log file for the llvm-3.3 error.

pypy fails because of a checksum mismatch:

Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2

Error: org.macports.checksum for port pypy returned: Unable to verify
file checksums

I'm not sure what the problem with v8 is so I'll try to attach the log
file for that as well.

On Sat, Oct 18, 2014 at 8:16 PM, Ryan Schmidt ryandes...@macports.org
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 Yosemite,
and cmake along with other ports such as pypy etc fail to upgrade properly.
I am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1 to
be released

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco oraclmas...@gmail.com
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 now. Migration tells you
to remove and reinstall for a reason.

(And ultimately that reason is Apple changing things as it sees fit,
regardless of the effect on downstream folks like MacPorts and Homebrew.
The latter is good at ignoring those reasons and then causing
incomprehensible problems down the road... although they're getting better
about it, slowly, having repeatedly had to learn the hard way why MacPorts
does things in ways they consider stupid.)

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On 19 Oct 2014, at 6:00 pm, Carlo Tambuatco oraclmas...@gmail.com 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
simpler solution.

So do i take it that you didn't do this when you upgraded, i.e. You didn't
properly follow the migration guide ? If so, then thats your problem. You need
to do what it says, there is no alternative.

On Sun, Oct 19, 2014 at 12:57 PM, Chris Jones jon...@hep.phy.cam.ac.uk
wrote:
Hi,

On 19 Oct 2014, at 5:50 pm, Carlo Tambuatco oraclmas...@gmail.com wrote:

When you say you upgraded all your ports, did you do this exactly how the
guide says ? I.e. Did you first uninstall them all, then, reinstall them
from scratch ?

From the macports migration page:

Several other settings in macports.conf have changed their defaults over
the years. Take a moment to compare each line of your macports.conf with
the corresponding line in macports.conf.default in the same directory.
Unless you know a reason why a line your settings file should be different
from the defaults, adopt the line from the defaults file.

I don't really know enough about these settings to mess with them myself.
Did you change any values in the macports.conf file or
macports.conf.default file to get it to work? Other than this I can't think
of anything I did that is different to the steps for migrating macports.

I did not touch any conf files.

https://guide.macports.org/chunked/installing.macports.uninstalling.html

Then reinstall from scratch.

Chris

On Sun, Oct 19, 2014 at 12:34 PM, Chris Jones jon...@hep.phy.cam.ac.uk
wrote:
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 did not
follow the migration instructions..

Chris

On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco oraclmas...@gmail.com 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)

gcc47 4.7.4_1 4.7.4_1 (platform darwin 13 !=
darwin 14)

gcc48 4.8.3_0 4.8.3_0 (platform darwin 13 !=
darwin 14)

libgcc 4.9.1_0 4.9.1_0 (platform darwin 13 !=
darwin 14)

llvm-3.3 3.3_4 3.3_4 (platform darwin 13 !=
darwin 14)

py26-wxpython-2.8 2.8.12.1_0 2.8.12.1_0 (platform darwin
13 != darwin 14)

pypy 2.4.0_0 2.4.0_0 (platform darwin 13 !=
darwin 14)

v8 3.23.17.23_1 3.23.17.23_1 (platform
darwin 13 != darwin 14)

The failure of gcc47 and gcc48 seem to be connected to the failure to
configure llvm-3.3

Here's the specific llvm-3.3 error:

Error: org.macports.configure for port llvm-3.3 returned: configure
failure: command execution failed

I will attach the log file for the llvm-3.3 error.

pypy fails because of a checksum mismatch:

Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2

Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2

Error: org.macports.checksum for port pypy returned: Unable to verify
file checksums

I'm not sure what the problem with v8 is so I'll try to attach the log
file for that as well.

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 allber...@gmail.com wrote:

 On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco oraclmas...@gmail.com
 javascript:_e(%7B%7D,'cvml','oraclmas...@gmail.com'); 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 now. Migration tells you
 to remove and reinstall for a reason.

 (And ultimately that reason is Apple changing things as it sees fit,
 regardless of the effect on downstream folks like MacPorts and Homebrew.
 The latter is good at ignoring those reasons and then causing
 incomprehensible problems down the road... although they're getting better
 about it, slowly, having repeatedly had to learn the hard way why MacPorts
 does things in ways they consider stupid.)

 --
 brandon s allbery kf8nh   sine nomine
 associates
 allber...@gmail.com javascript:_e(%7B%7D,'cvml','allber...@gmail.com');
  ballb...@sinenomine.net
 javascript:_e(%7B%7D,'cvml','ballb...@sinenomine.net');
 unix, openafs, kerberos, infrastructure, xmonad
 http://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

2014-10-19 Thread Dominik Reichardt

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 oraclmas...@gmail.com:
 
 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 allber...@gmail.com wrote:
 On Sun, Oct 19, 2014 at 1:00 PM, Carlo Tambuatco oraclmas...@gmail.com 
 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 now. Migration tells you 
 to remove and reinstall for a reason.
 
 (And ultimately that reason is Apple changing things as it sees fit, 
 regardless of the effect on downstream folks like MacPorts and Homebrew. The 
 latter is good at ignoring those reasons and then causing incomprehensible 
 problems down the road... although they're getting better about it, slowly, 
 having repeatedly had to learn the hard way why MacPorts does things in ways 
 they consider stupid.)
 
 -- 
 brandon s allbery kf8nh   sine nomine associates
 allber...@gmail.com  ballb...@sinenomine.net
 unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

2014-10-19 Thread Michael


 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 minecraft videos
http://YouTube.com/keybounce

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

2014-10-19 Thread Dave Horsfall

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 names such as Melbourne and Brisbane :-)

-- 
Dave Horsfall (VK2KFU)
http://www.horsfall.org/spam.html (and check the home page)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 1:46 PM, Dave Horsfall d...@horsfall.org 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  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

You mean Mel-buhn and Bris-ben?

On Sun, Oct 19, 2014 at 1:46 PM, Dave Horsfall d...@horsfall.org 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 pronounced
 ARK-cun-sor, for example.  In return I'll happily teach anyone how to
 pronounce Australian names such as Melbourne and Brisbane :-)

 --
 Dave Horsfall (VK2KFU)
 http://www.horsfall.org/spam.html (and check the home page)
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 11:15 AM, Carlo Tambuatco oraclmas...@gmail.com 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.

 gcc47  4.7.4_1  4.7.4_1  (platform darwin 13 != 
 darwin 14)  
 
 gcc48  4.8.3_0  4.8.3_0  (platform darwin 13 != 
 darwin 14)  
 
 libgcc 4.9.1_0  4.9.1_0  (platform darwin 13 != 
 darwin 14)  
 
 llvm-3.3   3.3_4  3.3_4  (platform darwin 13 != darwin 
 14)  

I suspect you don't actually care about llvm-3.3, and that it's just getting 
pulled in because of cctools +llvm33 and ld64 +llvm33 (which the GCC ports 
require). You may want to switch to the +llvm35 variants of those ports before 
trying to install GCC again.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 12:16 PM, Carlo Tambuatco oraclmas...@gmail.com 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
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 1:46 PM, Dave Horsfall d...@horsfall.org 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 Arkansas is pronounced 
 ARK-cun-sor, for example.

Who told you that? I say AR-kin-saw.

vq

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:09 PM, Lawrence Velázquez lar...@macports.org
wrote:

 On Oct 19, 2014, at 12:16 PM, Carlo Tambuatco oraclmas...@gmail.com
 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


Agreed. Somebody should get on that pronto.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 12:57 PM, Chris Jones jon...@hep.phy.cam.ac.uk 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 ports, and the ones he 
listed are the ones that failed for one reason or another. Since they are left 
over from Mavericks, base considers them outdated.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 11:15 AM, Carlo Tambuatco oraclmas...@gmail.com 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 string, line 1
:info:configure import sys; print sys.version.split()[0]
:info:configure ^
:info:configure SyntaxError: invalid syntax

It looks like you used `port select` to make Python 3.x your default, and 
LLVM's configure is choking on it. You should run `sudo port select --set 
python none` and try again.

Actually you should still switch to LLVM 3.5, as I mentioned earlier.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade





 On 19 Oct 2014, at 7:26 pm, Lawrence Velázquez lar...@macports.org wrote:
 
 On Oct 19, 2014, at 12:57 PM, Chris Jones jon...@hep.phy.cam.ac.uk 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 ports, and the ones 
 he listed are the ones that failed for one reason or another. Since they are 
 left over from Mavericks, base considers them outdated.

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.

 
 vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:25 PM, Lawrence Velázquez lar...@macports.org
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 select`ed python.) If it wants
the system python, it should be forced to find only /usr/bin/python;
otherwise it should depend on a specific MacPorts python.

(Trace mode would be helpful here.)

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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 Jones jon...@hep.phy.cam.ac.uk
wrote:





  On 19 Oct 2014, at 7:26 pm, Lawrence Velázquez lar...@macports.org
 wrote:
 
  On Oct 19, 2014, at 12:57 PM, Chris Jones jon...@hep.phy.cam.ac.uk
 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 ports, and the
 ones he listed are the ones that failed for one reason or another. Since
 they are left over from Mavericks, base considers them outdated.

 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.

 
  vq

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Sun, Oct 19, 2014 at 2:33 PM, Carlo Tambuatco oraclmas...@gmail.com
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 approach this problem...


Indeed, the happy-go-lucky way: hope stuff will work because it looks like
it did and then get incomprehensible problems later on.

I know you'd really prefer to cut corners, but do you really want to pay
for it later on?

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 2:30 PM, Chris Jones jon...@hep.phy.cam.ac.uk 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't 
(doesn't?) always work, which is why the official migration procedure involves 
starting from a clean slate.

http://thread.gmane.org/gmane.os.apple.macports.devel/28290/focus=28291

But so far, most of Carlo's problems seem like they can be explained/fixed.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

On Oct 19, 2014, at 2:33 PM, Carlo Tambuatco oraclmas...@gmail.com 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 approach this problem...

Didn't you say (or intimate) that you upgraded all your ports? That means 
you've trashed and recompiled them all anyway, so you're not really saving any 
time.

There are undoubtedly other ways to go about this, but starting from scratch is 
the most reliable and usually works out best for everyone involved.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade

2014-10-19 Thread Jean-François Gobin

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 used to uninstall everything/reinstall everything or even port
a list of ports to another machine.

J.


2014-10-19 14:47 GMT-04:00 Lawrence Velázquez lar...@macports.org:

 On Oct 19, 2014, at 2:33 PM, Carlo Tambuatco oraclmas...@gmail.com
 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 approach this problem...

 Didn't you say (or intimate) that you upgraded all your ports? That means
 you've trashed and recompiled them all anyway, so you're not really saving
 any time.

 There are undoubtedly other ways to go about this, but starting from
 scratch is the most reliable and usually works out best for everyone
 involved.

 vq
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users




-- 
Jean-François Gobin, Ing., CCENT, CCNA, CCNA Security
http://newsfromjean.blogspot.com/
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite upgrade