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
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
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
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
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
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
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
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
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 ).
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
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
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
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:
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
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
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?
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
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
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
19 matches
Mail list logo
