Re: Why don't p5-* ports mark their dependencies?

[Daniel J. Luke]

On Jun 6, 2021, at 1:41 PM, Bill Cole 
 wrote:
> I *think* I've even worked out the right way to use that construct to make 
> Perl upgrades simpler, so I use the p5-* ports:

I gave up on trying to use this in any useful way a while ago - if you've got 
some way that it works, please share.

(FWIW, things would 'just work' if we'd ship the current version of perl5 and 
only have p5-foo ports).

For anything outside of MacPorts I recommend using perlbrew and just letting 
the macports perl install be only for things installed via macports.

-- 
Daniel J. Luke

Re: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration

[Bjarne D Mathiesen]

See the thread : Warning: -Wimplicit-function-declaration
from 20/05-2021

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina
2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM
ATI Radeon RX 590 8 GB

Why don't p5-* ports mark their dependencies?

[Bill Cole]

Not sure where the bug is here, but it's evident in 'port reclaim'.

The p5-* ports are basically placeholders for the p5.##- ports. I 
*think* I've even worked out the right way to use that construct to make 
Perl upgrades simpler, so I use the p5-* ports:


$ sudo port install p5-net-cidr p5-term-readline p5-test-fatal
--->  Computing dependencies for p5-net-cidr
The following dependencies will be installed:  p5.30-net-cidr
Continue? [Y/n]: y
--->  Fetching archive for p5.30-net-cidr
	--->  Attempting to fetch 
p5.30-net-cidr-0.200.0_0.darwin_18.noarch.tbz2 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-net-cidr
	--->  Attempting to fetch 
p5.30-net-cidr-0.200.0_0.darwin_18.noarch.tbz2.rmd160 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-net-cidr

--->  Installing p5.30-net-cidr @0.200.0_0
--->  Activating p5.30-net-cidr @0.200.0_0
--->  Cleaning p5.30-net-cidr
--->  Cleaning p5-net-cidr
--->  Computing dependencies for p5-term-readline
The following dependencies will be installed:  p5.30-term-readline
Continue? [Y/n]: y
--->  Fetching archive for p5.30-term-readline
	--->  Attempting to fetch 
p5.30-term-readline-1.140.0_0.darwin_18.noarch.tbz2 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-term-readline
	--->  Attempting to fetch 
p5.30-term-readline-1.140.0_0.darwin_18.noarch.tbz2.rmd160 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-term-readline

--->  Installing p5.30-term-readline @1.140.0_0
--->  Activating p5.30-term-readline @1.140.0_0
--->  Cleaning p5.30-term-readline
--->  Cleaning p5-term-readline
--->  Computing dependencies for p5-test-fatal
The following dependencies will be installed:  p5.30-test-fatal
Continue? [Y/n]: y
--->  Fetching archive for p5.30-test-fatal
	--->  Attempting to fetch 
p5.30-test-fatal-0.16.0_0.darwin_18.noarch.tbz2 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-test-fatal
	--->  Attempting to fetch 
p5.30-test-fatal-0.16.0_0.darwin_18.noarch.tbz2.rmd160 from 
https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.30-test-fatal

--->  Installing p5.30-test-fatal @0.16.0_0
--->  Activating p5.30-test-fatal @0.16.0_0
--->  Cleaning p5.30-test-fatal
--->  Cleaning p5-test-fatal
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

Perfectly normal, right?

However, immediately after doing that, I did a reclaim and got a 
surprise:


$ sudo port -v reclaim
--->  Checking for unnecessary unrequested ports
Unrequested ports without requested dependents found:
 p5.30-test-fatal  @0.16.0_0
 p5.30-net-cidr  @0.200.0_0
 p5.30-term-readline  @1.140.0_0
Would you like to uninstall them? [Y/n]: n

And the dependency map is not reversible:

$ port deps p5-net-cidr
Full Name: p5-net-cidr @0.200.0_0
Library Dependencies: p5.30-net-cidr
$ port rdependents p5.30-net-cidr
p5.30-net-cidr has no dependents.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Re: cdrtools streamripper

[Christopher Jones]

Please check for an open trac ticket, and if one does not exist open one.

> On 9 Jun 2021, at 9:47 am, Giuseppe Di Matteo  wrote:
> 
> I made the change in the Portfile, but it still won’t install. It seems that 
> the problem is now with the arch arm64 (Mac mini M1).
> Giuseppe Di Matteo
> pinodimat...@me.com 
> 
> 
> 
> 
> 
>> Le 8 juin 2021 à 20:48, Christopher Jones > > a écrit :
>> 
>> 
>> For the smake issue see
>> 
>> https://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1
>>  
>> 
>> 
>>> On 7 Jun 2021, at 5:15 pm, Andrew Udvare >> > wrote:
>>> 
>>> 
 On 2021-06-07, at 09:34, Giuseppe Di Matteo via macports-users 
 >>> > wrote:
 
 I can’t install cdrtools and streamripper on macOS 11 (Big Sur).
 
 Giuseppe Di Matteo
 pinodimat...@me.com 
 
 
 
 
 
 
 
>>> 
>>> I can reproduce the issue with cdrtools. `smake` does not accept -j.
>>> 
>>> I cannot reproduce the issue with streamripper. streamripper builds for me. 
>>> However, I am on x86-64.
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cdrtools streamripper

[Giuseppe Di Matteo via macports-users]

I made the change in the Portfile, but it still won’t install. It seems that the problem is now with the arch arm64 (Mac mini M1).
Giuseppe Di Matteopinodimat...@me.com



main.log
Description: Binary data

Le 8 juin 2021 à 20:48, Christopher Jones  a écrit :For the smake issue seehttps://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1On 7 Jun 2021, at 5:15 pm, Andrew Udvare  wrote:On 2021-06-07, at 09:34, Giuseppe Di Matteo via macports-users  wrote:I can’t install cdrtools and streamripper on macOS 11 (Big Sur).Giuseppe Di Matteopinodimat...@me.comI can reproduce the issue with cdrtools. `smake` does not accept -j.I cannot reproduce the issue with streamripper. streamripper builds for me. However, I am on x86-64.