Re: ncurses 6.2 failing with reinplace warnings

[Jeffrey Walton]

On Sun, Mar 15, 2020 at 7:26 PM Richard DeLaurell
 wrote:
>
> I am trying to update from ncurses 6.1 to 6.2, but am getting the warnings 
> noted in ticket #60152; however, unlike the ticket report there my 
> installation does not complete.

If you are talking about the reinplace warnings, then install
MacPort's gsed. I found the warnings went away after I installed gsed
when trying to build CMake for a PowerMac. Your mileage may vary.

Jeff

Re: installing patched okular: cannot open Portfile

[Nicolas Pavillon]

Hi, 

This is an initial guess, but I would not necessarily recommend to change the 
name of the port, as this could lead to conflicts with existing files from the 
original one. 
And if you do change it, be sure to also change the name of the port in the 
Portfile. This might be the reason why your system can’t install the port.

Cheers,

Nicolas

> On Mar 15, 2020, at 4:57, Murray Eisenberg  wrote:
> 
> In order to get okular working, I’m following the instructions in 
> https://trac.macports.org/ticket/60059#comment:8 
> .
> 
> This involves, among other things, creating a local port (okular2) in a 
> folder under my own account, namely:
> 
>   ~/macports/myports/kde/okular2
> 
> containing subdirectory files and Portfile, copied from the macports sources, 
> but with Portfile edited per those instructions.
> 
> When I finally execute…
> 
>   sudo port install okular2
> 
> .. I get error message:
> 
>   Unable to execute port: Could not open file: 
> /Users/murray/macports/myports/kde/okular2/Portfile
> 
> The permissions seem to be the same on my modified Portfile in as for the 
> distributed Portfile in 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/kde/okular
>  , except that I 
> am the owner, in group staff, of the former, whereas messagebus, with group 
> ldap, is the owner of the latter. The permissions on my modified file are:
> 
>   -rw-r--r--@
> 
> What could be wrong?
> 
> Note that before attempting the install, I _did_ execute:
> 
>   cd ~/macports/myports
>  port index
> 
> which did create file ~/macports/myports/kde/Portindex.
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

Re: macports-users Digest, Vol 163, Issue 10

[j...@tigger.ws]

> On 15 Mar 2020, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
> 
>> 
>> My old PowerMac G5 cannot build the CMake being supplied with
>> MacPorts. I know CMake now requires C+11 or C++14, and the antique
>> tools on the Mac do not meet the requirements. I want to pin CMake to
>> an older version for the Mac. For example, 3.15.4 or 3.14.6.
>> 
>> How do I pin a package using MacPorts?
> 
> MacPorts doesn't have a "pin a package" feature. We would not be able to 
> accommodate the explosion of bug reports that would arise if we allowed users 
> to construct arbitrary combinations of versions of ports from the past. 
> Instead, we focus on providing a single collection of ports that are 
> hopefully somewhat up to date and should work together.
> 
> In a collection of this size, it is inevitable that at any given point some 
> things will be broken, such as the bug you found where cmake doesn't build on 
> 10.5 right now. Those bugs should be fixed.
> 
> While we don't allow users to decide what version of a port they want, the 
> maintainer of a port can make such decisions and it can be based on 
> variables. For example, several ports already restrict themselves to an older 
> version of the software when the port is installed on older operating systems 
> if the latest version of the software no longer builds on older systems. If 
> that were necessary to resolve this issue for 10.5, the maintainer of the 
> port could choose to do that, however it's not clear at this point whether 
> that would help.

Ryan

I've just been a dumb user, so the answer may be obvious

Can I download a port build, 'maintain it' build and install on my system?

James

Re: ncurses 6.2 failing with reinplace warnings

[Chris Jones]

> On 15 Mar 2020, at 11:26 pm, Richard DeLaurell  
> wrote:
> 
> 
> Hello,
> 
> I am trying to update from ncurses 6.1 to 6.2, but am getting the warnings 
> noted in ticket #60152; however, unlike the ticket report there my 
> installation does not complete.
> 
> The failure log reports: install error CHILDSTATUS 43121 2
> 
> What could be the problem?

The ticket above is unlikely to be related to your problem. Its hard to tell 
and Without more information no one is going to be able to help. Please open a 
new ticket in trac, and be sure to attach a complete log file showing the 
failure.

Chris

> 
> Thanks for any wisdom.
> 

ncurses 6.2 failing with reinplace warnings

[Richard DeLaurell]

Hello,

I am trying to update from ncurses 6.1 to 6.2, but am getting the warnings
noted in ticket #60152 ; however,
unlike the ticket report there my installation does not complete.

The failure log reports: install error CHILDSTATUS 43121 2

What could be the problem?

Thanks for any wisdom.

Re: What does "Exit code: 11" mean when building CMake?

[Ken Cunningham]

cmake (and other software) is quite broken on 10.5 ppc with libgcc7. 

please see the cmake ticket.

rolling back to libgcc7 is presenly the only known fix. there is a pr 
referenced in the ticket where I reluctantly propose to do that if no better 
solution is found.

upstream says it's complicated to fix. they have to separate libstdc++ from the 
libstdc++abi code. Not for the squeamish. Probably few around who could do it.

btw, on macports, you cannot force a compiler like that. 

K

Re: How to pin a package?

[Jeffrey Walton]

On Sat, Mar 14, 2020 at 11:24 AM Ryan Schmidt  wrote:
>
> On Mar 14, 2020, at 00:39, Jeffrey Walton wrote:
>
> > My old PowerMac G5 cannot build the CMake being supplied with
> > MacPorts. I know CMake now requires C+11 or C++14, and the antique
> > tools on the Mac do not meet the requirements. I want to pin CMake to
> > an older version for the Mac. For example, 3.15.4 or 3.14.6.
> >
> > How do I pin a package using MacPorts?
>
> MacPorts doesn't have a "pin a package" feature. We would not be able to 
> accommodate the explosion of bug reports that would arise if we allowed users 
> to construct arbitrary combinations of versions of ports from the past. 
> Instead, we focus on providing a single collection of ports that are 
> hopefully somewhat up to date and should work together.
>
> In a collection of this size, it is inevitable that at any given point some 
> things will be broken, such as the bug you found where cmake doesn't build on 
> 10.5 right now. Those bugs should be fixed.
>
> While we don't allow users to decide what version of a port they want, the 
> maintainer of a port can make such decisions and it can be based on 
> variables. For example, several ports already restrict themselves to an older 
> version of the software when the port is installed on older operating systems 
> if the latest version of the software no longer builds on older systems. If 
> that were necessary to resolve this issue for 10.5, the maintainer of the 
> port could choose to do that, however it's not clear at this point whether 
> that would help.

Ack, thanks.

Based on Ken's advice I'll build it with GCC 5.

Jeff