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

[Jeffrey Walton]

On Sun, Mar 15, 2020 at 10:11 AM Ken Cunningham
 wrote:
> ...
> 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.

A quick question Ken... Would Musl help solve this problem? Rich
Felker is fairly aggressive at supporting platforms. He may be
interested in the port. In fact, he has managed to build something
similar for PowerPC. I believe he does it through a custom GCC
cross-compiler (https://github.com/richfelker/musl-cross-make).

Jeff

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

[Dave Horsfall]

On Mon, 16 Mar 2020, Ryan Schmidt wrote:

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


I don't think I understand your question.

You can install a port by running "sudo port install thePortName". In 
what way is what you are asking different from that?


It sounds like the OP wants to maintain a "private" port base, in much the 
same way that FreeBSD's ports system allows.


PS: I wish people would use the correct Subject: line when replying to a 
digest; "macports-users Digest, Vol 163, Issue 10" means stuff-all to me 
(and others), and I believe that there are MUAs that can reply to a digest 
in the correct manner.


-- Dave

--disable-tls does not limit functionality, it only determines how std::call_once works

[Jeffrey Walton]

Hi Everyone/Ken,

I was looking through
https://github.com/kencu/LeopardPorts/blob/master/lang/gcc7/Portfile,
and noticed this comment:

# see https://lists.macports.org/pipermail/macports-dev/2017-August/036209.html
# --disable-tls does not limit functionality
# it only determines how std::call_once works

Based on my testing of i686, x86_64, ARM-32, Aarch64 and PowerPC,
std::call_once is completely broken everywhere except x86_64. When I
tired to use std::call_once in my programs I had truckloads of
unexplained crashes everywhere except x86_64. There's GCC bug report
that details the same.

If possible, GCC should be built without std::call_once. Or
std::call_once should throw std::runtime_error("Not implemented!"). I
don't know if GCC ever fixed std::call_once on non-Intel platforms,
but you should avoid std::call_once. Treat it like the coronavirus.

Off topic, here's some interesting reading on coronavirus and its
origins in horseshoe bats in southern asia:
https://www.scientificamerican.com/article/how-chinas-bat-woman-hunted-down-viruses-from-sars-to-the-new-coronavirus1/

Jeff

Re: installing patched okular: cannot open Portfile

[Pieter van Oostrum]

Ken Cunningham  writes:

> gives error:
> 
> Unable to execute port: Could not open file: 
> /Users/murray/macports/myports/kde/okular/Portfile
> 
> Could it still be a permissions or ownership issue?
>
> It is a permissions error. Although Chris and others seem to make this work, 
> it has never worked
> for me to put a macports repo in my home folder. I don’t know why, and I gave 
> up trying to fix it.
>
> Just put it in /Users/Shared/MacPorts or, what I do, is put them all in /opt 
> (but then you have to
> be careful with sudo, which I always am).
>
Very strange. I have been using this construction for years. I have all my 
directories in my private repository with mode 755, and the files 644.
-- 
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

Re: installing patched okular: cannot open Portfile

[Ken Cunningham]

> 
> gives error:
> 
>   Unable to execute port: Could not open file: 
> /Users/murray/macports/myports/kde/okular/Portfile
> 
> Could it still be a permissions or ownership issue?
> 

It is a permissions error. Although Chris and others seem to make this work, it 
has never worked for me to put a macports repo in my home folder. I don’t know 
why, and I gave up trying to fix it.

Just put it in /Users/Shared/MacPorts or, what I do, is put them all in /opt 
(but then you have to be careful with sudo, which I always am).

Ken

Re: Clang 7.1 for PPC

[Ken Cunningham]

> Hi everyone,
> 
> I'm trying to install Clang 7.1 on a PowerMac. Clang 7.1 is important
> because it has this bug fix:
> https://bugs.llvm.org/show_bug.cgi?id=39704. 
>  The 39704 issue fixed
> unaligned loads and stores for Altivec.
> 
> Clang 7.0 - which supports PPC - provides this error:
> 
> $ sudo port install clang-7.0
> Error: clang-7.0 cannot be installed for the configured build_arch
> 'ppc' because it only supports the arch(s) 'i386 x86_64'.
> 
> Clang 7.1 results in an error:
> 
> $ sudo port install clang-7.1
> Error: Port clang-7.1 not found
> 
> Would it be possible to update the configuration files to allow Clang
> 7.0 and 7.1 for PowerPC?
> 
> Jeff


That version will not work on PowerPC, so we can’t enable it. All versions 
after that have had PowerPC support completely stripped / disabled by upstream.

There is, however, a version that almost works — it is not ABI compatible with 
any part of macOS, but it’s fun to play around with if you have nothing to do.

It’s not presently useful for anything other than playing, but it might be one 
day, with encouragement.

I have considered setting up a Portfile for it, but as it is just not ready, I 
didn’t bother.

There is also a nice version of ld64 > 250 included as well, that you can play 
with.

Do this separately from your MacPorts installation, or you will screw 
everything up really severely.

Have fun!



Ken

Re: installing patched okular: cannot open Portfile

[Murray Eisenberg]

In short: keeping the name okular for the modified port does not work, either.

In detail:

I just tried that — keeping the name okular for the modified port (both as the 
name of the directory /Users/murray/macports/myports/kde/okular and in the file 
Portfile.

Of course I had also already edited /opt/local/etc/macports/sources.conf to 
insert

file:///Users/murray/macports/myports 


before:

rsync://rsync.macports.org/release/tarballs/ports.tar [default]

Still, does not work: after running portindex in 
/Users/murray/macports/myports, command

sudo port install okular

gives error:

Unable to execute port: Could not open file: 
/Users/murray/macports/myports/kde/okular/Portfile

Could it still be a permissions or ownership issue?

(Note: That the port install command gets that far as to know the correct 
Portfile location does confirm that it’s OK to re-use the port name provided 
the indicated modification to sources.conf has been made.)

> On 16 Mar2020, at 12:29 AM, Nicolas Pavillon  wrote:
> 
> 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
>> 
>> 
> 

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

Clang 7.1 for PPC

[Jeffrey Walton]

Hi everyone,

I'm trying to install Clang 7.1 on a PowerMac. Clang 7.1 is important
because it has this bug fix:
https://bugs.llvm.org/show_bug.cgi?id=39704. The 39704 issue fixed
unaligned loads and stores for Altivec.

Clang 7.0 - which supports PPC - provides this error:

$ sudo port install clang-7.0
Error: clang-7.0 cannot be installed for the configured build_arch
'ppc' because it only supports the arch(s) 'i386 x86_64'.

Clang 7.1 results in an error:

$ sudo port install clang-7.1
Error: Port clang-7.1 not found

Would it be possible to update the configuration files to allow Clang
7.0 and 7.1 for PowerPC?

Jeff

Re: installing patched okular: cannot open Portfile

[Pieter van Oostrum]

Murray Eisenberg  writes:

> The cited instructions at trac.macports.org do change the name.
>
> And if I do _not_ change the name, then how will command “sudo port install 
> okular” know to use
> the modified port, inside my home tree, instead of the distributed one?

You can give it a higher revision number.
-- 
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

Re: installing patched okular: cannot open Portfile

[Nicolas Pavillon]

Hi,

> On Mar 16, 2020, at 23:19, Murray Eisenberg  wrote:
> 
> The cited instructions at trac.macports.org  do 
> change the name.

Indeed, and I added a note today to that ticket to mention the points I made 
below as soon as I noticed that. 

> And if I do _not_ change the name, then how will command “sudo port install 
> okular” know to use the modified port, inside my home tree, instead of the 
> distributed one?

If I am not mistaken, the order in which you define your sources in 
sources.conf determines which one supersedes the other (to have your local one 
superseding, put it before the main one). 
To be sure of which one you use, you can also increase the revision to check 
the version of the installed port. 

And again, I just don’t recommend it, but you can use the name okular2. You 
just have then to be consistent in the name used in the Portfile itself. 

Cheers, 

Nicolas

> 
>> On 16 Mar2020, at 12:29 AM, Nicolas Pavillon > > wrote:
>> 
>> 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 Eisenbergmurrayeisenb...@gmail.com 
>>> 
>>> 503 King Farm Blvd #101 Home (240)-246-7240
>>> Rockville, MD 20850-6667Mobile (413)-427-5334
>>> 
>>> 
>> 
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

Re: installing patched okular: cannot open Portfile

[Ken Cunningham]

> And if I do _not_ change the name, then how will command “sudo port install 
> okular” know to use the modified port, inside my home tree, instead of the 
> distributed one?

for a one-off like that, you can use a MacPorts feature.
If you type "sudo port install" without a name, in a port directory, it will 
always build and install the port with the default name from the portfile in 
the directory you are in.
Gets trickier when using variants, though. To do that, you need to use a 
subport syntax, like this:

sudo port -v install subport=name +myvariant -myunwantedvariant

and then it will build and install the named subport in your local folder, 
which can be the main port name, or some subport of it, with your variants.

For permanently setting your port as the replacement of the named port I cannot 
tell you, but look in recent prior messages and you will see it mentioned.

K

Re: installing patched okular: cannot open Portfile

[Murray Eisenberg]

The cited instructions at trac.macports.org do change the name.

And if I do _not_ change the name, then how will command “sudo port install 
okular” know to use the modified port, inside my home tree, instead of the 
distributed one?

> On 16 Mar2020, at 12:29 AM, Nicolas Pavillon  wrote:
> 
> 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
>> 
>> 
> 

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

Re: How to pin a package?

[Ryan Schmidt]

On Mar 15, 2020, at 09:13, Ken Cunningham wrote:

> on macports you pin a package using a personal repository.
> 
> I explained it a few answers above. It's a very simple, 30 second, procedure.

But that is not what we want users to need to do. When a user encounters a 
problem, we do not want the official answer to be "manually perform such and 
such workaround". We want the answer to be "we will fix the problem in the 
official ports collection so that all users receive the fix automatically when 
they selfupdate."

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

[Ryan Schmidt]

On Mar 15, 2020, at 18:50, j...@tigger.ws wrote:

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

I don't think I understand your question.

You can install a port by running "sudo port install thePortName". In what way 
is what you are asking different from that?