On Fri, Nov 16, 2012 at 6:38 PM, Ryan Schmidt wrote:
>
> On Nov 16, 2012, at 14:48, Daniel J. Luke wrote:
>
>> If you have a bunch of modules that you installed yourself (not with
>> macports) then you'll have to deal with them yourself as well.
>
> We usually recommend you not install perl modu
On Nov 16, 2012, at 14:48, Daniel J. Luke wrote:
> If you have a bunch of modules that you installed yourself (not with
> macports) then you'll have to deal with them yourself as well.
We usually recommend you not install perl modules yourself, nor install any
other software into the MacPorts
On Nov 16, 2012, at 3:24 PM, Alejandro Imass wrote:
> I still don't understand very well how MacPorts layers the older
> versions of stuff.
Maybe the guide helps? http://guide.macports.org/#internals.images
> In other words, all this happened when I upgraded
> Perl. I work with Catalyst so I had
On Fri, Nov 16, 2012 at 2:59 PM, Jeremy Lavergne
wrote:
>> I cut the sentence short here and makes no sense. What I meant to say
[...]
>> to fix it so that is what I'm asking: Is there a way to increase the
>> verbosity or something that would tell me exactly what binaries it's
>> referring to ?
> I cut the sentence short here and makes no sense. What I meant to say
> is that it would seem that some binaries depend on dylibs that are
> actually part of Perl modules and that seems really weird. I have no
> way of finding out exactly which binaries were depending on these
> dylibs.
>
> Exam
On Thu, Nov 15, 2012 at 6:34 PM, Alejandro Imass wrote:
> On Thu, Nov 15, 2012 at 6:21 PM, Brandon Allbery wrote:
>> On Thu, Nov 15, 2012 at 6:11 PM, Alejandro Imass
>> wrote:
>>>
>>> fix on Perl but it didn't. Also, I can't seem to get port to tell me
> port command only. Apparently there are s
On Thu, Nov 15, 2012 at 6:21 PM, Brandon Allbery wrote:
> On Thu, Nov 15, 2012 at 6:11 PM, Alejandro Imass
> wrote:
>>
>> fix on Perl but it didn't. Also, I can't seem to get port to tell me
>> exactly which binary is complaining about the lining errors. Anyway
>
>
> rev-upgrade can't sensibly fi
On Thu, Nov 15, 2012 at 06:11:47PM -0500, Alejandro Imass wrote:
> Also, I can't seem to get port to tell me exactly which binary is
> complaining about the lining errors.
Try running sudo port -d -y rev-upgrade.
> Anyway after a long upgrade process, same thang:
>
> ---> Cleaning p5.12-term-re
On Thu, Nov 15, 2012 at 6:11 PM, Alejandro Imass wrote:
> fix on Perl but it didn't. Also, I can't seem to get port to tell me
> exactly which binary is complaining about the lining errors. Anyway
>
rev-upgrade can't sensibly fix stuff installed manually via CPAN; you will
need to fix them via CP
On Thu, Nov 15, 2012 at 5:12 PM, Jeremy Lavergne
wrote:
>> The question is how do I go about cleaning / fixing this?
>
> You could force upgrade everything that's active, that will make MacPorts
> reinstall the files from its archives. You can add "and category:perl" to
> narrow down what will g
> The question is how do I go about cleaning / fixing this?
You could force upgrade everything that's active, that will make MacPorts
reinstall the files from its archives. You can add "and category:perl" to
narrow down what will get reinstalled, or replace "active and category:perl"
with speci
Hi folks,
I upgraded Perl a while back and I erased some modules that I thought
I had installed for the previous version via the CPAN shell. I must
have erased some that were dependent for some binaries I installed via
macports.
All I get are a bunch of errors like:
Scanning binaries for linking
12 matches
Mail list logo
