On Wed, Mar 02, 2011 at 08:53:25AM +0100, Erwan David wrote:
ANd what abbout ports like ghostscript which depends on perl, but are not in
p5-* ?
If they do not build perl modules, they should not need to be rebuilt.
That said, it's quite possible I missed something; if you still have
problems
On Tue, Mar 1, 2011 at 3:20 AM, Andrew Watts ahwa...@gmail.com wrote:
I just tried uninstalling reinstalling 5.05, and I'm getting the
same behavior. I get identical results to yours from the file -l
commands.
Curiously, it's also not recognizing binaries (like its own) as Mach-O
On Mar 2, 2011, at 03:50, Bill Christensen wrote:
On Tue, Mar 1, 2011 at 2:48 PM, Ryan Schmidt wrote:
On Mar 1, 2011, at 12:38, Bill Christensen wrote:
Considering the error: perl module Locale::gettext required, is this
essentially fallout of the perl5 discussion currently going on?
Here's an example:
--- Computing dependencies for openssl
--- Building opensslError: Target org.macports.build returned:
shell command failed (see log for details)
Log for openssl is at: /opt/local/var/macports/logs/
_opt_local_var_macports_sources_rsync
On Mar 2, 2011, at 09:53, Philip Hudson wrote:
Here's an example:
--- Computing dependencies for openssl
--- Building opensslError: Target org.macports.build returned: shell
command failed (see log for details)
Log for openssl is at:
It looks like my MD5 is the same as yours. The only difference I can
see is that mine appears to be i386-specific for 10.5 and yours is a
universal binary for 10.6. I'll try building a universal binary.
andrew@drbernice ~ $ md5 /opt/local/share/misc/magic.mgc
MD5
Nope. Universal on my machine installs it for i386 and PPC, which
means I'm still running the i386 version that wasn't working before.
On Wed, Mar 2, 2011 at 11:05 AM, Andrew Watts ahwa...@gmail.com wrote:
It looks like my MD5 is the same as yours. The only difference I can
see is that mine
Hey Folks,
Okay. I've gone through the selfupdate and update outdated processes, but when
I look at ports installed it seems I have TWO versions of Perl installed:
perl5 @5.12.3_0+perl5_12 (active)
perl5.12 @5.12.3_1 (active)
If I understand correctly I need to uninstall:
perl5
On Wed, Mar 2, 2011 at 8:56 AM, Christopher Stone
listmeis...@thestoneforge.com wrote:
Hey Folks,
Okay. I've gone through the selfupdate and update outdated processes, but
when I look at ports installed it seems I have TWO versions of Perl installed:
perl5 @5.12.3_0+perl5_12 (active)
On Wed, Mar 02, 2011 at 10:56:40AM -0600, Christopher Stone wrote:
Hey Folks,
Okay. I've gone through the selfupdate and update outdated processes, but
when I look at ports installed it seems I have TWO versions of Perl installed:
perl5 @5.12.3_0+perl5_12 (active)
perl5.12 @5.12.3_1
On Mar 02, 2011, at 11:04, Eric Hall wrote:
You've got exactly what you should have, you shouldn't
have to uninstall anything. The perl5 port is a wrapper for
perl5.x (i.e. perl5.8, perl5.10, perl5.12) so that other ports
can depend on perl5, not a particular version of perl5.
Arg! Lets start out with that
My original installation of MacPorts was on a G4 iMac running 10.4.x. I'm NOT
sure what version it was, but PROBABLY older than 1.71
Upgraded from the G4 to an Intel MacBook Pro running 10.5... Used Migration
Assistant to move all the information from the G4
Don't upgrade, just delete your macports installation per the
instructions and start over from scratch. If you really want to know
which ports you had installed before, you can likely figure that out
by examining the directory structure in /opt/local.
That's what I'd do anyway. Macports doesn't
On Mar 2, 2011, at 15:43, Scott Webster wrote:
Don't upgrade, just delete your macports installation per the
instructions and start over from scratch. If you really want to know
which ports you had installed before, you can likely figure that out
by examining the directory structure in
On Wed, Mar 2, 2011 at 1:56 PM, Ryan Schmidt ryandes...@macports.org wrote:
Well, we do have the Migration instructions in the wiki, which ought to work
in most cases.
https://trac.macports.org/wiki/Migration
Those instructions basically accomplish reinstalling base and then
reinstalling
Hello,
I'm have tried to install qemu-usermode and get an error. In the log file the
stated reason is:
:info:configure WARNING: gcc looks like gcc 4.x
:info:configure Looking for gcc 3.x
:info:configure gcc 3.x not found!
:info:configure QEMU is known to have problems when compiled with gcc
On Mar 2, 2011, at 16:08, Scott Webster wrote:
On Wed, Mar 2, 2011 at 1:56 PM, Ryan Schmidt wrote:
https://trac.macports.org/wiki/Migration
Those instructions basically accomplish reinstalling base and then
reinstalling all your ports though, right? I definitely agree that
it's good to
Thanks all for your patience and responses, I got it hammered out The
version I was running initially looks like it was 1.6.0, it looks like it had a
somewhat different directory structure than what the removal documentation was
listing. Finally just removed the whole /opt directory
18 matches
Mail list logo
