Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Mar 02, 2014, at 01:29, Ryan Schmidt wrote: On Mar 1, 2014, at 06:48, René J.V. Bertin rjvber...@gmail.com wrote: Given that I do not myself have any direct requirements on perl versions, shouldn't I just have removed all references to specific perl5 versions/variants, or bumped all +perl5_12 to +perl5_16? I recommend that. Ok, good in that case I didn't wait - seems it worked. I even could uninstall perl5.12 without complaints. I've had some errors about variants that apparently were (attempted to be) installed with the perl5_12 but a clean and manual (re)install without reference to perl variants seems to have done the trick. I had to kill the initial installation of ImageMagick because clang spent 447 minutes on compiling coders/png.c but the 2nd time the restore script encountered the package it started staging (almost) immediately. Weird, out-of-memory condition in the VM, maybe? I’d try “sudo port uninstall installed and name:^p5.12”. If nothing depends on them, that should succeed. If that fails, it’ll tell you what port requires it. You can then investigate whether that port offers variants for newer versions of perl. Thing is, none of the p5.12 ports install because of a missing package in CPAN (YAML if memory serves me well, let me know if I it's worth the time to raise an issue on this; I'd reckon one of you can just as easily try to install a light p5.12 package and decide whether CPAN is indeed missing required bits, and whether that justifies removing the p5.12 packages from the repo all together?) Since it was only recently that the default perl was changed from 5.12 to 5.16, there are probably still many ports that depend unconditionally on 5.12 and have yet to be updated to 5.16. If you find such ports, please file tickets. Oh great, I love playing guinea pig --- groink! :) Fortunately it seems for now that p5.16 ports have been pulled in where required. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
OK, after additionally getting rid of the reference to webkit-gtk3-2.0, my restore process terminated successfully. Thanks for the support. Is there any interest in posting the list of installed ports I fed to restore.tcl? R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
I'm continuing my endeavours after a little break ...
The source install I'm upgrading for 10.9 had 2 perl5 variants installed:
perl5 @5.12.4_0+perl5_12
perl5 @5.12.4_0+perl5_16 (active)
both presumably dependencies of ports I requested, and their upgrades over the
time (I'm running 10.6 with MacPorts since autumn 2010). I also have a whole
slew (55) of p5.12-* ports, and a few p5.16-* ports.
It looks like having those 2 variants may be causing reinstallation issues, as
I've seen many a message referring to @perl5_12 when apparently a port didn't
request a specific perl5 variant, and failures on the installation of all p5.12
ports.
(Example extract from one of the build logs:
:notice:configure --- Configuring p5.12-error
:debug:configure Using compiler 'Xcode Clang'
:debug:configure Executing org.macports.configure (p5.12-error)
:debug:configure Environment: CPATH='/Volumes/Debian/MacPorts/include'
CFLAGS='-Os' CPPFLAGS='-I/Volumes/Debian/MacPorts/include' CXXFLAGS='-Os'
LIBRARY_PATH='/Volumes/Debian/MacPorts/lib' MACOSX_DEPLOYMENT_TARGET='10.9'
CXX='/usr/bin/clang++'
CC_PRINT_OPTIONS_FILE='/Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-error/p5.12-error/work/.CC_PRINT_OPTIONS'
F90FLAGS='-Os' LDFLAGS='-L/Volumes/Debian/MacPorts/lib
-Wl,-headerpad_max_install_names' FCFLAGS='-Os' OBJC='/usr/bin/clang'
OBJCXX='/usr/bin/clang++' INSTALL='/usr/bin/install -c'
PERL_AUTOINSTALL='--skipdeps' FFLAGS='-Os' OBJCFLAGS='-Os' OBJCXXFLAGS='-Os'
CC_PRINT_OPTIONS='YES' CC='/usr/bin/clang'
:debug:configure Assembled command: 'cd
/Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-error/p5.12-error/work/Error-0.17016
/Volumes/Debian/MacPorts/bin/perl5.12 Makefile.PL INSTALLDIRS=vendor
CC=/usr/bin/clang LD=/usr/bin/clang'
:debug:configure Executing command line: cd
/Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-error/p5.12-error/work/Error-0.17016
/Volumes/Debian/MacPorts/bin/perl5.12 Makefile.PL INSTALLDIRS=vendor
CC=/usr/bin/clang LD=/usr/bin/clang
:info:configure Checking if your kit is complete...
:info:configure Looks good
:info:configure CPAN::Meta::YAML 0.002 is not available
:info:configure at
/Volumes/Debian/MacPorts/lib/perl5/site_perl/5.12.4/CPAN/Meta.pm line 320.
:info:configure Command failed: cd
/Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-error/p5.12-error/work/Error-0.17016
/Volumes/Debian/MacPorts/bin/perl5.12 Makefile.PL INSTALLDIRS=vendor
CC=/usr/bin/clang LD=/usr/bin/clang
:info:configure Exit code: 2
:error:configure org.macports.configure for port p5.12-error returned:
configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
while executing
$procedure $targetname
:info:configure Warning: targets not executed for p5.12-error:
org.macports.activate org.macports.configure org.macports.build
org.macports.destroot org.macports.install
:error:configure Failed to install p5.12-error
:debug:configure Registry error: p5.12-net-ssleay not registered as installed
active.
invoked from within
registry_active ${subport}
invoked from within
$workername eval registry_active \${subport}
:notice:configure Please see the log file for port p5.12-error for details:
/Volumes/Debian/MacPorts/var/macports/logs/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-error/p5.12-error/main.log
)
I hope I haven't overlooked anything in the docs, but how does the restore.tcl
script handle multiple perl5 variants/versions? Given that I do not myself have
any direct requirements on perl versions, shouldn't I just have removed all
references to specific perl5 versions/variants, or bumped all +perl5_12 to
+perl5_16? If so, can I rectify that WITHOUT having to start everything from
scratch?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Mar 1, 2014, at 06:48, René J.V. Bertin rjvber...@gmail.com wrote: Given that I do not myself have any direct requirements on perl versions, shouldn't I just have removed all references to specific perl5 versions/variants, or bumped all +perl5_12 to +perl5_16? I recommend that. If so, can I rectify that WITHOUT having to start everything from scratch? I’d try “sudo port uninstall installed and name:^p5.12”. If nothing depends on them, that should succeed. If that fails, it’ll tell you what port requires it. You can then investigate whether that port offers variants for newer versions of perl. Since it was only recently that the default perl was changed from 5.12 to 5.16, there are probably still many ports that depend unconditionally on 5.12 and have yet to be updated to 5.16. If you find such ports, please file tickets. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9
On Tuesday February 18 2014 22:10:53 Ryan Schmidt wrote: Things started out fine, but somehow I found myself with a 64bit-only libiconv (despite the fact that the database told me I had the universal variant, as requested), which of course gave problems. Couldn't figure out how to force-reinstall the port, For future reference: sudo port -ns upgrade --force libiconv Thanks. I tried with -f and possibly even with -n, but that resulted just in the usual post-install scan of the database. MacPorts does not have the capability to re-install older versions of ports; if you want that you have to follow the instructions in the howto/InstallingOlderPort wiki page. So no, the instructions will only leave you with the latest version of each port, because that’s all that MacPorts knows how to install. Good to know, also as a reminder not to uninstall older versions immediately after each upgrade as apparently there's no (easy) way back! R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 8:27 AM, René J.V. Bertin rjvber...@gmail.com wrote: So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? you didn't follow the Migration instructions correctly, specifically you missed https://trac.macports.org/wiki/Migration#ReinstallMacPorts [MacPorts picks up which tar/gnutar to use at install time] -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Wed, Feb 19, 2014 at 8:27 AM, René J.V. Bertin rjvber...@gmail.comwrote: So I uninstalled and cleaned my MacPorts installation as instructed and the called restore.tcl . Now builds are failing with :debug:extract Executing command line: cd /Volumes/Debian/MacPorts/var/macports/build/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_bsdmake/bsdmake/work /usr/bin/gzip -dc '/Volumes/Debian/MacPorts/var/macports/distfiles/bsdmake/bsdmake-24.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - :info:extract sh: /usr/bin/gnutar: No such file or directory Indeed I have no /usr/bin/gnutar, and I don't see where in the MacPorts conf files this parameters is set? Did you reinstall or upgrade the MacPorts base? Installing the latest MacPorts for Mavericks will fix this; upgrading the existing base (`sudo port selfupdate`) should detect it during configure and deal with it (but if you did that and it didn't, please file a bug on trac.macports.org). -- 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: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Hi, Did you reinstall or upgrade the MacPorts base? Installing the latest MacPorts for Mavericks will fix this; upgrading the existing base (`sudo port selfupdate`) should detect it during configure and deal with it (but if you did that and it didn't, please file a bug on trac.macports.org ). `sudo port selfupdate` will only fix this, if the current version of base is actually outdated, i.e. if you had 2.2.0 installed before upgrading to Mavericks. If you already had 2.2.1 installed before the OS upgrade, selfupdate will not reconfigure/rebuild and this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. I guess the selfupdate action should check whether current base has been built on an older OS and trigger the rebuild if it was. I know we recently added a field for the OS version when base was built, but I'm not sure we already trigger selfupdate on OS version mismatch. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 15:37, Clemens Lang wrote: this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. I guess the selfupdate action should check whether current base has been built on an older OS and trigger the rebuild if it was. I know we recently added a field for the OS version when base was built, but I'm not sure we already trigger selfupdate on OS version mismatch. In the end it must have come through. I've configured MacPorts to run install as a normal user (meaning I did the selfupdate without sudo, clearly that wasn't the best idea), and I also had to move a couple of older gnutar variants out of the path. Things are building now, I suppose using the system tar command. We'll see how far the process goes! Thanks for the suggestions in any case! R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 08:37, Clemens Lang wrote: `sudo port selfupdate` will only fix this, if the current version of base is actually outdated, i.e. if you had 2.2.0 installed before upgrading to Mavericks. If you already had 2.2.1 installed before the OS upgrade, selfupdate will not reconfigure/rebuild and this will not work. That's why I suggested using `sudo port -f selfupdate`, which skips the version check and forces the rebuild, but I now realize this might not have triggered a re-configure either. Why wouldn’t “sudo port -f selfupdate have triggered a re-configure and re-build? I thought that’s exactly what it would do. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Hi, Why wouldn’t “sudo port -f selfupdate have triggered a re-configure and re-build? I thought that’s exactly what it would do. It would certainly trigger a rebuild, I'm just not sure it would trigger a re-configure. If the files generated by configure were still in place and newer than the configure script, a re-configure might not happen unless you run make distclean first. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
Just saw --- Fetching distfiles for libstdcxx --- Verifying checksums for libstdcxx --- Extracting libstdcxx --- Configuring libstdcxx Error: libstdcxx has been made obsolete by the port libgcc. Please install libgcc instead. Error: org.macports.configure for port libstdcxx returned: obsolete port Please see the log file for port libstdcxx for details: /Volumes/Debian/MacPorts/var/macports/logs/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_lang_libstdcxx/libstdcxx/main.log popping up. The script is continuing, can I presume that libgcc will get installed automatically? R ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9 - missing gnutar?
On Feb 19, 2014, at 12:05, René J.V. Bertin rjvber...@gmail.com wrote: Just saw --- Fetching distfiles for libstdcxx --- Verifying checksums for libstdcxx --- Extracting libstdcxx --- Configuring libstdcxx Error: libstdcxx has been made obsolete by the port libgcc. Please install libgcc instead. Error: org.macports.configure for port libstdcxx returned: obsolete port Please see the log file for port libstdcxx for details: /Volumes/Debian/MacPorts/var/macports/logs/_Volumes_Debian_MacPorts_var_macports_sources_rsync.macports.org_release_ports_lang_libstdcxx/libstdcxx/main.log popping up. The script is continuing, can I presume that libgcc will get installed automatically? Sure, if libgcc is required by another port you’re installing (i.e. any of the gcc4x ports). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
upgrading MacPorts after updating from 10.6 to 10.9
I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be updated by doing the usual port selfupdate port upgrade outdated sequence - possibly with -f and -p to have the process come through? Also (and I know this is off-topic), exactly how impossible is it to keep XCode 3.2.6 installed alongside XCode 5? The OS updater didn't kick /Developer off and googling suggests that it might be doable, but does anyone on here have experience with actually running the IDE? Thanks, René ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9
On Tue, Feb 18, 2014 at 10:21 AM, René J.V. Bertin rjvber...@gmail.comwrote: I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be updated by doing the usual port selfupdate port upgrade outdated sequence - possibly with -f and -p to have the process come through? http://trac.macports.org/wiki/Migration always after an OS upgrade. port upgrade outdated is not expected to work, because Apple can and does (and very much did in 10.9) make major changes. Also (and I know this is off-topic), exactly how impossible is it to keep XCode 3.2.6 installed alongside XCode 5? The OS updater didn't kick /Developer off and googling suggests that it might be doable, but does anyone on here have experience with actually running the IDE? I wouldn't expect it to work, to be honest; too much stuff has changed. -- 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: upgrading MacPorts after updating from 10.6 to 10.9
Hi, I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be updated by doing the usual port selfupdate port upgrade outdated sequence - possibly with -f and -p to have the process come through? First: -p is considered harmful when installing ports. That's because MacPorts usually ensures all its dependencies are upgraded to the current version before upgrading a port. With -p, if a dependency fails to build, MacPorts will happily continue on to the dependent port, building it against the older version of the dependency. That might fail unexpectedly, or defy the point of the upgrade, if it was a revision bump to rebuild against a newer version of library, or it might actually work but lead to problems later on when mixing this port with binaries built by our buildbot which expect the newer dependency version. So, in summary, don't use -p unless everything you do is download stuff (which is really the only reason why it's there in the first place). You might be able to get around re-installing MacPorts itself by running sudo port -f selfupdate, which will make sure your version of MacPorts base is built on Mavericks and for Mavericks. As for the ports, avoiding Migration is probably not possible, especially because of the drop of libtool .la files when updating to Mavericks. Deleting only half of them leads to numerous problems and failed build, only deleting them all at once will work fine. Now, obviously since MacPorts upgrades all dependencies before attempting to upgrade a port itself, all .la files used by a port should theoretically be gone by the time MacPorts rebuilds a port. In practice, automagic dependencies (i.e. dependencies that are picked up and used when present) will rain on your parade at this point. Though it technically it is a bug to have automagic dependencies in a MacPorts port, there still are many that do. Safe yourself some trouble and follow migration. If you'd like to automate the process use the script from the Automatically reinstall ports ports paragraph at http://trac.macports.org/wiki/Migration#automatic. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9
On Feb 18, 2014, at 16:35, Clemens Lang wrote: later on when mixing this port with binaries built by our buildbot which expect the newer dependency version. So, in summary, don't use -p unless everything you do is download stuff (which is really the only reason why it's there in the first place). Hmmm, you've got a point. Don't think I ever ran into it but I'll remember (off late on 10.6 it was too tempting to use -p). You might be able to get around re-installing MacPorts itself by running sudo port -f selfupdate, which will make sure your version of MacPorts base is built on Mavericks and for Mavericks. ... Safe yourself some trouble and follow migration. If you'd like to automate the process use the script from the Automatically reinstall ports ports paragraph at http://trac.macports.org/wiki/Migration#automatic. Things started out fine, but somehow I found myself with a 64bit-only libiconv (despite the fact that the database told me I had the universal variant, as requested), which of course gave problems. Couldn't figure out how to force-reinstall the port, so I uninstalled it, and then of course gnutar no longer worked. Long story short, I'm following the migration guide now. I presume the tcl restore script restores all ports in the input list, and not only the most recent versions of the listed ports, so I'd have to uninstall all inactive ports before generating the list if I don't want to have to prune it by hand? R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: upgrading MacPorts after updating from 10.6 to 10.9
On Feb 18, 2014, at 17:23, René J.V. Bertin rjvber...@gmail.com wrote: On Feb 18, 2014, at 16:35, Clemens Lang wrote: later on when mixing this port with binaries built by our buildbot which expect the newer dependency version. So, in summary, don't use -p unless everything you do is download stuff (which is really the only reason why it's there in the first place). Hmmm, you've got a point. Don't think I ever ran into it but I'll remember (off late on 10.6 it was too tempting to use -p). You might be able to get around re-installing MacPorts itself by running sudo port -f selfupdate, which will make sure your version of MacPorts base is built on Mavericks and for Mavericks. ... Safe yourself some trouble and follow migration. If you'd like to automate the process use the script from the Automatically reinstall ports ports paragraph at http://trac.macports.org/wiki/Migration#automatic. Things started out fine, but somehow I found myself with a 64bit-only libiconv (despite the fact that the database told me I had the universal variant, as requested), which of course gave problems. Couldn't figure out how to force-reinstall the port, For future reference: sudo port -ns upgrade --force libiconv so I uninstalled it, and then of course gnutar no longer worked. Long story short, I'm following the migration guide now. I presume the tcl restore script restores all ports in the input list, and not only the most recent versions of the listed ports, so I'd have to uninstall all inactive ports before generating the list if I don't want to have to prune it by hand? MacPorts does not have the capability to re-install older versions of ports; if you want that you have to follow the instructions in the howto/InstallingOlderPort wiki page. So no, the instructions will only leave you with the latest version of each port, because that’s all that MacPorts knows how to install. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
