Re: Updating php56-apache2handler gives configure error

2015-11-02 Thread Murray Eisenberg

> On 1 Nov2015, at 5:10 PM, Brandon Allbery  wrote:
> 
> On Sun, Nov 1, 2015 at 5:07 PM, Murray Eisenberg  
> wrote:
> My misunderstanding: I didn't realize that just because "which perl5" showed 
> "/opt/local/bin/perl5" and I had an active perl5.xx installed, I still had to 
> do the step you showed.
> 
> Hm. Sounds like a dangling link to a no longer installed perl --- but that's 
> something that "port select" can cause but the perl5 port shouldn't. 
> Confusing.

Unless I'm misunderstanding something, "port select" does not work at all for 
perl:

sudo port select --list perl5
Warning: Unable to get active selected version: The specified group 'perl5' 
does not exist.
Error: The 'list' command failed: The specified group 'perl5' does not 
exist.

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: p5.16-libapreq2 won't reinstall after migration to El Capitan - SOLVED!

2015-11-02 Thread Murray Eisenberg

> On27 Oct 2015 23:27:27 +0100,Murray Eisenberg  
> wrote:
> 
> 
> On Tue, Oct 27, 2015 at 11:03 PM, Murray Eisenberg wrote:
>> After migrating macports from Yosemite to El Capitan, installing 
>> p5.16-libapreq2 failed during build its all-too-tamiliar error:
>> 
>>  Can't locate ModPerl/MM.pm in @INC
>> 
>> Following a recommendation when the same thing happened under Yosemite, with 
>> the reinstalled macports under El Capitan I did follow the same procedure:
>> 
>>  * install perl5 with a variant that corresponds to the perl version you 
>> want to use
>> 
>>I think I got this right; I have:
>> 
>>perl5 @5.16.3_0+perl5_16
>>perl5 @5.16.3_0+perl5_20 (active)
>> 
>>  * forcibly rebuild mod_perl2 from source (i.e. "sudo port -ns upgrade 
>> --force mod_perl2") or if you have not yet installed mod_perl2, install it 
>> from source (i.e. "sudo port -s install mod_perl2")
>> 
>>I did the force rebuild of mod_perl2.
>> 
>>  * install the p5-libapreq2 support for the perl version you want to use
>> 
>>I tried "sudo port install p5.16-libapreq2", which failed.
>> 
>> 
>> Also, I note that there no longer seems to be any p5.20-libapreq2 port 
>> available.
>> 
>> How fix??
> 
> If you want to keep using perl5perl +perl5_20, then you need to
> install mod_perl2 +perl5_20 and p5.20-libapreq2. I have no clue why
> p5.20-libapreq is missing and thin could be fixed.
> 
> If you want to switch to 5.16, you need to install perl5 +perl5_16,
> then mod_perl2 +perl5_16 and finally p5.16-libapreq2.

The issue re p5.16-libapreq2 is solved!  After the migration, I had never 
activated a version of perl5 by doing "sudo install perl5 +perl5_16. Not doing 
that seems to be what caused failure to build mod_perl2 and hence prevented 
subsequent installation of p5.16-libapreq2.

(I do still wish a port p5.20-libapreq2 were available, so that I would not 
need to deal with the older versions of perl5.)


---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: Updating php56-apache2handler gives configure error

2015-11-02 Thread Brandon Allbery
On Mon, Nov 2, 2015 at 10:26 AM, Murray Eisenberg  wrote:

> >
> > Hm. Sounds like a dangling link to a no longer installed perl --- but
> that's something that "port select" can cause but the perl5 port shouldn't.
> Confusing.
>
> Unless I'm misunderstanding something, "port select" does not work at all
> for perl:
>

It doesn't. But one of the shortcomings of the "port select" mechanism in
general is that there are circumstances where it leaves dangling symlinks
around; the variants-based mechanism used by the perl ports can't normally
do this, unless you've been playing games with --force or manually removing
stuff. So I'm confused as to how you managed to have an invalid
/opt/local/bin/perl.

-- 
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: p5.16-libapreq2 won't reinstall after migration to El Capitan

2015-11-02 Thread Mojca Miklavec
On Tue, Nov 3, 2015 at 12:14 AM, Murray Eisenberg wrote:
> After uninstalling p5.16-libapeq2 and mod_perl2 + perl5_16, I was able to 
> install in order:
>
> perl5 + perl5_22
> mod_perl2 +perl5_22
>
> However, "port install  p5.22-libapreq2" still used mod_perl2 + perl5.20

Can you please try again the following:
port info mod_perl2
sudo port selfupdate
port info mod_perl2
sudo port install mod_perl2
port installed mod_perl2
(and tell me the variants reported by mod_perl2)?

For some weird reason "sudo port install mod_perl2 +perl5_22" would
also install "mod_perl2 + perl5_20" for me in the beginning, but that
was before I fixed the port and added perl5_22 to the list of
variants. (I'm curious why it picked 5.20; I would expect 5.16 at
best.)

So maybe you did a selfupdate too fast. Unless you have a second copy
of the Portfile somewhere, that's my only explanation, otherwise you
shouldn't have ended up with +perl5_20. So hopefully another
selfupdate and installation of mod_perl2 will fix the issue.

> and the process ends with error that mod_perl2 must be installed with 
> +perl5_22 !

At least the error message is more clear now. Earlier you would have
ended up with a cryptic build error saying that one perl module was
missing.

> So no go.

You seem to be almost there.

Mojca


>> On 2 Nov2015, at 11:14 AM, Mojca Miklavec  wrote:
>>
>> Dear Murray,
>>
>> On Mon, Nov 2, 2015 at 4:20 PM, Murray Eisenberg wrote:
>>>
>>> The issue re p5.16-libapreq2 is solved!  After the migration, I had never 
>>> activated a version of perl5 by doing "sudo install perl5 +perl5_16. Not 
>>> doing that seems to be what caused failure to build mod_perl2 and hence 
>>> prevented subsequent installation of p5.16-libapreq2.
>>>
>>> (I do still wish a port p5.20-libapreq2 were available, so that I would not 
>>> need to deal with the older versions of perl5.)
>>
>> I just added it now (you could try to switch to 5.22, else you'll be
>> "outdated" soon again).
>>
>> You will have to uninstall or deactivate p5.16-libapreq2, install
>> "perl5 +perl5_22" and "mod_perl2 +perl5_22" and finally install
>> p5.22-libapreq2.
>>
>> Then again it might be nice to get some feedback. Running the
>> testsuite on p5.22-libapre2 fails for some tests. I got rid of some
>> failures by upgrading mod_perl2 to 2.0.9, but some failures remain.
>>
>> Mojca
>>
>> (PS: you might have to wait for half an hour for the port definitions
>> to catch up if you are using rsync for selfupdate)
>
> ---
> Murray Eisenbergmurrayeisenb...@gmail.com
> 503 King Farm Blvd #101 Home (240)-246-7240
> Rockville, MD 20850-6667Mobile (413)-427-5334
>
>
>
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: p5.16-libapreq2 won't reinstall after migration to El Capitan - SOLVED!

2015-11-02 Thread Mojca Miklavec
Dear Murray,

On Mon, Nov 2, 2015 at 4:20 PM, Murray Eisenberg wrote:
>
> The issue re p5.16-libapreq2 is solved!  After the migration, I had never 
> activated a version of perl5 by doing "sudo install perl5 +perl5_16. Not 
> doing that seems to be what caused failure to build mod_perl2 and hence 
> prevented subsequent installation of p5.16-libapreq2.
>
> (I do still wish a port p5.20-libapreq2 were available, so that I would not 
> need to deal with the older versions of perl5.)

I just added it now (you could try to switch to 5.22, else you'll be
"outdated" soon again).

You will have to uninstall or deactivate p5.16-libapreq2, install
"perl5 +perl5_22" and "mod_perl2 +perl5_22" and finally install
p5.22-libapreq2.

Then again it might be nice to get some feedback. Running the
testsuite on p5.22-libapre2 fails for some tests. I got rid of some
failures by upgrading mod_perl2 to 2.0.9, but some failures remain.

Mojca

(PS: you might have to wait for half an hour for the port definitions
to catch up if you are using rsync for selfupdate)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: error upgrading gcc48 port

2015-11-02 Thread Fabrizio Salvatore
Thanks a lot, this actually solved all my issues! Thanks again!

Fab

On 2 November 2015 at 00:36, Ryan Schmidt  wrote:

>
> On Nov 1, 2015, at 6:35 PM, Brandon Allbery wrote:
>
> > On Sun, Nov 1, 2015 at 7:31 PM, Fabrizio Salvatore <
> p.fabrizio.salvat...@googlemail.com> wrote:
> > I do indeed use ROOT as analysis package: is there a version for gcc49
> or gcc5?
> >
> > "port variants root5"
> > Which, here, shows (among many others) the following variants
> >
> >gcc43: Build with gfortran from gcc43
> >  * conflicts with gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5
> >gcc44: Build with gfortran from gcc44
> >  * conflicts with gcc43 gcc45 gcc46 gcc47 gcc48 gcc49 gcc5
> >gcc45: Build with gfortran from gcc45
> >  * conflicts with gcc43 gcc44 gcc46 gcc47 gcc48 gcc49 gcc5
> >gcc46: Build with gfortran from gcc46
> >  * conflicts with gcc43 gcc44 gcc45 gcc47 gcc48 gcc49 gcc5
> >gcc47: Build with gfortran from gcc47
> >  * conflicts with gcc43 gcc44 gcc45 gcc46 gcc48 gcc49 gcc5
> >gcc48: Build with gfortran from gcc48
> >  * conflicts with gcc43 gcc44 gcc45 gcc46 gcc47 gcc49 gcc5
> >gcc49: Build with gfortran from gcc49
> >  * conflicts with gcc43 gcc44 gcc45 gcc46 gcc47 gcc48 gcc5
> > [+]gcc5: Build with gfortran from gcc5
> >  * conflicts with gcc43 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49
> >
> > The [+] means that if you were to install it from scratch instead of
> upgrading, you'd get the gcc5 variant.
> >
> > I think you want: sudo port upgrade root5 -gcc48 +gcc5
>
> Might have to use:
>
> sudo port upgrade --enforce-variants root5 -gcc48 +gcc5
>
>


-- 
+++
Dr Fabrizio Salvatore|e-mail: p.f.salvat...@sussex.ac.uk
Department of Physics and Astronomy, University of Sussex,
Brighton, Sussex, BN1 9QH, United Kingdom
Tel.:  +44 (0)1273 67 8749; Fax: +44 (0)1273 67 8068
http://epp.phys.susx.ac.uk/epp/FabrizioSalvatore

facebook.com/p.fabrizio.salvatore
+++
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: p5.16-libapreq2 won't reinstall after migration to El Capitan

2015-11-02 Thread Murray Eisenberg
After uninstalling p5.16-libapeq2 and mod_perl2 + perl5_16, I was able to 
install in order:

perl5 + perl5_22
mod_perl2 +perl5_22
   
However, "port install  p5.22-libapreq2" still used mod_perl2 + perl5.20 and 
the process ends with error that mod_perl2 must be installed with +perl5_22 !  

So no go.


> On 2 Nov2015, at 11:14 AM, Mojca Miklavec  wrote:
> 
> Dear Murray,
> 
> On Mon, Nov 2, 2015 at 4:20 PM, Murray Eisenberg wrote:
>> 
>> The issue re p5.16-libapreq2 is solved!  After the migration, I had never 
>> activated a version of perl5 by doing "sudo install perl5 +perl5_16. Not 
>> doing that seems to be what caused failure to build mod_perl2 and hence 
>> prevented subsequent installation of p5.16-libapreq2.
>> 
>> (I do still wish a port p5.20-libapreq2 were available, so that I would not 
>> need to deal with the older versions of perl5.)
> 
> I just added it now (you could try to switch to 5.22, else you'll be
> "outdated" soon again).
> 
> You will have to uninstall or deactivate p5.16-libapreq2, install
> "perl5 +perl5_22" and "mod_perl2 +perl5_22" and finally install
> p5.22-libapreq2.
> 
> Then again it might be nice to get some feedback. Running the
> testsuite on p5.22-libapre2 fails for some tests. I got rid of some
> failures by upgrading mod_perl2 to 2.0.9, but some failures remain.
> 
> Mojca
> 
> (PS: you might have to wait for half an hour for the port definitions
> to catch up if you are using rsync for selfupdate)

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334





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


Re: Updating php56-apache2handler gives configure error

2015-11-02 Thread Ryan Schmidt

On Nov 2, 2015, at 9:28 AM, Brandon Allbery wrote:
> 
> On Mon, Nov 2, 2015 at 10:26 AM, Murray Eisenberg wrote:
> 
>> Hm. Sounds like a dangling link to a no longer installed perl --- but that's 
>> something that "port select" can cause but the perl5 port shouldn't. 
>> Confusing.
> 
> Unless I'm misunderstanding something, "port select" does not work at all for 
> perl:
> 
> It doesn't.

That's correct. That bug is:

https://trac.macports.org/ticket/29763

It is not an easy bug to fix because the select mechanism is defined to be 
something for the user to use, but we have zillions of ports relying on the 
perl symlink the perl5 port installs. One solution might be to change all ports 
that currently depend on that perl symlink so that they depend on a specific 
version of perl instead, but that's a lot of work, and work that would want to 
be repeated every time we declare that a new version of perl shall be the 
default version, so that isn't great. It's been suggested that this and other 
issues would be avoided by abandoning the idea of offering multiple versions of 
perl and going back to a single version of perl, like we had years ago.


> But one of the shortcomings of the "port select" mechanism in general is that 
> there are circumstances where it leaves dangling symlinks around;

That bug is:

https://trac.macports.org/ticket/47755


> the variants-based mechanism used by the perl ports can't normally do this, 
> unless you've been playing games with --force or manually removing stuff. So 
> I'm confused as to how you managed to have an invalid /opt/local/bin/perl.

Evidently Murray forcibly deactivated his perl5 port, or something went wrong 
in MacPorts that caused it to become deactivated. The solution would be to 
reactivate the desired version/variant of the perl5 port.


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