Re: 7zip port - what's the name of the binary?

[Christoph Kukulies via macports-users]

Found it:

7zz

Thanks for port content.

Saves me from running /usr/libexec/locate.updatedb everytime I'm installing a 
port :-)



> Am 23.06.2024 um 17:05 schrieb Ken Cunningham 
> :
> 
> port contents 7zip
> 
> will tell you what’s installed by a port.
> 
> pipe it to grep for a specific path like bin/
> 
>> On Jun 23, 2024, at 07:49, Christoph Kukulies via macports-users 
>>  wrote:
>> 
>> 7zip



signature.asc
Description: Message signed with OpenPGP

7zip port - what's the name of the binary?

[Christoph Kukulies via macports-users]

I can't the heck not figure out what the name of the binary is, once you did a

`sudo port install 7zip` under macOS?

$ p7zip
-bash: p7zip: command not found
$ 7zip
-bash: 7zip: command not found
$ pzip
-bash: pzip: command not found
$ p7zip
-bash: p7zip: command not found
$ 7z
-bash: 7z: command not found
$ 7zip
-bash: 7zip: command not found
$



Could anyone solve the secret?

--
Christoph



signature.asc
Description: Message signed with OpenPGP

Re: /usr/bin/mail , mailutils port

[Christoph Kukulies via macports-users]

I must add that the behaviour is infact:


$ mail
Illegal use of "message list"
No mail for kuku
$ 

> Am 09.06.2024 um 11:20 schrieb Christoph Kukulies via macports-users 
> :
> 
> It seems that the installation of the mailutils port screwed up the 
> functioning of the `mail` commandline tool for sending mails.
> I'm pretty sure that I was able to forge the From field of an email I sent 
> with the "mail" command from the command line by editing
> ~/.mailrc with the line "from m...@valid.domain.tld" (without the 
> apostrophes).
> 
> This suddenly stopped working. Uninstalling mailutils didn't bring back the 
> functionality.
> 
> --
> Christoph
> 
> 

/usr/bin/mail , mailutils port

[Christoph Kukulies via macports-users]

It seems that the installation of the mailutils port screwed up the functioning 
of the `mail` commandline tool for sending mails.
I'm pretty sure that I was able to forge the From field of an email I sent with 
the "mail" command from the command line by editing
~/.mailrc with the line "from m...@valid.domain.tld 
" (without the apostrophes).

This suddenly stopped working. Uninstalling mailutils didn't bring back the 
functionality.

--
Christoph




smime.p7s
Description: S/MIME cryptographic signature

Re: Segfault 11 of sshfs

[Christoph Kukulies via macports-users]

Answer from the maintainers:

2.10 is six years old. Please update.




> Am 14.10.2023 um 12:12 schrieb Christopher Jones :
> 
> 
> 
>> On 14 Oct 2023, at 10:39 am, Christoph Kukulies via macports-users 
>>  wrote:
>> 
>> Trying to use sshfs under BigSur and errouneously typing an imcomplete 
>> command:
>> 
>> $ sshfs foobar.de <http://foobar.de/>:/home/foo
>> Segmentation fault: 11
>> $ 
>> 
>> leads to a Segmentation fault:  11.
>> 
>> Just would like to bring this to the maintainers' attention.
> 
> Which sending a mail to this list is not going to g to necessarily do. Please 
> open a trac ticket.
> 
>> 
>> --
>> Christoph
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Segfault 11 of sshfs

[Christoph Kukulies via macports-users]

Thanks. Sorry for posting to the wrong responsibilities. Opened an issue on 
https://github.com/libfuse/sshfs/issues 
<https://github.com/libfuse/sshfs/issues>.
--
Christoph


> Am 14.10.2023 um 12:12 schrieb Christopher Jones :
> 
> 
> 
>> On 14 Oct 2023, at 10:39 am, Christoph Kukulies via macports-users 
>>  wrote:
>> 
>> Trying to use sshfs under BigSur and errouneously typing an imcomplete 
>> command:
>> 
>> $ sshfs foobar.de <http://foobar.de/>:/home/foo
>> Segmentation fault: 11
>> $ 
>> 
>> leads to a Segmentation fault:  11.
>> 
>> Just would like to bring this to the maintainers' attention.
> 
> Which sending a mail to this list is not going to g to necessarily do. Please 
> open a trac ticket.
> 
>> 
>> --
>> Christoph
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Segfault 11 of sshfs

[Christoph Kukulies via macports-users]

Trying to use sshfs under BigSur and errouneously typing an imcomplete command:

$ sshfs foobar.de:/home/foo
Segmentation fault: 11
$ 

leads to a Segmentation fault:  11.

Just would like to bring this to the maintainers' attention.

--
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Problem with binutils

[Christoph Kukulies]

Hi,

I was trying to sudo port install binutils and got this:

$ sudo port install binutils
Password:
--->  Computing dependencies for binutils
--->  Fetching archive for binutils
--->  Attempting to fetch binutils-2.39_1.darwin_20.x86_64.tbz2 from 
https://packages.macports.org/binutils
--->  Attempting to fetch binutils-2.39_1.darwin_20.x86_64.tbz2.rmd160 from 
https://packages.macports.org/binutils
--->  Installing binutils @2.39_1
--->  Activating binutils @2.39_1
Error: Failed to activate binutils: Image error: /opt/local/include/ansidecl.h 
is being used by the active gdb port.  Please deactivate this port first, or 
use 'port -f activate binutils' to force the activation.
while executing
"throw registry::image-error $msg"
("foreach" body line 47)
invoked from within
"foreach file $imagefiles {
set srcfile "${extracted_dir}${file}"

# To be able to install links, we test if we can lst..."
invoked from within
"registry::write {
foreach file $imagefiles {
set srcfile "${extracted_dir}${file}"

# To be able to instal..."
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port binutils failed
$ 

How can I get around?

--
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Re: Wine

[Christoph Kukulies]

Data  point:

$ sudo port install wine
Password:
wine is known to fail. Try to install anyway? [y/N]: y
Error: wine cannot be installed for the configured build_arch 'x86_64' because 
it only supports the arch(s) 'i386'.
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port wine failed
$ 



> Am 30.04.2023 um 10:45 schrieb Christoph Kukulies :
> 
> Does macports support Wine ?
> 
> —
> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Wine

[Christoph Kukulies]

Does macports support Wine ?

—
Christoph

Re: argp.h

[Christoph Kukulies]

OK, I found in the macOS prerequisite list for macOS that the brew package 
„argp_standalone“ is required.
I hate mixing brew and macports.

> Am 07.04.2023 um 11:02 schrieb Christoph Kukulies :
> 
> I’m about to compile a tool, named „drat“ - an APFS repair tool 
> (https://github.com/jivanpal/drat <https://github.com/jivanpal/drat>)  maybe 
> worth making a port of it - and I’m getting compilation errors since the 
> argp_parse library (seems to be a part of the gnu clib, but which one?) 
> cannot be found.
> 
> Anyone having an idea where the  is buried?
> 
> —
> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

argp.h

[Christoph Kukulies]

I’m about to compile a tool, named „drat“ - an APFS repair tool 
(https://github.com/jivanpal/drat )  maybe 
worth making a port of it - and I’m getting compilation errors since the 
argp_parse library (seems to be a part of the gnu clib, but which one?) cannot 
be found.

Anyone having an idea where the  is buried?

—
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Mixing brew and macports

[Christoph Kukulies]

I’m not sure whether I can harmlessly use brew to install a package that is not 
available under macports, to be precise, sigrok/pulseview is the target.

All available remedies refer to using brew install.

May I use brew along with macports, the latter being my tool of choice for 
maintaining external software packages for macOS?

—
Christoph

Re: Problem with gdb port

[Christoph Kukulies]

I followed the recommended steps to deactivate binutils. Finally I got 
something not being called gdb, but ggdb.

And running it tells me I gotta codesign the binary.

OK, als I got through this codesigning process but at some point I’m asked 
${which gdb}

Before I dare to run the script with this macro from which I would expect that 
it would fail anyway, I’m asking: would it be safe to renam or link ggdb to gdb?

—
Christoph



> Am 06.04.2022 um 16:31 schrieb Christoph Kukulies :
> 
> I’m gettig the following:
> 
> $ sudo port install gdb
> --->  Computing dependencies for gdb
> The following dependencies will be installed:  boehmgc
> Continue? [Y/n]: 
> --->  Fetching archive for boehmgc
> --->  Attempting to fetch boehmgc-8.0.6_0.darwin_20.x86_64.tbz2 from 
> https://packages.macports.org/boehmgc <https://packages.macports.org/boehmgc>
> --->  Attempting to fetch boehmgc-8.0.6_0.darwin_20.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/boehmgc <https://packages.macports.org/boehmgc>
> --->  Installing boehmgc @8.0.6_0
> --->  Activating boehmgc @8.0.6_0
> --->  Cleaning boehmgc
> --->  Fetching archive for gdb
> --->  Attempting to fetch gdb-11.2_0.darwin_20.x86_64.tbz2 from 
> https://packages.macports.org/gdb <https://packages.macports.org/gdb>
> --->  Attempting to fetch gdb-11.2_0.darwin_20.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/gdb <https://packages.macports.org/gdb>
> --->  Installing gdb @11.2_0
> --->  Activating gdb @11.2_0
> Error: Failed to activate gdb: Image error: /opt/local/include/ansidecl.h is 
> being used by the active binutils port.  Please deactivate this port first, 
> or use 'port -f activate gdb' to force the activation.
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gdb/gdb/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets 
> <https://guide.macports.org/#project.tickets> if you believe there is a bug.
> Error: Processing of port gdb failed
> $



smime.p7s
Description: S/MIME cryptographic signature

Problem with gdb port

[Christoph Kukulies]

I’m gettig the following:

$ sudo port install gdb
--->  Computing dependencies for gdb
The following dependencies will be installed:  boehmgc
Continue? [Y/n]: 
--->  Fetching archive for boehmgc
--->  Attempting to fetch boehmgc-8.0.6_0.darwin_20.x86_64.tbz2 from 
https://packages.macports.org/boehmgc
--->  Attempting to fetch boehmgc-8.0.6_0.darwin_20.x86_64.tbz2.rmd160 from 
https://packages.macports.org/boehmgc
--->  Installing boehmgc @8.0.6_0
--->  Activating boehmgc @8.0.6_0
--->  Cleaning boehmgc
--->  Fetching archive for gdb
--->  Attempting to fetch gdb-11.2_0.darwin_20.x86_64.tbz2 from 
https://packages.macports.org/gdb
--->  Attempting to fetch gdb-11.2_0.darwin_20.x86_64.tbz2.rmd160 from 
https://packages.macports.org/gdb
--->  Installing gdb @11.2_0
--->  Activating gdb @11.2_0
Error: Failed to activate gdb: Image error: /opt/local/include/ansidecl.h is 
being used by the active binutils port.  Please deactivate this port first, or 
use 'port -f activate gdb' to force the activation.
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gdb/gdb/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port gdb failed
$

smime.p7s
Description: S/MIME cryptographic signature

Re: libusb-devel port

[Christoph Kukulies]

Thanks. Assumed I have downloaded a binary release from libusb’s github 
Releases and it looks like that in the tree:

$ find macos_11.6
macos_11.6
macos_11.6/.DS_Store
macos_11.6/bin
macos_11.6/bin/dpfp
macos_11.6/bin/listdevs
macos_11.6/bin/sam3u_benchmark
macos_11.6/bin/fxload
macos_11.6/bin/xusb
macos_11.6/bin/testlibusb
macos_11.6/bin/hotplugtest
macos_11.6/bin/stress
macos_11.6/include
macos_11.6/include/.DS_Store
macos_11.6/include/libusb-1.0
macos_11.6/include/libusb-1.0/libusb.h
macos_11.6/lib
macos_11.6/lib/pkgconfig
macos_11.6/lib/pkgconfig/libusb-1.0.pc
macos_11.6/lib/libusb-1.0.dylib
macos_11.6/lib/libusb-1.0.0.dylib
macos_11.6/lib/libusb-1.0.a
macos_11.6/lib/libusb-1.0.la

How can I make these active in libusb-devel or otherwise available?

Do the pkgconfig .pc files play a role in the installation mechanism?

—
Christoph

> Am 05.04.2022 um 15:36 schrieb Chris Jones :
> 
> 
> On 05/04/2022 1:54 pm, Christoph Kukulies wrote:
>> Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
>> 1.0.26-rc1 „HEAD“
> 
> you cannot. You still get whatever version libusb-devel is current set to 
> provide. The idea of a X-devel port though is these can be updated and tested 
> without affecting the default X port.
> 
> If you want a different version than libusb-devel currently provides, then 
> you need to update the port to provide this.
> 
>> Btw, what is the correspondent to
>> ldd
>> under macOS?
> 
> otool -L
> 
>> —
>> Christoph
>>> Am 05.04.2022 um 12:56 schrieb Chris Jones :
>>> 
>>> 
>>> 
>>>> On 05/04/2022 11:50 am, Christoph Kukulies wrote:
>>>> $ sudo port deactivate libusb @1.0.25_0
>>>> Password:
>>>> Note: It is not recommended to uninstall/deactivate a port that has 
>>>> dependents as it breaks the dependents.
>>>> The following ports will break:
>>>>  libusb-compat @0.1.7_0
>>>>  openocd @0.11.0_0
>>>>  usbutils @007_1
>>>>  libftdi1 @1.5_1
>>>>  qemu @6.2.0_0
>>>>  stlink @1.7.0_1
>>>> Continue? [y/N]:
>>>> 
>>>> OK to continue?
>>> 
>>> yes.
>>> 
>>> ports that depend on libusb should use a path style dependency, to allow 
>>> libusb or libusb-devel to satisfy it
>>> 
>>> path:lib/pkgconfig/libusb-1.0.pc:libusb
>>> 
>>> so assuming you are about to install libusb-devel its fine.



smime.p7s
Description: S/MIME cryptographic signature

Re: libusb-devel port

[Christoph Kukulies]

Thanks. Nonetheless I don‘t get how I can aim at a specific version or 
1.0.26-rc1 „HEAD“

Btw, what is the correspondent to

ldd

under macOS?

—
Christoph 

> Am 05.04.2022 um 12:56 schrieb Chris Jones :
> 
> 
> 
>> On 05/04/2022 11:50 am, Christoph Kukulies wrote:
>> $ sudo port deactivate libusb @1.0.25_0
>> Password:
>> Note: It is not recommended to uninstall/deactivate a port that has 
>> dependents as it breaks the dependents.
>> The following ports will break:
>>  libusb-compat @0.1.7_0
>>  openocd @0.11.0_0
>>  usbutils @007_1
>>  libftdi1 @1.5_1
>>  qemu @6.2.0_0
>>  stlink @1.7.0_1
>> Continue? [y/N]:
> >
> > OK to continue?
> 
> yes.
> 
> ports that depend on libusb should use a path style dependency, to allow 
> libusb or libusb-devel to satisfy it
> 
> path:lib/pkgconfig/libusb-1.0.pc:libusb
> 
> so assuming you are about to install libusb-devel its fine.

Re: libusb-devel port

[Christoph Kukulies]

$ sudo port deactivate libusb @1.0.25_0
Password:
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break:
 libusb-compat @0.1.7_0
 openocd @0.11.0_0
 usbutils @007_1
 libftdi1 @1.5_1
 qemu @6.2.0_0
 stlink @1.7.0_1
Continue? [y/N]: 





OK to continue?

—
Christoph 


> Am 05.04.2022 um 12:40 schrieb Chris Jones :
> 
> 
> 
> On 05/04/2022 11:33 am, Christoph Kukulies wrote:
>> I’m in the need of testing a libusb issue with an intermediate build of 
>> libusb (1.0.26-rc1, that is)
>> Since I’m always reluctant of mixing brew and macports - is that actually 
>> „dangerous“ or impossible at all, should that be avoided or can it be done -
>> One of the developers of libusb told me that the libusb-devel port is 
>> broken. I’d prefer using macports. Trying it, I got:
>> $ sudo port install libusb-devel
>> Password:
>> Error: Can't install libusb-devel because conflicting ports are active: 
>> libusb
>> Error: Follow https://guide.macports.org/#project.tickets 
>> <https://guide.macports.org/#project.tickets> if you believe there is a bug.
>> Error: Processing of port libusb-devel failed
>> $
>> Any advice?
> 
> you need to deacivate libusb first
> 



smime.p7s
Description: S/MIME cryptographic signature

libusb-devel port

[Christoph Kukulies]

I’m in the need of testing a libusb issue with an intermediate build of libusb 
(1.0.26-rc1, that is)

Since I’m always reluctant of mixing brew and macports - is that actually 
„dangerous“ or impossible at all, should that be avoided or can it be done -

One of the developers of libusb told me that the libusb-devel port is broken. 
I’d prefer using macports. Trying it, I got:

$ sudo port install libusb-devel
Password:

Error: Can't install libusb-devel because conflicting ports are active: libusb
Error: Follow https://guide.macports.org/#project.tickets if you believe there 
is a bug.
Error: Processing of port libusb-devel failed
$ 

Any advice?

—
Christoph




smime.p7s
Description: S/MIME cryptographic signature

Falling back on a certain version of a port

[Christoph Kukulies]

I’m in the course of installing

sudo port install stlink

The question came to me whether it’s possible to install a specific version of 
the software?

—
Christoph




smime.p7s
Description: S/MIME cryptographic signature

Aspell port

[Christoph Kukulies]

macOS 11.5.2

I tried to install the aspell port  aspell @0.60.8_1 (textproc) plus appropiate 
language packs.

The port installs but I don’t see any traces of aspell in applications like 
Mail.app.

Any clues? I also experimented using brew and cocoAspell. For a while I saw 
German (Aspell) or Deutsch (Aspell) in
but they seem to have disappeared by some action I did, but cannot reconstruct, 
what action it was. Maybe removing cocoAspell (?).

Any help appreciated. TIA.

Christoph

smime.p7s
Description: S/MIME cryptographic signature

Re: Telnet not in netutils

[Christoph Kukulies]

No, of course I didn’t read the port notes since I don’t know where one can 
find them after having done a 
port install.
Why did they do that (prefixing the utils with a „g“). Is it now a GNU thing?

Yes, I know that it is insecure and what not, but for local connections like 
talking to a port of a local process it’s just fine :)

And I also recalled how to quit the telnet session (on the Mac keyboard): 
CTRL-ALT-]
(^]) :)



> Am 27.05.2021 um 22:04 schrieb Christopher Jones :
> 
> Hi,
> 
> I guess you didn’t read/notice the port notes when you installed inetutils ?
> 
>  inetutils has the following notes:
>All clients are now installed with the "g" prefix.
> 
> Oberon ~/Projects/MacPorts/ports > sudo port contents inetutils | grep telnet
>  /opt/local/bin/gtelnet
>  /opt/local/share/man/man1/gtelnet.1.gz
> 
> Chris
> ]
>> On 27 May 2021, at 8:57 pm, Christoph Kukulies  wrote:
>> 
>> I’m trying to get a telnet installed under macOS 11.3.1. Didn’t have it 
>> installed before and some reading says it ought to be in netutils,
>> but it ain’t.
>> 
>> Any clues?
>> 
>> —
>> Christoph
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Telnet not in netutils

[Christoph Kukulies]

I’m trying to get a telnet installed under macOS 11.3.1. Didn’t have it 
installed before and some reading says it ought to be in netutils,
but it ain’t.

Any clues?

—
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Re: Getting python3.8 with macports

[Christoph Kukulies]

Ah, I wasn’t aware of writing python38
all in one without any interpunctuation.
—
Christoph



> Am 16.04.2021 um 17:10 schrieb Christopher Jones :
> 
> Just like how you would install any other port...
> 
>> sudo port install python38
> 
> gives the latest python 3.8
> 
> or
> 
>> sudo port install python39
> 
> for the latest in the 3.9 series.
> 
>> On 16 Apr 2021, at 3:47 pm, Christoph Kukulies  wrote:
>> 
>> How can I upgrade to the latest version of python (python 3.8.x)?
>> Or should I use conda or something else?
>> 
>> —
>> Christoph
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Getting python3.8 with macports

[Christoph Kukulies]

How can I upgrade to the latest version of python (python 3.8.x)?
Or should I use conda or something else?

—
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Messed with a binary in /usr/local/bin

[Christoph Kukulies]

I messed up my macports structure a bit. 
While I was in need of a newer tidy (tidy-html5) I deleted /usr7local/bin/tidy 
(which is the macports binary if I’m correct).
How can I „repair“ this situation using some macports command, maybe something 
like —force?


Christoph Kukulies






smime.p7s
Description: S/MIME cryptographic signature

Re: read() on dir

[Christoph Kukulies]

Argh! I was wrong.

$ cat /tmp
cat: /tmp: Is a directory


Sorry for the noise.


> Am 17.03.2021 um 16:19 schrieb Christoph Kukulies :
> 
> There was some discussion in the FreeBSD mailing list about changing the 
> behaviour of a directory fd WRT
> the read() function. A change has been made towards disallowing this from 
> FreeBSD 12.2 onwards (IIRC) and there was big discussion on this since it
> „violates“ the cleanness of UNIX, that a file is a file is a file or 
> „everything is a file“. Many purists were against the disallowing behaviour.
> 
> At that time I cross checked whether this is allowed in macOS and - again 
> IIRC - at that time (Catalina) it was disallowed either to do
> a „vi .“:
> 
> $ vi /tmp
> 
> " 
> " Netrw Directory Listing(netrw v168)
> "   /tmp
> "   Sorted by  name
> "   Sort sequence: 
> [\/]$,\,\.h$,\.c$,\.cpp$,\~\=\*$,*,\.o$,\.obj$,\.info$,\.swp$,\.bak$,\~$
> "   Quick Help: :help  -:go up dir  D:delete  R:rename  s:sort-by  
> x:special
> " 
> ==
> ../   
>  
> ./
> .vbox-kuku-ipc/
> com.apple.launchd.AUnEPqi6tC/
> com.apple.launchd.atGF3BeR4X/
> com.apple.launchd.lOdpt02m8q/
> powerlog/
> FirstBootAfterUpdate
> FirstBootCleanupHandled
> OSL_PIPE_501_SingleOfficeIPC_57c1e9acbaf815f47e314f3cbee8d6=
> fseventsd-uuid
> 
> Now I’m surprised that this is possible (again?) under BigSur. I may be 
> totally wrong on this. I don’t have the
> opportunity to cross check that against Catalina. Could someone confirm or 
> proove the opposite?
> 
> —
> Christoph 
> a UNIX dinosaur
> 
> 
> 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

read() on dir

[Christoph Kukulies]

There was some discussion in the FreeBSD mailing list about changing the 
behaviour of a directory fd WRT
the read() function. A change has been made towards disallowing this from 
FreeBSD 12.2 onwards (IIRC) and there was big discussion on this since it
„violates“ the cleanness of UNIX, that a file is a file is a file or 
„everything is a file“. Many purists were against the disallowing behaviour.

At that time I cross checked whether this is allowed in macOS and - again IIRC 
- at that time (Catalina) it was disallowed either to do
a „vi .“:

$ vi /tmp

" 
" Netrw Directory Listing(netrw v168)
"   /tmp
"   Sorted by  name
"   Sort sequence: 
[\/]$,\,\.h$,\.c$,\.cpp$,\~\=\*$,*,\.o$,\.obj$,\.info$,\.swp$,\.bak$,\~$
"   Quick Help: :help  -:go up dir  D:delete  R:rename  s:sort-by  x:special
" ==
../ 
   
./
.vbox-kuku-ipc/
com.apple.launchd.AUnEPqi6tC/
com.apple.launchd.atGF3BeR4X/
com.apple.launchd.lOdpt02m8q/
powerlog/
FirstBootAfterUpdate
FirstBootCleanupHandled
OSL_PIPE_501_SingleOfficeIPC_57c1e9acbaf815f47e314f3cbee8d6=
fseventsd-uuid

Now I’m surprised that this is possible (again?) under BigSur. I may be totally 
wrong on this. I don’t have the
opportunity to cross check that against Catalina. Could someone confirm or 
proove the opposite?

—
Christoph 
a UNIX dinosaur







smime.p7s
Description: S/MIME cryptographic signature

Re: OS Platform mismatch - while installing stm32flash

[Christoph Kukulies]

You (Chris) may be right on this point. I might have overseen to do a migration 
when I went from Catalina to BigSur. 

Thanks anyway for commenting.

—
Christoph




> Am 11.03.2021 um 19:19 schrieb Chris Jones :
> 
> Hi,
> 
>> On 11 Mar 2021, at 6:16 pm, James Secan  wrote:
>> 
>> Not sure I understand this.  Do we now need to “migrate” when we update 
>> from x.x.y to x.x.y+1?  Has Apple fouled things up that badly?  I thought 
>> migration was only needed in a major OS upgrade, which I would consider to 
>> be from macOS x to maxOS x+1.
> 
> You are correct, for a minor update it is not required.
> 
> The issue is the OP must not have followed the migration instructions 
> correctly when updating from Darwin19 to Darwin20 (macOS 10.15 to 11.0), as I 
> don’t see any other way he could have got those errors messages.
> 
> Chris
> 
>> 
>> Jim
>> 3222 NE 89th St
>> Seattle, WA 98115
>> (206) 430-0109
>> 
>>> On Mar 11, 2021, at 6:44 AM, Chris Jones  wrote:
>>> 
>>> Hi,
>>> 
>>> Looks like at some point you did not follow the migration instructions 
>>> correctly. You should do so now.
>>> 
>>> Chris
>>> 
>>>>> On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies  
>>>>> wrote:
>>>> 
>>>> Of course the error (OS platform mismatch) occurs on every command I'm
>>>> running on port,
>>>> 
>>>> like
>>>> 
>>>> port info
>>>> 
>>>>> Am 11.03.2021 um 14:20 schrieb Christoph Kukulies:
>>>>> Tried to do
>>>>> 
>>>>> 
>>>>> $ sudo port install stm32flash
>>>>> Password:
>>>>> Error: Current platform "darwin 20" does not match expected platform 
>>>>> "darwin 19"
>>>>> Error: If you upgraded your OS, please follow the migration instructions: 
>>>>> https://trac.macports.org/wiki/Migration
>>>>> OS platform mismatch
>>>>> while executing
>>>>> "mportinit ui_options global_options global_variations"
>>>>> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
>>>>> mismatch
>>>>> 
>>>>> 
>>>>> Did an os update from macOS 12.2.2 to 12.2.3 right before.
>>>>> 
>>>>> 
>>>>> —
>>>>> Christoph
>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: OS Platform mismatch - while installing stm32flash

[Christoph Kukulies]

Seemed like brute force reinstalling from the installer solved the OS mismatch. 
I can
do

port list

and 

port install stm32flash


All seems to be back again.

—
Christoph


> Am 11.03.2021 um 18:58 schrieb Christoph Kukulies :
> 
> It looks like I cannot do any command on macports. That way it is not even 
> possible to uninstall macports from the uninstall instructions,
> not to mention making a list of currently  installed ports.
> 
> I’m locked up. 
> 
> —
> Christoph
> 
> 
> 
>> Am 11.03.2021 um 15:44 schrieb Chris Jones :
>> 
>> Hi,
>> 
>> Looks like at some point you did not follow the migration instructions 
>> correctly. You should do so now.
>> 
>> Chris
>> 
>>> On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies  
>>> wrote:
>>> 
>>> Of course the error (OS platform mismatch) occurs on every command I'm
>>> running on port,
>>> 
>>> like
>>> 
>>> port info
>>> 
>>>> Am 11.03.2021 um 14:20 schrieb Christoph Kukulies:
>>>> Tried to do
>>>> 
>>>> 
>>>> $ sudo port install stm32flash
>>>> Password:
>>>> Error: Current platform "darwin 20" does not match expected platform 
>>>> "darwin 19"
>>>> Error: If you upgraded your OS, please follow the migration instructions: 
>>>> https://trac.macports.org/wiki/Migration
>>>> OS platform mismatch
>>>>  while executing
>>>> "mportinit ui_options global_options global_variations"
>>>> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
>>>> mismatch
>>>> 
>>>> 
>>>> Did an os update from macOS 12.2.2 to 12.2.3 right before.
>>>> 
>>>> 
>>>> —
>>>> Christoph
>>>> 
>>>> 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: OS Platform mismatch - while installing stm32flash

[Christoph Kukulies]

It looks like I cannot do any command on macports. That way it is not even 
possible to uninstall macports from the uninstall instructions,
not to mention making a list of currently  installed ports.

I’m locked up. 

—
Christoph



> Am 11.03.2021 um 15:44 schrieb Chris Jones :
> 
> Hi,
> 
> Looks like at some point you did not follow the migration instructions 
> correctly. You should do so now.
> 
> Chris
> 
>> On 11 Mar 2021, at 2:41 pm, Christoph P.U. Kukulies  
>> wrote:
>> 
>> Of course the error (OS platform mismatch) occurs on every command I'm
>> running on port,
>> 
>> like
>> 
>> port info
>> 
>>> Am 11.03.2021 um 14:20 schrieb Christoph Kukulies:
>>> Tried to do
>>> 
>>> 
>>> $ sudo port install stm32flash
>>> Password:
>>> Error: Current platform "darwin 20" does not match expected platform 
>>> "darwin 19"
>>> Error: If you upgraded your OS, please follow the migration instructions: 
>>> https://trac.macports.org/wiki/Migration
>>> OS platform mismatch
>>>   while executing
>>> "mportinit ui_options global_options global_variations"
>>> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
>>> mismatch
>>> 
>>> 
>>> Did an os update from macOS 12.2.2 to 12.2.3 right before.
>>> 
>>> 
>>> —
>>> Christoph
>>> 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

OS Platform mismatch - while installing stm32flash

[Christoph Kukulies]

Tried to do


$ sudo port install stm32flash
Password:
Error: Current platform "darwin 20" does not match expected platform "darwin 19"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch


Did an os update from macOS 12.2.2 to 12.2.3 right before.


—
Christoph




smime.p7s
Description: S/MIME cryptographic signature

Re: macOS symbol/conditional for Makefiles (porting)

[Christoph Kukulies]

Thanks. shell UNAME is a nice trick.

$ uname 
Darwin
Christoph Kukulies




> Am 28.12.2020 um 21:28 schrieb Ken Cunningham 
> :
> 
> > Does macOS supply any built-in variable for building that if block?
> 
> 
> See <https://stackoverflow.com/questions/714100/os-detecting-makefile 
> <https://stackoverflow.com/questions/714100/os-detecting-makefile>> and 
> similar examples for ways of detecting and branching on the OS in Makefiles.
> 
> Ken
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

macOS symbol/conditional for Makefiles (porting)

[Christoph Kukulies]

I’m trying to compile a package „blackmagic“ (a microcontroller gdb debugging 
and flashing program addendum to gdb).

It has some issues like missing packages (libftdi1 - I was able to add that via 
macports)

Now I want to add some condional in the Makefile like this:

ifdef macOS

CFLAGS += -I/opt/local/include

endif

Only, macOS isn’t just the variable that works. Does macOS supply any built-in 
variable for building that if block?

Christoph





smime.p7s
Description: S/MIME cryptographic signature

What is pkg-config WRT macports

[Christoph Kukulies]

I’m stumbling accross some build errors in a package named „blackmagic“:

$ git clone https://github.com/blacksphere/blackmagic.git
Cloning into 'blackmagic'...
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 9237 (delta 0), reused 0 (delta 0), pack-reused 9232
Receiving objects: 100% (9237/9237), 3.15 MiB | 1.36 MiB/s, done.
Resolving deltas: 100% (6867/6867), done.
$ cd blackmagic/
$ make PROBE_HOST=hosted
 GIT include/version.h
Package libftdi1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libftdi1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libftdi1' found
Package hidapi-libusb was not found in the pkg-config search path.
Perhaps you should add the directory containing `hidapi-libusb.pc'
to the PKG_CONFIG_PATH environment variable
No package 'hidapi-libusb' found

Now I’m wondering: is that pkg-config a part of macports or in other words, can 
macports help in supplying the issing packages?

Merry Christmas, Happy Seasons,

Christoph



smime.p7s
Description: S/MIME cryptographic signature

ARM gdb compilation fails with implicit function declaration error ioctl

[Christoph Kukulies]

Excuses if is not actually a macports issue but I’m a bit lost.

I’m about to build this:
https://gitlab.com/LinkiTools/binutils-gdb 
<https://gitlab.com/LinkiTools/binutils-gdb>


/Users/kuku/Downloads/binutils-gdb-users-ARM-embedded-gdb-master-2018q4/




Running ./configure and make in this directory ends with an error:

config.status: executing default commands
rm -f readline.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 readline.c
rm -f vi_mode.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 vi_mode.c
rm -f funmap.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 funmap.c
rm -f keymaps.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 keymaps.c
rm -f parens.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 parens.c
rm -f search.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 search.c
rm -f rltty.o
gcc -c -DHAVE_CONFIG_H-I. -I. -DRL_LIBRARY_VERSION='"6.2"' -g -O2 rltty.c
rltty.c:83:7: error: implicit declaration of function 'ioctl' is invalid in C99 
[-Werror,-Wimplicit-function-declaration]
  if (ioctl (tty, TIOCGWINSZ, &w) == 0)
  ^
rltty.c:720:3: error: implicit declaration of function 'ioctl' is invalid in 
C99 [-Werror,-Wimplicit-function-declaration]
  ioctl (fildes, TIOCSTART, 0);
  ^
rltty.c:759:3: error: implicit declaration of function 'ioctl' is invalid in 
C99 [-Werror,-Wimplicit-function-declaration]
  ioctl (fildes, TIOCSTOP, 0);
  ^
3 errors generated.
make[2]: *** [rltty.o] Error 1
make[1]: *** [all-readline] Error 2
make: *** [all] Error 2



Is there a way to either pass gcc an appropriate -W switch to overcome this 
error or „repair“ the readline source accordingly?


$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.0 (clang-1200.0.32.28)
Target: x86_64-apple-darwin19.6.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

OS is macOS Catalina 10.15.7

Help greatly appreciated.

(reason why not using a binary package is that I want to apply a patch to 
arm-none-eabi-gdb.

Thanks

Christoph Kukulies





smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick port outdated

[Christoph Kukulies]

I had deinstalled ImageMagick during my attempts to get heic working and 
installing the tar ball from the ImageMagick site.
Thus no /opt/was there.

Now I reinstalled the port:

$ port info ImageMagick
ImageMagick @6.9.11-29 (graphics, devel)
...

./lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la <http://heic.la/>

just typing


$ convert Appearance.heic Appearance.png

worked !



> Am 25.09.2020 um 22:44 schrieb Dave Allured - NOAA Affiliate via 
> macports-users :
> 
> Short answer, that is being considered, and it will take some work.  Details 
> in the ticket showed below by Ruben:
> https://trac.macports.org/ticket/51310 
> <https://trac.macports.org/ticket/51310>
> 
> 
> On Fri, Sep 25, 2020 at 2:10 PM Fred Weinhaus  <mailto:f...@alink.net>> wrote:
> Why not just offer both ImageMagick 6 and Imagemagick 7. The user could then 
> choose which he wants to use.
> 
> Fred
> 
> 
>> On Sep 25, 2020, at 1:02 PM, Sean DALY > <mailto:sdaly...@gmail.com>> wrote:
>> 
>> Dave - that is my understanding, but I haven’t tested it. I have a ton of 
>> scripts and code snippets which would break with IMv7 and my Macs also run 
>> older OSes so I am not in a rush to move to IMv7. I use sips often in 
>> conjuction with imagemagick, the sips color profile and metadata handling is 
>> excellent
>> 
>> Sean
>> 
>> 
>> On Friday, September 25, 2020, Dave Allured - NOAA Affiliate via 
>> macports-users > <mailto:macports-users@lists.macports.org>> wrote:
>> Sean,
>> 
>> "possible to invoke the previous parser" -- Do you mean that some of the 
>> IMv6 commands can be used with IMv7, simply by prefixing with "magick" and a 
>> space?  I wonder how many of the many ports depending on IMv6 could be 
>> satisfied with this simple patch.
>> 
>> 
>> On Fri, Sep 25, 2020 at 12:32 PM Sean DALY > <mailto:sdaly...@gmail.com>> wrote:
>> Hi Christoph,
>> 
>> I use imagemagick every day and IMv7 introduces a number of changes, in 
>> particular the "magick" command which replaces the previous "identify", 
>> "convert", "montage", "composite" etc. commands. The CLI parser has been 
>> rewritten and following the previous CLI parameters order will not work. It 
>> is however possible to invoke the previous parser using "magick convert" or 
>> "magick composite" for example.
>> 
>> As an alternative, if you are on a Mac running OSX v10.13 or later, for HEIF 
>> files use the OSX sips (Scriptable Image Processing System) tool, e.g.:
>> 
>> # inspect file properties
>> $ sips --getProperty allheic_image.heic
>> 
>> # convert to JPEG
>> $ sips --setProperty format jpeg heic_image.heic --setProperty formatOptions 
>> high --out heic_image.jpg
>> 
>> sips is a good companion to imagemagick's convert for raster formats, it is 
>> fast and offers a number of features.
>> 
>> As IM have stated they will support IMv6 for another ten years, it's 
>> probably best to not rush to IMv7 considering the number of changes
>> 
>> Sean
>> 
>> 
>> On Fri, Sep 25, 2020 at 11:59 AM Ruben Di Battista 
>> mailto:rubendibatti...@gmail.com>> wrote:
>> Moreover, HEIC format seems to be included here:
>> https://github.com/macports/macports-ports/pull/6021 
>> <https://github.com/macports/macports-ports/pull/6021>
>> 
>> Are there any problems?
>> 
>> On Fri, Sep 25, 2020 at 5:58 PM Ruben Di Battista
>> mailto:rubendibatti...@gmail.com>> wrote:
>> >
>> > Hello Christoph,
>> >
>> > here's there's a discussion about version 7:
>> > https://github.com/macports/macports-ports/pull/5014 
>> > <https://github.com/macports/macports-ports/pull/5014> and here
>> > https://trac.macports.org/ticket/51310 
>> > <https://trac.macports.org/ticket/51310>. It probably will be provided
>> > as a separate port.
>> >
>> > On Fri, Sep 25, 2020 at 5:40 PM Christoph Kukulies > > <mailto:k...@kukulies.org>> wrote:
>> > >
>> > > I was seeking for a means to convert Apples new HEIC/HEIF format to more 
>> > > traditional formats and I always remembered  ImageMagick being a good 
>> > > choice for that.
>> > > Unfortunately the macports version is quite outdated.
>> > > 6.9.11-29
>> > >
>> > > vs. 7.0.10-30 being the latest.
>> > >
>> > > How can I get a newer version via macports?
>> > >
>> > > —
>> > > Christoph



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick port outdated

[Christoph Kukulies]

Oh, I’m so sorry. Indeed, ImageMagick wan’t installed at all (at this time). 
Maybe I removed it 
at some point in time, when I installed the tar ball directly. 

At the moment I’m reinstalling ImageMagick from ports.

—
Christoph


> Am 28.09.2020 um 23:13 schrieb Eric F :
> 
> 
> On 9/28/20 14:58 , Christoph Kukulies wrote:
>> locate doing wildcards or not, * matches somthing and . also, anyway:
>> 
>> $ locate heic.la <http://heic.la/>
>> $
>> 
>> There is no 
>> 
>> $ ls  /opt/local/lib/ImageMagick-6.9.11
>> ls: /opt/local/lib/ImageMagick-6.9.11: No such file or directory
>> $ 
>> 
>> —
>> Christoph
> 
> Try using `port content'. If the progam is installed, it'll show you where 
> the files are located (incase you have another prefix):
> $ grep heic <(port content ImageMagick)
>   /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la
>   /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.so
> // If the program isn't installed, `port content' will tell you that.
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick port outdated

[Christoph Kukulies]

locate doing wildcards or not, * matches somthing and . also, anyway:

$ locate heic.la <http://heic.la/>
$

There is no 

$ ls  /opt/local/lib/ImageMagick-6.9.11
ls: /opt/local/lib/ImageMagick-6.9.11: No such file or directory
$ 

—
Christoph

> Am 28.09.2020 um 10:28 schrieb Richard L. Hamilton :
> 
> locate doesn't do wildcards.
> 
> $ locate -i hei | fgrep .la
> /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la <http://heic.la/>
> 
> 
>> On Sep 28, 2020, at 04:15, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> FWIW, with me here, macOS 10.15.6:
>> 
>> $ port list ImageMagick
>> ImageMagick@6.9.11-29  graphics/ImageMagick
>> 
>> 
>> $ sudo /usr/libexec/locate.updatedb
>> $ locate *.la | grep hei
>> $ 
>> 
>> Nothing related to heif, heic.
>> 
>> —
>> Christoph
>> 
>>> Am 28.09.2020 um 07:39 schrieb Ryan Schmidt >> <mailto:ryandes...@macports.org>>:
>>> 
>>> 
>>> 
>>> On Sep 27, 2020, at 18:20, Uli Wienands wrote:
>>> 
>>>> Being curious, and just having received my first .HEIC image ever (form a 
>>>> guy with an iPhone), I upgraded ImageMagic to the present version (worked) 
>>>> and then tried it: It failed. Here are the call & the error message:
>>>> 
>>>> macbook-pro:Pictures uli$ convert IMG_3160.HEIC img_3160.png
>>>> convert: unable to load module 
>>>> `/opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la 
>>>> <http://heic.la/>': file not found @ error/module.c/OpenModule/1315.
>>>> convert: no decode delegate for this image format `HEIC' @ 
>>>> error/constitute.c/ReadImage/566.
>>>> convert: no images defined `img_3160.png' @ 
>>>> error/convert.c/ConvertImageCommand/3226.
>>>> 
>>>> The weird thing is that 
>>>> /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la 
>>>> <http://heic.la/> actually exists, and so are the four related libraries 
>>>> in /opt/local/bin: /opt/local/lib/libheif.1.dylib /opt/local/lib/libheif.a 
>>>>/opt/local/lib/libheif.dylib /opt/local/lib/libheif.la 
>>>> <http://libheif.la/>
>>>> 
>>>> So, what could be amiss?
>>> 
>>> Not sure! I tried converting some heic images now and it worked fine for me 
>>> on macOS 10.13.6.
>>> 
>>> What's the contents of 
>>> /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la 
>>> <http://heic.la/>?
>>> 
>>> Does /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.so also 
>>> exist? What's the output of:
>>> 
>>> otool -L /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.so
>>> 
>>> 
>>> What OS version are you on? You mentioned /opt/local/lib/libheif.la 
>>> <http://libheif.la/> exists. The default behavior for MacPorts is to delete 
>>> .la files* on OS X 10.9 and later. If you are on 10.8 or earlier, maybe 
>>> there is a problem specific to older OS versions that we need to 
>>> investigate. The only reason why you should have /opt/local/lib/libheif.la 
>>> <http://libheif.la/> if you're on 10.9 or later is if you edited 
>>> macports.conf and set "delete_la_files no".
>>> 
>>> 
>>> *ImageMagick is an exception. It needs the .la files of its modules for 
>>> proper operation so they will not be deleted for that port on any OS 
>>> version.
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick port outdated

[Christoph Kukulies]

FWIW, with me here, macOS 10.15.6:

$ port list ImageMagick
ImageMagick@6.9.11-29  graphics/ImageMagick


$ sudo /usr/libexec/locate.updatedb
$ locate *.la | grep hei
$ 

Nothing related to heif, heic.

—
Christoph

> Am 28.09.2020 um 07:39 schrieb Ryan Schmidt :
> 
> 
> 
> On Sep 27, 2020, at 18:20, Uli Wienands wrote:
> 
>> Being curious, and just having received my first .HEIC image ever (form a 
>> guy with an iPhone), I upgraded ImageMagic to the present version (worked) 
>> and then tried it: It failed. Here are the call & the error message:
>> 
>> macbook-pro:Pictures uli$ convert IMG_3160.HEIC img_3160.png
>> convert: unable to load module 
>> `/opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la': file not 
>> found @ error/module.c/OpenModule/1315.
>> convert: no decode delegate for this image format `HEIC' @ 
>> error/constitute.c/ReadImage/566.
>> convert: no images defined `img_3160.png' @ 
>> error/convert.c/ConvertImageCommand/3226.
>> 
>> The weird thing is that 
>> /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la actually 
>> exists, and so are the four related libraries in /opt/local/bin: 
>> /opt/local/lib/libheif.1.dylib /opt/local/lib/libheif.a
>> /opt/local/lib/libheif.dylib /opt/local/lib/libheif.la
>> 
>> So, what could be amiss?
> 
> Not sure! I tried converting some heic images now and it worked fine for me 
> on macOS 10.13.6.
> 
> What's the contents of 
> /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.la 
> ?
> 
> Does /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.so also exist? 
> What's the output of:
> 
> otool -L /opt/local/lib/ImageMagick-6.9.11/modules-Q16/coders/heic.so
> 
> 
> What OS version are you on? You mentioned /opt/local/lib/libheif.la 
>  exists. The default behavior for MacPorts is to delete 
> .la files* on OS X 10.9 and later. If you are on 10.8 or earlier, maybe there 
> is a problem specific to older OS versions that we need to investigate. The 
> only reason why you should have /opt/local/lib/libheif.la 
>  if you're on 10.9 or later is if you edited 
> macports.conf and set "delete_la_files no".
> 
> 
> *ImageMagick is an exception. It needs the .la files of its modules for 
> proper operation so they will not be deleted for that port on any OS version.



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick port outdated

[Christoph Kukulies]

Hi Sean, Ruben,

thanks. I’m using macOS Catalina 10.15.6.

I’m wondering though how I would achieve getting the libheic delegate into the 
current IM 6 in macports.
Also I don’t want to use jpeg since the target is png. heic->png


—
Christoph

> Am 25.09.2020 um 20:31 schrieb Sean DALY :
> 
> Hi Christoph,
> 
> I use imagemagick every day and IMv7 introduces a number of changes, in 
> particular the "magick" command which replaces the previous "identify", 
> "convert", "montage", "composite" etc. commands. The CLI parser has been 
> rewritten and following the previous CLI parameters order will not work. It 
> is however possible to invoke the previous parser using "magick convert" or 
> "magick composite" for example.
> 
> As an alternative, if you are on a Mac running OSX v10.13 or later, for HEIF 
> files use the OSX sips (Scriptable Image Processing System) tool, e.g.:
> 
> # inspect file properties
> $ sips --getProperty allheic_image.heic
> 
> # convert to JPEG
> $ sips --setProperty format jpeg heic_image.heic --setProperty formatOptions 
> high --out heic_image.jpg
> 
> sips is a good companion to imagemagick's convert for raster formats, it is 
> fast and offers a number of features.
> 
> As IM have stated they will support IMv6 for another ten years, it's probably 
> best to not rush to IMv7 considering the number of changes
> 
> Sean
> 
> 
> On Fri, Sep 25, 2020 at 11:59 AM Ruben Di Battista  <mailto:rubendibatti...@gmail.com>> wrote:
> Moreover, HEIC format seems to be included here:
> https://github.com/macports/macports-ports/pull/6021 
> <https://github.com/macports/macports-ports/pull/6021>
> 
> Are there any problems?
> 
> On Fri, Sep 25, 2020 at 5:58 PM Ruben Di Battista
> mailto:rubendibatti...@gmail.com>> wrote:
> >
> > Hello Christoph,
> >
> > here's there's a discussion about version 7:
> > https://github.com/macports/macports-ports/pull/5014 
> > <https://github.com/macports/macports-ports/pull/5014> and here
> > https://trac.macports.org/ticket/51310 
> > <https://trac.macports.org/ticket/51310>. It probably will be provided
> > as a separate port.
> >
> > On Fri, Sep 25, 2020 at 5:40 PM Christoph Kukulies  > <mailto:k...@kukulies.org>> wrote:
> > >
> > > I was seeking for a means to convert Apples new HEIC/HEIF format to more 
> > > traditional formats and I always remembered  ImageMagick being a good 
> > > choice for that.
> > > Unfortunately the macports version is quite outdated.
> > > 6.9.11-29
> > >
> > > vs. 7.0.10-30 being the latest.
> > >
> > > How can I get a newer version via macports?
> > >
> > > —
> > > Christoph
> > >
> >
> >
> > --
> >   _
> > -. .´  |
> >   ',  ;|∞∞
> > ˜˜   |∞ RdB
> > ,.,|∞∞
> >   .'   '.  |
> > -'   `'
> > https://rdb.is <https://rdb.is/>
> 
> 
> 
> -- 
>   _
> -. .´  |
>   ',  ;|∞∞
> ˜˜   |∞ RdB
> ,.,|∞∞
>   .'   '.  |
> -'   `'
> https://rdb.is <https://rdb.is/>



smime.p7s
Description: S/MIME cryptographic signature

ImageMagick port outdated

[Christoph Kukulies]

I was seeking for a means to convert Apples new HEIC/HEIF format to more 
traditional formats and I always remembered  ImageMagick being a good choice 
for that.
Unfortunately the macports version is quite outdated.
6.9.11-29

vs. 7.0.10-30 being the latest.

How can I get a newer version via macports?

—
Christoph



smime.p7s
Description: S/MIME cryptographic signature

Re: MS Sans Serif font in X11 under macOS

[Christoph Kukulies]

I come to the conclusion that it must be a Catalina problem with X11 fonts 
(directory access rights or something in that direction).

When I run the program bsvc locally under macOS (catalina 15.5.6) the 
application starts and has no font problem at all.

It seems to be a problem with the remote client accessing the X11-server.

—
Christoph



> Am 22.08.2020 um 11:23 schrieb Peter West :
> 
> On my Mojave installation, there’s am MS Reference Sans Serif.
> 
> 
>> On 22 Aug 2020, at 6:32 pm, Andrew Udvare > <mailto:audv...@gmail.com>> wrote:
>> 
>> 
>> 
>> On Sat, Aug 22, 2020, 02:37 Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> I’m running a tk/tcl app on my FreeBSD box that has the font „MS Sans Serif“ 
>> wired in.
>> This leads to an X11-error when starting the application (bsvc) with my 
>> macOS (catalina 15.5.6) as the server:
>> 
>> $ bsvc
>> X Error of failed request:  BadName (named color or font does not exist)
>>   Major opcode of failed request:  45 (X_OpenFont)
>>   Serial number of failed request:  42
>>   Current serial number in output stream:  59
>> 
>> 
>> Is there a way to install the missing font using a macport? Or what is the 
>> closest standard X11 font that can be used instead of the MS font?
>> 
>> That font should be included with macOS as it has been since Leopard. It's 
>> possibly named slightly differently.
>> 
>> The closest font is probably Helvetica but your app has the MS font hard 
>> coded.
>> 
>> —
>> Christoph
>> 
>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: MS Sans Serif font in X11 under macOS

[Christoph Kukulies]

Funnily, when I run the same application (bsvc) locally on macOS against the 
same server (XQuartz 1.20.8 xorg server 1.20.8)
the font problem doesn’t show up.


It must be some other problem with the X11forwarding perhaps?


> Am 22.08.2020 um 11:23 schrieb Peter West :
> 
> On my Mojave installation, there’s am MS Reference Sans Serif.
> 
> 
>> On 22 Aug 2020, at 6:32 pm, Andrew Udvare > <mailto:audv...@gmail.com>> wrote:
>> 
>> 
>> 
>> On Sat, Aug 22, 2020, 02:37 Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> I’m running a tk/tcl app on my FreeBSD box that has the font „MS Sans Serif“ 
>> wired in.
>> This leads to an X11-error when starting the application (bsvc) with my 
>> macOS (catalina 15.5.6) as the server:
>> 
>> $ bsvc
>> X Error of failed request:  BadName (named color or font does not exist)
>>   Major opcode of failed request:  45 (X_OpenFont)
>>   Serial number of failed request:  42
>>   Current serial number in output stream:  59
>> 
>> 
>> Is there a way to install the missing font using a macport? Or what is the 
>> closest standard X11 font that can be used instead of the MS font?
>> 
>> That font should be included with macOS as it has been since Leopard. It's 
>> possibly named slightly differently.
>> 
>> The closest font is probably Helvetica but your app has the MS font hard 
>> coded.
>> 
>> —
>> Christoph
>> 
>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

MS Sans Serif font in X11 under macOS

[Christoph Kukulies]

I’m running a tk/tcl app on my FreeBSD box that has the font „MS Sans Serif“ 
wired in.
This leads to an X11-error when starting the application (bsvc) with my macOS 
(catalina 15.5.6) as the server:

$ bsvc
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  42
  Current serial number in output stream:  59


Is there a way to install the missing font using a macport? Or what is the 
closest standard X11 font that can be used instead of the MS font?

—
Christoph





smime.p7s
Description: S/MIME cryptographic signature

Re: X11.bin Error opening or reading file

[Christoph Kukulies]

And finally I figured out that this got to be installed using npm.

Sorry for being off topic what ports is concerned, but the missing X11.bin 
error remains addressed.

—
Christoph



> Am 05.08.2020 um 17:14 schrieb Christoph Kukulies :
> 
> It might be that the xpm I meant is not the one being addressed with the port 
> install command.
> 
> This is the one I mean:
> 
> https://xpack.github.io/xpm/install/ <https://xpack.github.io/xpm/install/>
> 
> 
>> Am 05.08.2020 um 16:46 schrieb Christoph Kukulies > <mailto:k...@kukulies.org>>:
>> 
>> I’m trying to install xpm as a port. Before doing that I was asked to do a 
>> ports selfupdate and a port reclaim.
>> Did that but I’m stuck in this:
>> 
>> Christophs-MBP:~ kuku$ sudo port reclaim
>> --->  Checking for unnecessary unrequested ports
>> Found no unrequested ports without requested dependents.
>> --->  Checking for inactive ports
>> Found no inactive ports.
>> --->  Building list of distfiles still in use
>> Warning: cltversion: The Command Line Tools are installed, but MacPorts 
>> cannot determine the version.
>> Warning: cltversion: For a possible fix, please see: 
>> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
>> <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>
>> --->  Searching for unused distfiles 
>> Found 7 files (total 12.57 MiB) that are no longer needed and can be deleted.
>> [l]ist/[d]elete/[K]eep: d
>> Deleting...
>> --->  Scanning binaries for linking errors
>> Warning: Error parsing file 
>> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin: Error opening or 
>> reading file
>> --->  No broken files found.
>> --->  No broken ports found.
>> Christophs-MBP:~ kuku$  
>> 
>> 
>> Any clues?
>> 
>> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: X11.bin Error opening or reading file

[Christoph Kukulies]

It might be that the xpm I meant is not the one being addressed with the port 
install command.

This is the one I mean:

https://xpack.github.io/xpm/install/ <https://xpack.github.io/xpm/install/>


> Am 05.08.2020 um 16:46 schrieb Christoph Kukulies :
> 
> I’m trying to install xpm as a port. Before doing that I was asked to do a 
> ports selfupdate and a port reclaim.
> Did that but I’m stuck in this:
> 
> Christophs-MBP:~ kuku$ sudo port reclaim
> --->  Checking for unnecessary unrequested ports
> Found no unrequested ports without requested dependents.
> --->  Checking for inactive ports
> Found no inactive ports.
> --->  Building list of distfiles still in use
> Warning: cltversion: The Command Line Tools are installed, but MacPorts 
> cannot determine the version.
> Warning: cltversion: For a possible fix, please see: 
> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>
> --->  Searching for unused distfiles 
> Found 7 files (total 12.57 MiB) that are no longer needed and can be deleted.
> [l]ist/[d]elete/[K]eep: d
> Deleting...
> --->  Scanning binaries for linking errors
> Warning: Error parsing file 
> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin: Error opening or 
> reading file
> --->  No broken files found.
> --->  No broken ports found.
> Christophs-MBP:~ kuku$  
> 
> 
> Any clues?
> 
> Christoph



smime.p7s
Description: S/MIME cryptographic signature

X11.bin Error opening or reading file

[Christoph Kukulies]

I’m trying to install xpm as a port. Before doing that I was asked to do a 
ports selfupdate and a port reclaim.
Did that but I’m stuck in this:

Christophs-MBP:~ kuku$ sudo port reclaim
--->  Checking for unnecessary unrequested ports
Found no unrequested ports without requested dependents.
--->  Checking for inactive ports
Found no inactive ports.
--->  Building list of distfiles still in use
Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot 
determine the version.
Warning: cltversion: For a possible fix, please see: 
https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt
--->  Searching for unused distfiles 
Found 7 files (total 12.57 MiB) that are no longer needed and can be deleted.
[l]ist/[d]elete/[K]eep: d
Deleting...
--->  Scanning binaries for linking errors
Warning: Error parsing file 
/Applications/MacPorts/X11.app/Contents/MacOS/X11.bin: Error opening or reading 
file
--->  No broken files found.
--->  No broken ports found.
Christophs-MBP:~ kuku$  


Any clues?

Christoph

smime.p7s
Description: S/MIME cryptographic signature

Re: xterm: unable to locate a suitable font

[Christoph Kukulies]

Meanwhile I managed to use a font in .Xdefaults that is recognized. Did an 
xlsfonts and chose one out of the list.
But I don’t recall to have had to use such intricate things before to use ssh 
-Y from within a terminal. And through an xterm
now ssh -Y doesn’t work either.

I always used the normal macOS terminal before, IIRC.
 
Christoph

> Am 10.07.2020 um 09:53 schrieb Christoph Kukulies :
> 
> Catalina 10.15.5
> 
> Cannot open an xterm - XQuartz 1.20.8 xorg server
> 
> 
> When I start X11 an click  on Programme->Terminal, nothing happens.
> Clicking Xlogo, Xman works. Starting an xclock from within a normal macOS 
> terminal also starts X11
> and the xclock appears.
> 
> When I type xterm in a normal macOS terminal, I’ getting xterm: unable to 
> locate a suitable font
> 
> Creating a  .Xdefaults with an appropriate entry doesn’t help. 
> I remember that that used to work.
> 
> A problem with path since I switched to bash? But switching back to zsh 
> doesn’t help either.
> 
> 
> 
> —
> Christoph



smime.p7s
Description: S/MIME cryptographic signature

xterm: unable to locate a suitable font

[Christoph Kukulies]

Catalina 10.15.5

Cannot open an xterm - XQuartz 1.20.8 xorg server


When I start X11 an click  on Programme->Terminal, nothing happens.
Clicking Xlogo, Xman works. Starting an xclock from within a normal macOS 
terminal also starts X11
and the xclock appears.

When I type xterm in a normal macOS terminal, I’ getting xterm: unable to 
locate a suitable font

Creating a  .Xdefaults with an appropriate entry doesn’t help. 
I remember that that used to work.

A problem with path since I switched to bash? But switching back to zsh doesn’t 
help either.



—
Christoph

smime.p7s
Description: S/MIME cryptographic signature

Re: Building xorg fails

[Christoph Kukulies]

>> 
>> I would expect an hour lasting compilation orgy.
> 
> Not at all just rebuilding frog-server takes a few minutes not an hour…
> 
> sudo port uninstall xorg-server
> sudo port -s install xorg-server
> 
> -s forces build from source…
> 
> However, I fail to see the need for you to build from source…. The binary 
> tarballs are perfectly functional.
> 
> 

OK. thanks. Wasn’t aware of that. Mixed macports up a bit with FreeBSD ports 
tree, where everything is built from source while
binary package are treated separately by the pkg tool.

All is fine now. 

Thanks a lot for helping and clarification.

—
Christoph

Re: Building xorg fails

[Christoph Kukulies]

> Am 09.05.2020 um 17:02 schrieb Lenore Horner :
> 
> Try cleaning after uninstalling (although when I recently uninstalled 
> inactive, I think clean happened automatically).  
> 
>> On May 9, 2020, at 10:57, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> If you meant update the command line tools I did so now. 
>> 
>> How can I rebuild xorg-server (or maybe the whole xorg) now. When doing an 
>> uninstall, a subsequent install
>> is satisfied so quickly that it doesn’t seem anything has been rebuilt at 
>> all.

I did:


Christophs-MBP:~ kuku$ sudo port  clean xorg-server
--->  Cleaning xorg-server
Christophs-MBP:~ kuku$ sudo port uninstall xorg
--->  Deactivating xorg @20090316_0
--->  Cleaning xorg
--->  Uninstalling xorg @20090316_0
--->  Cleaning xorg
Christophs-MBP:~ kuku$ sudo port clean xorg-server
--->  Cleaning xorg-server

Christophs-MBP:~ kuku$ sudo port install xorg
--->  Computing dependencies for xorg
The following dependencies will be installed:  xorg-server
Continue? [Y/n]: Y
--->  Fetching archive for xorg-server
--->  Attempting to fetch xorg-server-1.20.8_0.darwin_19.x86_64.tbz2 from 
https://packages.macports.org/xorg-server
--->  Attempting to fetch xorg-server-1.20.8_0.darwin_19.x86_64.tbz2.rmd160 
from https://packages.macports.org/xorg-server
--->  Installing xorg-server @1.20.8_0
--->  Activating xorg-server @1.20.8_0
--->  Cleaning xorg-server
--->  Fetching archive for xorg
--->  Attempting to fetch xorg-20090316_0.darwin_19.noarch.tbz2 from 
https://packages.macports.org/xorg
--->  Attempting to fetch xorg-20090316_0.darwin_19.noarch.tbz2.rmd160 from 
https://packages.macports.org/xorg
--->  Installing xorg @20090316_0
--->  Activating xorg @20090316_0
--->  Cleaning xorg
--->  Scanning binaries for linking errors
--->  No broken files found. 
--->  No broken ports found.
Christophs-MBP:~ kuku$ 

I would expect an hour lasting compilation orgy.

Re: Building xorg fails

[Christoph Kukulies]

If you meant update the command line tools I did so now. 

How can I rebuild xorg-server (or maybe the whole xorg) now. When doing an 
uninstall, a subsequent install
is satisfied so quickly that it doesn’t seem anything has been rebuilt at all.



> Am 09.05.2020 um 14:04 schrieb Christopher Jones :
> 
> 
> 
>> On 9 May 2020, at 12:59 pm, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> 
>> The failure exists also on just building xorg-server.
>> 
>> I gout around it by:
>> 
>> sudo ln -s 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
>>  /Library/Developer/CommandLineTools/
>> 
>> 
>> (found that on a japanes site:
>> https://qiita.com/kazuhidet/items/70d983c6b7381a839471 
>> <https://qiita.com/kazuhidet/items/70d983c6b7381a839471>)
> 
> 
> bad idea. strongly suggest you undo that.
> 
> If you had checked the failing port log file you most probably would have 
> found an error message directing you to
> 
> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>
> 
> Go there and follow the instructions therein.
> 
> Chris
> 
> 
>> 
>> 
>>> Am 09.05.2020 um 13:53 schrieb Christopher Jones >> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>> 
>>> 
>>> you do not need to install all off xorg just to get the X11 server. You 
>>> only need xorg-server for that.
>>> 
>>>> On 9 May 2020, at 9:12 am, Christoph Kukulies >>> <mailto:k...@kukulies.org>> wrote:
>>>> 
>>>> In my desperation about this - currently unresolvable x11/Quartz server 
>>>> problem - I’m trying tp build Xorg/Quartz under Catalina 10.15.4, but I’m 
>>>> running into an error right off:
>>>> 
>>>> 
>>>> kuku@Christophs-MBP ~ % sudo port install xorg
>>>> Password:
>>>> --->  Computing dependencies for xorg
>>>> The following dependencies will be installed: 
>>>>  Xft2
>>>>  font-adobe-100dpi
>>>>  font-adobe-75dpi
>>>>  font-adobe-utopia-100dpi
>>>>  font-adobe-utopia-75dpi
>>>>  font-adobe-utopia-type1
>>>>  font-arabic-misc
>>>>  font-bh-100dpi
>>>>  font-bh-75dpi
>>>>  font-bh-lucidatypewriter-100dpi
>>>>  font-bh-lucidatypewriter-75dpi
>>>>  font-bh-ttf
>>>>  font-bh-type1
>>>>  font-bitstream-100dpi
>>>>  font-bitstream-75dpi
>>>>  font-bitstream-speedo
>>>>  font-bitstream-type1
>>>>  font-cronyx-cyrillic
>>>>  font-cursor-misc
>>>>  font-daewoo-misc
>>>>  font-dec-misc
>>>>  font-ibm-type1
>>>>  font-isas-misc
>>>>  font-jis-misc
>>>>  font-micro-misc
>>>>  font-misc-cyrillic
>>>>  font-misc-meltho
>>>>  font-misc-misc
>>>>  font-mutt-misc
>>>>  font-schumacher-misc
>>>>  font-screen-cyrillic
>>>>  font-sony-misc
>>>>  font-sun-misc
>>>>  font-winitzki-cyrillic
>>>>  font-xfree86-type1
>>>>  fontconfig
>>>>  ossp-uuid
>>>>  x11perf
>>>>  xbacklight
>>>>  xcalc
>>>>  xclipboard
>>>>  xclock
>>>>  xcmsdb
>>>>  xcompmgr
>>>>  xconsole
>>>>  xcursorgen
>>>>  xditview
>>>>  xdm
>>>>  xdpyinfo
>>>>  xedit
>>>>  xev
>>>>  xeyes
>>>>  xfd
>>>>  xfindproxy
>>>>  xfontsel
>>>>  xfs
>>>>  xfsinfo
>>>>  xgamma
>>>>  xgc
>>>>  xinput
>>>>  xkbevd
>>>>  xkbprint
>>>>  xkbutils
>>>>  xkill
>>>>  xload
>>>>  xlogo
>>>>  xlsatoms
>>>>  xlsclients
>>>>  xlsfonts
>>>>  xmag
>>>>  xman
>>>>  xmessage
>>>>  xmh
>>>>  xmodmap
>>>>  xmore
>>>>  xorg-apps
>>>>  xorg-fonts
>>>>  xorg-libXTrap
>>>>  xorg-libXtst
>>>>  xorg-libXv
>>>>  xorg-libdmx
>>>>  xorg-scripts
>>>>  xorg-server
>>>>  xpr
>>>>  xprop
>>>>  xrandr
>>>>  xrefresh
>>>>  xsetmode
>>>>  xsetpointer
>>>>  xsetroot
>>>&

Re: X11 no longer working

[Christoph Kukulies]

> Am 09.05.2020 um 16:29 schrieb Christopher Jones :
> 
> 
> 
>> On 9 May 2020, at 1:21 pm, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> The port install xorg-server went through and as a result I have XQuartz 
>> working again.
>> 
>> Now you say I should revert this (japanes sites’) hack. I removed the 
>> symbolic link that this hack suggested, ran
>> sudo uninstall xorg-server and then sudo install xorg-server. It ran much 
>> faster now as if it didn’t compile anything.
> 
> If you don’t follow the instructions in the link I sent you you will likely 
> have other problems. The above means nothing as you didn’t rebuild anything. 
> You have been warned…



I followed the link you gave me but I didn’t find the cause I should look for 
in the list of possible failures on that page.

Also cannot reconstruct the failing case now. The log file seems to be 
overwritten.

Re: X11 no longer working

[Christoph Kukulies]

The port install xorg-server went through and as a result I have XQuartz 
working again.

Now you say I should revert this (japanes sites’) hack. I removed the symbolic 
link that this hack suggested, ran
sudo uninstall xorg-server and then sudo install xorg-server. It ran much 
faster now as if it didn’t compile anything.

So I didn’t run into this error below again.

Thanks to all. 


X11 working again.

—
Christoph


> Am 09.05.2020 um 14:09 schrieb Christopher Jones :
> 
> 
> Thats not what I am referring to. There was likely a warning earlier on 
> directing you to the macports problem hot list.
> 
>> On 9 May 2020, at 1:07 pm, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> 
>> 
>>> Am 09.05.2020 um 13:51 schrieb Christopher Jones >> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>> 
>>> 
>>> then you need to figure out what is failing for you with ossp-uuid ...
>>> 
>> 
>> 
>> 
>> The error was this one:
>> 
>> 
>> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
>> 
>> 
>> see below in context:
>> 
>> :info:build /usr/bin/clang -c  -I. -I.. -fno-common -DPERL_DARWIN 
>> -mmacosx-version-min=10.15 -pipe -Os 
>> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk 
>> -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include 
>> -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  
>> "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
>> :info:build clang: warning: no such sysroot directory: 
>> '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' 
>> [-Wmissing-sysroot]
>> :info:build In file included from uuid.xs:30:
>> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
>> :info:build #include 
>> :info:build  ^
>> :info:build 1 error generated.
>> :info:build make[1]: *** [uuid.o] Error 1
>> :info:build make[1]: Leaving directory 
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
>> :info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
>> :info:build make: Leaving directory 
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
>> :info:build Command failed:  cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
>>  && /usr/bin/make -j8 -w all
>> :info:build Exit code: 2
>> :error:build Failed to build ossp-uuid: command execution failed
>> :debug:build Error code: CHILDSTATUS 19252 2
>> :debug:build Backtrace: command execution failed
>> :debug:build while executing
>> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
>> :debug:build invoked from within
>> :debug:build "command_exec build"
>> :debug:build (procedure "portbuild::build_main" line 8)
>> :debug:build invoked from within
>> :debug:build "$procedure $targetname"
>> :error:build See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>>  for details.
>> version:1
>> :debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
>> :debug:sysinfo MacPorts 2.6.2
>> :debug:sysinfo Xcode 11.4.1
>> :debug:sysinfo SDK 10.15
>> :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
>> :debug:clean dropping privileges: euid changed to 502, egid changed to 501.
>> :debug:main Executing org.macports.main (ossp-uuid)
>> 
>> 
>>>> On 9 May 2020, at 12:48 pm, Christoph Kukulies >>> <mailto:k...@kukulies.org>> wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> Am 09.05.2020 um 13:41 schrieb Christopher Jones 
>>>>> mailto:jon...@hep.phy.cam.ac.uk>>:
>>>>> 
>>>>> looks like your xorg-server installation is not working. Try removing it, 
>>>>> reinstall, then log out and back in again.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> That’s what I tried already and failed on that (see other post subject 
>>>> „Building xorg fails“):
>>>> 
>>>> 
>>>> kuku@

Re: X11 no longer working

[Christoph Kukulies]

> Am 09.05.2020 um 13:51 schrieb Christopher Jones :
> 
> 
> then you need to figure out what is failing for you with ossp-uuid ...
> 



The error was this one:


:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found


see below in context:

:info:build /usr/bin/clang -c  -I. -I.. -fno-common -DPERL_DARWIN 
-mmacosx-version-min=10.15 -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk 
-fno-strict-aliasing -fstack-protector-strong -I/opt/local/include 
-DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  
"-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build clang: warning: no such sysroot directory: 
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include 
:info:build  ^
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
 && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 19252 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
 for details.
version:1
:debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
:debug:sysinfo MacPorts 2.6.2
:debug:sysinfo Xcode 11.4.1
:debug:sysinfo SDK 10.15
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
:debug:clean dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Executing org.macports.main (ossp-uuid)


>> On 9 May 2020, at 12:48 pm, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> 
>> 
>> 
>> 
>>> Am 09.05.2020 um 13:41 schrieb Christopher Jones >> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>> 
>>> looks like your xorg-server installation is not working. Try removing it, 
>>> reinstall, then log out and back in again.
>> 
>> 
>> 
>> 
>> That’s what I tried already and failed on that (see other post subject 
>> „Building xorg fails“):
>> 
>> 
>> kuku@Christophs-MBP ~ % sudo port install xorg-server
>> --->  Computing dependencies for xorg-server
>> The following dependencies will be installed: 
>>  font-adobe-100dpi
>>  font-adobe-75dpi
>>  font-adobe-utopia-100dpi
>>  font-adobe-utopia-75dpi
>>  font-adobe-utopia-type1
>>  font-arabic-misc
>>  font-bh-100dpi
>>  font-bh-75dpi
>>  font-bh-lucidatypewriter-100dpi
>>  font-bh-lucidatypewriter-75dpi
>>  font-bh-ttf
>>  font-bh-type1
>>  font-bitstream-100dpi
>>  font-bitstream-75dpi
>>  font-bitstream-speedo
>>  font-bitstream-type1
>>  font-cronyx-cyrillic
>>  font-cursor-misc
>>  font-daewoo-misc
>>  font-dec-misc
>>  font-ibm-type1
>>  font-isas-misc
>>  font-jis-misc
>>  font-micro-misc
>>  font-misc-cyrillic
>>  font-misc-meltho
>>  font-misc-misc
>>  font-mutt-misc
>>  font-schumacher-misc
>>  font-screen-cyrillic
>>  font-sony-misc
>>  font-sun-misc
>>  font-winitzki-cyrillic
>>  font-xfree86-type1
>>  fontconfig
>>  ossp-uuid
>>  xorg-fonts
>> Continue? [Y/n]: Y
>> --->  Fetching archive for ossp-uuid
>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>> from https://packages.macports.org/ossp-uuid 
>> <https://packages.macports.org/ossp-uuid>
>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.d

Re: Building xorg fails

[Christoph Kukulies]

The failure exists also on just building xorg-server.

I gout around it by:

sudo ln -s 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
 /Library/Developer/CommandLineTools/


(found that on a japanes site:
https://qiita.com/kazuhidet/items/70d983c6b7381a839471 
<https://qiita.com/kazuhidet/items/70d983c6b7381a839471>)


> Am 09.05.2020 um 13:53 schrieb Christopher Jones :
> 
> 
> you do not need to install all off xorg just to get the X11 server. You only 
> need xorg-server for that.
> 
>> On 9 May 2020, at 9:12 am, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> In my desperation about this - currently unresolvable x11/Quartz server 
>> problem - I’m trying tp build Xorg/Quartz under Catalina 10.15.4, but I’m 
>> running into an error right off:
>> 
>> 
>> kuku@Christophs-MBP ~ % sudo port install xorg
>> Password:
>> --->  Computing dependencies for xorg
>> The following dependencies will be installed: 
>>  Xft2
>>  font-adobe-100dpi
>>  font-adobe-75dpi
>>  font-adobe-utopia-100dpi
>>  font-adobe-utopia-75dpi
>>  font-adobe-utopia-type1
>>  font-arabic-misc
>>  font-bh-100dpi
>>  font-bh-75dpi
>>  font-bh-lucidatypewriter-100dpi
>>  font-bh-lucidatypewriter-75dpi
>>  font-bh-ttf
>>  font-bh-type1
>>  font-bitstream-100dpi
>>  font-bitstream-75dpi
>>  font-bitstream-speedo
>>  font-bitstream-type1
>>  font-cronyx-cyrillic
>>  font-cursor-misc
>>  font-daewoo-misc
>>  font-dec-misc
>>  font-ibm-type1
>>  font-isas-misc
>>  font-jis-misc
>>  font-micro-misc
>>  font-misc-cyrillic
>>  font-misc-meltho
>>  font-misc-misc
>>  font-mutt-misc
>>  font-schumacher-misc
>>  font-screen-cyrillic
>>  font-sony-misc
>>  font-sun-misc
>>  font-winitzki-cyrillic
>>  font-xfree86-type1
>>  fontconfig
>>  ossp-uuid
>>  x11perf
>>  xbacklight
>>  xcalc
>>  xclipboard
>>  xclock
>>  xcmsdb
>>  xcompmgr
>>  xconsole
>>  xcursorgen
>>  xditview
>>  xdm
>>  xdpyinfo
>>  xedit
>>  xev
>>  xeyes
>>  xfd
>>  xfindproxy
>>  xfontsel
>>  xfs
>>  xfsinfo
>>  xgamma
>>  xgc
>>  xinput
>>  xkbevd
>>  xkbprint
>>  xkbutils
>>  xkill
>>  xload
>>  xlogo
>>  xlsatoms
>>  xlsclients
>>  xlsfonts
>>  xmag
>>  xman
>>  xmessage
>>  xmh
>>  xmodmap
>>  xmore
>>  xorg-apps
>>  xorg-fonts
>>  xorg-libXTrap
>>  xorg-libXtst
>>  xorg-libXv
>>  xorg-libdmx
>>  xorg-scripts
>>  xorg-server
>>  xpr
>>  xprop
>>  xrandr
>>  xrefresh
>>  xsetmode
>>  xsetpointer
>>  xsetroot
>>  xsm
>>  xstdcmap
>>  xterm
>>  xtrap
>>  xvinfo
>>  xwd
>>  xwininfo
>>  xwud
>> Continue? [Y/n]: Y
>> --->  Fetching archive for ossp-uuid
>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>> from https://packages.macports.org/ossp-uuid 
>> <https://packages.macports.org/ossp-uuid>
>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>> from http://nue.de.packages.macports.org/ossp-uuid 
>> <http://nue.de.packages.macports.org/ossp-uuid>
>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>> from http://lil.fr.packages.macports.org/ossp-uuid 
>> <http://lil.fr.packages.macports.org/ossp-uuid>
>> --->  Building ossp-uuid
>> Error: Failed to build ossp-uuid: command execution failed
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>>  for details.
>> Error: Follow https://guide.macports.org/#project.tickets 
>> <https://guide.macports.org/#project.tickets> to report a bug.
>> Error: Processing of port xorg failed
>> 
>> tail of main.log:
>> 
>> 
>> kuku@Christophs-MBP ~ % :info:build "/opt/local/bin/perl5.26" 
>> -MExtUtils::Command::MM -e 'cp_nonempty' -- uuid.bs 
>> blib/arch/auto/OSSP/uuid/uuid.bs 644
>> :info:build Skip blib/lib/OSSP/uuid.pm (unchanged)
>> :info:build Skip blib/lib/OSSP/../Data/UUID.pm (unchanged)
>> :info:build Skip blib/lib/OSSP/../Data/UUID.pod (unchanged)
>> :info:build Skip blib/lib/OSSP/uuid.pod (unchanged)
>> :info:build 1 error generated.
>> :info:build make[1]: *** [

Re: X11 no longer working

[Christoph Kukulies]

> Am 09.05.2020 um 13:41 schrieb Christopher Jones :
> 
> looks like your xorg-server installation is not working. Try removing it, 
> reinstall, then log out and back in again.




That’s what I tried already and failed on that (see other post subject 
„Building xorg fails“):


kuku@Christophs-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 

> 
>> On 9 May 2020, at 12:39 pm, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>> 
>> 
>> 
>>> Am 09.05.2020 um 13:22 schrieb Richard Tobin >> <mailto:rich...@inf.ed.ac.uk>>:
>>> 
>>> 
>>>>>> Does running xclock or other X clients locally work?
>>> 
>>>> No. xclock also hangs locally.
>>> 
>>> So it's not an ssh problem.
>>> 
>>>>> Also, do ssh -v -Y and see what it says about X11 forwarding.
>>> 
>>>> Have gone through the ssh connection already in previous posts.
>>> 
>>> So you did, I missed that.
>>> 
>>>> What make me wonder is, when I'm looking at the process command 
>>>> line of the Xquartz process that there is a -nolisten tcp (?!)
>>>> 
>>>> 6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx
>>>> -auth /var/root/.serverauth.6258
>>> 
>>> That's ok, you're not trying to connect to X by TCP, but through
>>> the unix socket :0.  (Just to be sure, try "xclock -display :0")
>> 
>> kuku@Christophs-MBP ~ % xclock -display :0
>> Error: Can't open display: :0
>> kuku@Christophs-MBP ~ % xclock -display \:0
>> Error: Can't open display: :0
>> kuku@Christophs-MBP ~ % echo $DISPLAY
>> /private/tmp/com.apple.launchd.vabAbiJezH/org.macports:0
>> kuku@Christophs-MBP ~ % 
>> 
>>> 
>>> Is there a quartz-wm process running?
>>> 
>> 
>> Not directy. WHat I see is:
>> 
>>  % ps ax | grep -i quartz
>>   419   ??  Ss 0:00.09 
>> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS/QuickLookUIService
>> 13030 s008  R+ 0:00.00 grep -i quartz
>> 
>> 
>>> -- Richard
>>> 
>>> -- 
>>> The University of Edinburgh is a charitable body, registered in
>>> Scotland, with registration number SC005336.
> 

Re: X11 no longer working

[Christoph Kukulies]

> Am 09.05.2020 um 13:22 schrieb Richard Tobin :
> 
> 
 Does running xclock or other X clients locally work?
> 
>> No. xclock also hangs locally.
> 
> So it's not an ssh problem.
> 
>>> Also, do ssh -v -Y and see what it says about X11 forwarding.
> 
>> Have gone through the ssh connection already in previous posts.
> 
> So you did, I missed that.
> 
>> What make me wonder is, when I'm looking at the process command 
>> line of the Xquartz process that there is a -nolisten tcp (?!)
>> 
>> 6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx
>> -auth /var/root/.serverauth.6258
> 
> That's ok, you're not trying to connect to X by TCP, but through
> the unix socket :0.  (Just to be sure, try "xclock -display :0")

kuku@Christophs-MBP ~ % xclock -display :0
Error: Can't open display: :0
kuku@Christophs-MBP ~ % xclock -display \:0
Error: Can't open display: :0
kuku@Christophs-MBP ~ % echo $DISPLAY
/private/tmp/com.apple.launchd.vabAbiJezH/org.macports:0
kuku@Christophs-MBP ~ % 

> 
> Is there a quartz-wm process running?
> 

Not directy. WHat I see is:

 % ps ax | grep -i quartz
  419   ??  Ss 0:00.09 
/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS/QuickLookUIService
13030 s008  R+ 0:00.00 grep -i quartz


> -- Richard
> 
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 

Re: X11 no longer working

[Christoph Kukulies]

The other strange thing is (on the target side, doing an nmap to the server):

Nmap done: 1 IP address (1 host up) scanned in 334.13 seconds
# nmap 192.168.178.51
Starting Nmap 7.70 ( https://nmap.org ) at 2020-05-09 12:55 CEST
Nmap scan report for Christophs-MBP.fritz.box (192.168.178.51)
Host is up (0.00050s latency).
All 1000 scanned ports on Christophs-MBP.fritz.box (192.168.178.51) are closed
MAC Address: A8:60:B6:2E:DF:6D (Apple)

Nmap done: 1 IP address (1 host up) scanned in 333.33 seconds


No port open to the outside.

> Am 09.05.2020 um 13:07 schrieb Christoph Kukulies :
> 
> 
> 
>> Am 09.05.2020 um 12:39 schrieb Richard Tobin > <mailto:rich...@inf.ed.ac.uk>>:
>> 
>>>> Launching X11 manually ./X11 is a good point. Did that and XQuartz
>>>> appears in the dock. Firing then xclock on the Target doesn't do
>>>> a connection. Silence. The xclock just hangs there.
>>> 
>>> Does running xclock or other X clients locally work?
> 
> No. xclock also hangs locally.
> 
> 
>>> 
>>> If it does, X is listening on the unix socket as expected and the
>>> problem must be with ssh connecting to it.  What X-related lines
>>> does /etc/ssh/ssh_config have?
>> 
>> Also, do ssh -v -Y and see what it says about X11 forwarding.
>> 
> 
> 
> Have gone through the ssh connection already in previous posts.
> 
> 
> What make me wonder is, when I’m looking at the process command line of the 
> Xquartz process that there is a
> -nolisten tcp (?!)
> 
>  6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth 
> /var/root/.serverauth.6258
> 
> Who is doing that?
> 
> —
> Christoph
> 
>> -- Richard
>> 
>> -- 
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>> 
> 

Re: X11 no longer working

[Christoph Kukulies]

> Am 09.05.2020 um 12:39 schrieb Richard Tobin :
> 
>>> Launching X11 manually ./X11 is a good point. Did that and XQuartz
>>> appears in the dock. Firing then xclock on the Target doesn't do
>>> a connection. Silence. The xclock just hangs there.
>> 
>> Does running xclock or other X clients locally work?

No. xclock also hangs locally.


>> 
>> If it does, X is listening on the unix socket as expected and the
>> problem must be with ssh connecting to it.  What X-related lines
>> does /etc/ssh/ssh_config have?
> 
> Also, do ssh -v -Y and see what it says about X11 forwarding.
> 


Have gone through the ssh connection already in previous posts.


What make me wonder is, when I’m looking at the process command line of the 
Xquartz process that there is a
-nolisten tcp (?!)

 6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth 
/var/root/.serverauth.6258

Who is doing that?

—
Christoph

> -- Richard
> 
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 

Re: X11 no longer working

[Christoph Kukulies]

Launching X11 manually ./X11 is a good point. Did that and XQuartz appears in 
the dock. Firing then xclock on the Target doesn’t do a connection. Silence. 
The xclock just hangs there.

I don’t see any listening socket:

kuku@Christophs-MBP ~ % ps ax | grep -i x11  
88342   ??  Ss 0:00.81 /opt/local/libexec/privileged_startx -d 
/opt/local/etc/X11/xinit/privileged_startx.d
 6254 s003  S+ 0:01.61 ./X11.bin
 6258 s003  S+ 0:00.02 /bin/sh /opt/X11/bin/startx -- /opt/X11/bin/Xquartz
 6305 s003  S+ 0:00.00 /opt/X11/bin/xinit /opt/X11/lib/X11/xinit/xinitrc -- 
/opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth /var/root/.serverauth.6258
 6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth 
/var/root/.serverauth.6258
 6405 s003  S  0:00.03 /opt/X11/bin/quartz-wm
10624 s005  R+ 0:00.00 grep -i x11
kuku@Christophs-MBP ~ % lsof -U | grep 6254
kuku@Christophs-MBP ~ % lsof -U | grep 6258
kuku@Christophs-MBP ~ % lsof -U | grep 6305
kuku@Christophs-MBP ~ % lsof -U | grep 6306
kuku@Christophs-MBP ~ % lsof -U | grep 6405
kuku@Christophs-MBP ~ % lsof -U | grep 88432
kuku@Christophs-MBP ~ % 

Building xorg fails

[Christoph Kukulies]

In my desperation about this - currently unresolvable x11/Quartz server problem 
- I’m trying tp build Xorg/Quartz under Catalina 10.15.4, but I’m running into 
an error right off:


kuku@Christophs-MBP ~ % sudo port install xorg
Password:
--->  Computing dependencies for xorg
The following dependencies will be installed: 
 Xft2
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 x11perf
 xbacklight
 xcalc
 xclipboard
 xclock
 xcmsdb
 xcompmgr
 xconsole
 xcursorgen
 xditview
 xdm
 xdpyinfo
 xedit
 xev
 xeyes
 xfd
 xfindproxy
 xfontsel
 xfs
 xfsinfo
 xgamma
 xgc
 xinput
 xkbevd
 xkbprint
 xkbutils
 xkill
 xload
 xlogo
 xlsatoms
 xlsclients
 xlsfonts
 xmag
 xman
 xmessage
 xmh
 xmodmap
 xmore
 xorg-apps
 xorg-fonts
 xorg-libXTrap
 xorg-libXtst
 xorg-libXv
 xorg-libdmx
 xorg-scripts
 xorg-server
 xpr
 xprop
 xrandr
 xrefresh
 xsetmode
 xsetpointer
 xsetroot
 xsm
 xstdcmap
 xterm
 xtrap
 xvinfo
 xwd
 xwininfo
 xwud
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from https://packages.macports.org/ossp-uuid 

--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from http://nue.de.packages.macports.org/ossp-uuid 

--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
from http://lil.fr.packages.macports.org/ossp-uuid 

--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets 
 to report a bug.
Error: Processing of port xorg failed

tail of main.log:


kuku@Christophs-MBP ~ % :info:build "/opt/local/bin/perl5.26" 
-MExtUtils::Command::MM -e 'cp_nonempty' -- uuid.bs 
blib/arch/auto/OSSP/uuid/uuid.bs 644
:info:build Skip blib/lib/OSSP/uuid.pm (unchanged)
:info:build Skip blib/lib/OSSP/../Data/UUID.pm (unchanged)
:info:build Skip blib/lib/OSSP/../Data/UUID.pod (unchanged)
:info:build Skip blib/lib/OSSP/uuid.pod (unchanged)
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
 && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 3564 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
 for details.

Re: X11 no longer working

[Christoph Kukulies]

ned unless I had done something to the PATH or 
macports tree.

What I did was remove the X11 icon from the dock, but that after it stopped 
working. It is so that X11 Quartz normally launches automatically when a client 
requests an X11 connection, right?

Still clueless. Maybe I’m overlooking something very obvious?
—
Christoph

> Am 08.05.2020 um 17:41 schrieb Pierre Malard :
> 
> Hi,
> 
> Some possibilities:
> 1) Try your « ssh -Y » in verbose mode like « ssh -v -Y » or
>   « ssh -vv -Y » for more verbose and take a look at the displayed
>   messages.
> 2) Is « xauth » package is on your target?
> 3) What about the « X11DisplayOffset » on your target?
> 4) What about these lines:
>   Source% ssh -Y user@cible
>   Target% echo $DISPLAY
>   Target% xclock
> 
> It’s not an SHELL problem.
> 
> Good luck
> 
>> Le 8 mai 2020 à 16:10, Christoph Kukulies  a écrit :
>> 
>> Today is a havoc day. I changed my login shell to bash. Also added this BASH 
>> Silencing variable succesfully.
>> Was playing around for hours with my FreeBSD system in the network and in 
>> the morning I ran some X clients.
>> Alway saw the X11 Quartz icon in the dock.
>> 
>> Is it correct, the X server starts automatically if an X cient wants to 
>> connect over the network, right.
>> Last thing I did was to remove the X11 icon from the dock. Now suddenly when 
>> I ssh -Y to the FreeBSD system, start xclock there,
>> nothing happens. The xclock command line hangs on the client side. But no 
>> message at all. DISPLAY is localhost:10.0.
>> 
>> I did a reboot of the FreeBSD system already to no avail. What’s going on? 
>> Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it 
>> has got to do with that.
>> 
>> —
>> Christoph
>> 
> 
> --
> Pierre Malard
> 
>   « Je n'ai jamais séparé la République des idées de justice sociale,
> sans laquelle elle n'est qu'un mot »
>  Jean Jaures 
> - 1887
>   |\  _,,,---,,_
>   /,`.-'`'-.  ;-;;,_
>  |,4-  ) )-,_. ,\ (  `'-'
> '---''(_/--'  `-'\_)   πr
> 
> perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. 
> ,\ (  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
> 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
> - --> Ce message n’engage que son auteur <--
> 

X11 no longer working

[Christoph Kukulies]

Today is a havoc day. I changed my login shell to bash. Also added this BASH 
Silencing variable succesfully.
Was playing around for hours with my FreeBSD system in the network and in the 
morning I ran some X clients.
Alway saw the X11 Quartz icon in the dock. 

Is it correct, the X server starts automatically if an X cient wants to connect 
over the network, right.
Last thing I did was to remove the X11 icon from the dock. Now suddenly when I 
ssh -Y to the FreeBSD system, start xclock there,
nothing happens. The xclock command line hangs on the client side. But no 
message at all. DISPLAY is localhost:10.0.

I did a reboot of the FreeBSD system already to no avail. What’s going on? Will 
reboot my Mac and next thing I’ll do is revert to zsh to see whether it has got 
to do with that.

—
Christoph

Login shell

[Christoph Kukulies]

I don’t know if that belongs into macports, but I believe a lot of problems (I 
currently have) with PATHs may be, that Catalina (?) changed the login shell 
from sh (bash) to zsh (or am I wrong with this)?

Where do I change the users’  lofin shell. Unixwise I would say in /etc/passwd, 
but I don’t find any (my) username there.

For instance my anaconda3 installation was totally spoiled after updating to 
Catalina.

For the fun of it I started bash, did a . .bash_profile and started 

conda update —prefix /opt/anaconda3  anaconda

and lo and behold, I received a smooth update in that window. 

Would the world be better for me if I go back to bash login shell? And why did 
Catalina cause such a mess?

—
Christoph

Re: X11 Server (Quartz 1.20.4) not having security extensions

[Christoph Kukulies]

That’s not the issue. I know that. My question see below (I’ll cite):

"Is there a way to make the server having these extensions? Or are there 
reasons standing against this?"

—
Christoph


> Am 07.05.2020 um 15:53 schrieb Uli Wienands :
> 
> Try ssh -Y ...
> 
> Uli
> 
> On 5/7/20 2:43 AM, Christoph Kukulies wrote:
>> I found that
>> 
>> ssh -X user@remote_host 
>> 
>> 
>> doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
>> (XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.
>> 
>> 
>> $ xdpyinfo -queryExtensions
>> 
>> name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
>> version number:11.0
>> vendor string:The X.Org <http://x.org/> Foundation
>> vendor release number:12004000
>> X.Org <http://x.org/> version: 1.20.4
>> maximum request size:  16777212 bytes
>> motion buffer size:  256
>> bitmap unit, bit order, padding:32, LSBFirst, 32
>> image byte order:LSBFirst
>> number of supported pixmap formats:7
>> supported pixmap formats:
>>depth 1, bits_per_pixel 1, scanline_pad 32
>>depth 4, bits_per_pixel 8, scanline_pad 32
>>depth 8, bits_per_pixel 8, scanline_pad 32
>>depth 15, bits_per_pixel 16, scanline_pad 32
>>depth 16, bits_per_pixel 16, scanline_pad 32
>>depth 24, bits_per_pixel 32, scanline_pad 32
>>depth 32, bits_per_pixel 32, scanline_pad 32
>> keycode range:minimum 8, maximum 255
>> focus:  None
>> number of extensions:21
>>Apple-DRI  (opcode: 128, base event: 64, base error: 128)
>>Apple-WM  (opcode: 129, base event: 68, base error: 130)
>>BIG-REQUESTS  (opcode: 134)
>>DAMAGE  (opcode: 142, base event: 97, base error: 154)
>>DOUBLE-BUFFER  (opcode: 144, base error: 155)
>>GLX  (opcode: 148, base event: 101, base error: 159)
>>Generic Event Extension  (opcode: 130)
>>MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
>>MIT-SHM  (opcode: 132, base event: 72, base error: 132)
>>Present  (opcode: 145)
>>RANDR  (opcode: 141, base event: 95, base error: 149)
>>RENDER  (opcode: 140, base error: 144)
>>SHAPE  (opcode: 131, base event: 71)
>>SYNC  (opcode: 135, base event: 90, base error: 138)
>>X-Resource  (opcode: 146)
>>XC-MISC  (opcode: 137)
>>XFIXES  (opcode: 139, base event: 93, base error: 142)
>>XINERAMA  (opcode: 138)
>>XInputExtension  (opcode: 133, base event: 73, base error: 133)
>>XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
>>XVideo  (opcode: 147, base event: 99, base error: 156)
>> default screen number:0
>> number of screens:1
>> 
>> screen #0:
>>  dimensions:1680x1028 pixels (445x272 millimeters)
>>  resolution:96x96 dots per inch
>>  depths (7):24, 1, 4, 8, 15, 16, 32
>>  root window id:0x111
>>  depth of root window:24 planes
>>  number of colormaps:minimum 1, maximum 1
>>  default colormap:0x21
>>  default number of colormap cells:256
>>  preallocated pixels:black 0, white 16777215
>>  options:backing-store NO, save-unders NO
>>  largest cursor:32x32
>>  current input event mask:0x1a
>>StructureNotifyMask  SubstructureNotifyMask   
>> SubstructureRedirectMask 
>>  number of visuals:80
>>  default visual id:  0x22
>>  visual:
>>visual id:0x22
>>class:TrueColor
>>depth:24 planes
>>available colormap entries:256 per subfield
>>red, green, blue masks:0xff, 0xff00, 0xff
>>significant bits in color specification:8 bits
>> 
>> 
>> 
>> Is there a way to make the server having these extensions? Or are there 
>> reasons standing against this?
>> 
>> 
>> —
>> Christoph

Cannot do anything with port - upgrade, uninstall not possible

[Christoph Kukulies]

Following the instructions of migrating macports is a dead end to me right now.

all attempts to uninstall or do anything woth the port command ends with that:

kuku@Christophs-MBP ~ % port -qv installed >myports.txt
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
kuku@Christophs-MBP ~ % sudo port -fp uninstall installed
Password:
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
kuku@Christophs-MBP ~ % 

Re: macports suddenly gone on my system

[Christoph Kukulies]

Interestingly I’m now getting this:

kuku@Christophs-MBP ~ % sudo port selfupdate
Password:
Error: Current platform "darwin 19" does not match expected platform "darwin 18"
Error: If you upgraded your OS, please follow the migration instructions: 
https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch

Will now go for reading that chapter


> Am 07.05.2020 um 10:32 schrieb Christoph Kukulies :
> 
> It’s zsh (is that the default on a macOS Catalina, think so)
> No .profile
> .zshrc is there:
> 
> 
> # >>> conda initialize >>>
> # !! Contents within this block are managed by 'conda init' !!
> __conda_setup="$('/Users/kuku/anaconda3/bin/conda' 'shell.zsh' 'hook' 2> 
> /dev/null)"
> if [ $? -eq 0 ]; then
> eval "$__conda_setup"
> else
> if [ -f "/Users/kuku/anaconda3/etc/profile.d/conda.sh" ]; then
> . "/Users/kuku/anaconda3/etc/profile.d/conda.sh"
> else
> export PATH="/Users/kuku/anaconda3/bin:$PATH"
> fi
> fi
> unset __conda_setup
> # <<< conda initialize <<<
> 
> 
> Find the followingat beginning of my .bash_profile (does .bash_profile have 
> impact on zsh? seems so):
> 
> 
> # added by Anaconda3 5.0.1 installer
> export PATH="/Users/kuku/anaconda3/bin:$PATH"
> 
> ##
> # Your previous /Users/kuku/.bash_profile file was backed up as 
> /Users/kuku/.bash_profile.macports-saved_2018-06-23_at_08:25:54
> ##
> 
> # MacPorts Installer addition on 2018-06-23_at_08:25:54: adding an 
> appropriate PATH variable for use with MacPorts.
> export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
> # Finished adapting your PATH environment variable for use with MacPorts.
> 
> 
> —
> Christoph
> 
> 
>> Am 07.05.2020 um 09:55 schrieb Dominik Reichardt > <mailto:domi...@reichardt.de>>:
>> 
>> 
>> Maybe it's still there but the PATH variable changed. Check your .profile 
>> and to make sure look at /opt/local/bin
>> 
>> On Thu, May 7, 2020 at 09:39, Christoph Kukulies > <mailto:k...@kukulies.org>> wrote:
>>> 
>>> Funny, suddenly I can’t do any longer 
>>> 
>>> sudo ports selfupdate
>>> 
>>> kuku@Christophs-MBP ~ % sudo port selfupdate
>>> Password:
>>> sudo: port: command not found
>>> kuku@Christophs-MBP ~ % 
>>> 
>>> I can’t remember having uninstalled macports.
>>> 
>>> —
>>> Christoph
>>> 
>> 
>> 
> 

Re: macports suddenly gone on my system

[Christoph Kukulies]

It’s zsh (is that the default on a macOS Catalina, think so)
No .profile
.zshrc is there:


# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/kuku/anaconda3/bin/conda' 'shell.zsh' 'hook' 2> 
/dev/null)"
if [ $? -eq 0 ]; then
eval "$__conda_setup"
else
if [ -f "/Users/kuku/anaconda3/etc/profile.d/conda.sh" ]; then
. "/Users/kuku/anaconda3/etc/profile.d/conda.sh"
else
export PATH="/Users/kuku/anaconda3/bin:$PATH"
fi
fi
unset __conda_setup
# <<< conda initialize <<<


Find the followingat beginning of my .bash_profile (does .bash_profile have 
impact on zsh? seems so):


# added by Anaconda3 5.0.1 installer
export PATH="/Users/kuku/anaconda3/bin:$PATH"

##
# Your previous /Users/kuku/.bash_profile file was backed up as 
/Users/kuku/.bash_profile.macports-saved_2018-06-23_at_08:25:54
##

# MacPorts Installer addition on 2018-06-23_at_08:25:54: adding an appropriate 
PATH variable for use with MacPorts.
export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
# Finished adapting your PATH environment variable for use with MacPorts.


—
Christoph


> Am 07.05.2020 um 09:55 schrieb Dominik Reichardt :
> 
> 
> Maybe it's still there but the PATH variable changed. Check your .profile and 
> to make sure look at /opt/local/bin
> 
> On Thu, May 7, 2020 at 09:39, Christoph Kukulies  <mailto:k...@kukulies.org>> wrote:
>> 
>> Funny, suddenly I can’t do any longer 
>> 
>> sudo ports selfupdate
>> 
>> kuku@Christophs-MBP ~ % sudo port selfupdate
>> Password:
>> sudo: port: command not found
>> kuku@Christophs-MBP ~ % 
>> 
>> I can’t remember having uninstalled macports.
>> 
>> —
>> Christoph
>> 
> 
> 

X11 Server (Quartz 1.20.4) not having security extensions

[Christoph Kukulies]

I found that

ssh -X user@remote_host 


doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
(XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.


$ xdpyinfo -queryExtensions

name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
version number:11.0
vendor string:The X.Org  Foundation
vendor release number:12004000
X.Org  version: 1.20.4
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:32, LSBFirst, 32
image byte order:LSBFirst
number of supported pixmap formats:7
supported pixmap formats:
   depth 1, bits_per_pixel 1, scanline_pad 32
   depth 4, bits_per_pixel 8, scanline_pad 32
   depth 8, bits_per_pixel 8, scanline_pad 32
   depth 15, bits_per_pixel 16, scanline_pad 32
   depth 16, bits_per_pixel 16, scanline_pad 32
   depth 24, bits_per_pixel 32, scanline_pad 32
   depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:minimum 8, maximum 255
focus:  None
number of extensions:21
   Apple-DRI  (opcode: 128, base event: 64, base error: 128)
   Apple-WM  (opcode: 129, base event: 68, base error: 130)
   BIG-REQUESTS  (opcode: 134)
   DAMAGE  (opcode: 142, base event: 97, base error: 154)
   DOUBLE-BUFFER  (opcode: 144, base error: 155)
   GLX  (opcode: 148, base event: 101, base error: 159)
   Generic Event Extension  (opcode: 130)
   MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
   MIT-SHM  (opcode: 132, base event: 72, base error: 132)
   Present  (opcode: 145)
   RANDR  (opcode: 141, base event: 95, base error: 149)
   RENDER  (opcode: 140, base error: 144)
   SHAPE  (opcode: 131, base event: 71)
   SYNC  (opcode: 135, base event: 90, base error: 138)
   X-Resource  (opcode: 146)
   XC-MISC  (opcode: 137)
   XFIXES  (opcode: 139, base event: 93, base error: 142)
   XINERAMA  (opcode: 138)
   XInputExtension  (opcode: 133, base event: 73, base error: 133)
   XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
   XVideo  (opcode: 147, base event: 99, base error: 156)
default screen number:0
number of screens:1

screen #0:
 dimensions:1680x1028 pixels (445x272 millimeters)
 resolution:96x96 dots per inch
 depths (7):24, 1, 4, 8, 15, 16, 32
 root window id:0x111
 depth of root window:24 planes
 number of colormaps:minimum 1, maximum 1
 default colormap:0x21
 default number of colormap cells:256
 preallocated pixels:black 0, white 16777215
 options:backing-store NO, save-unders NO
 largest cursor:32x32
 current input event mask:0x1a
   StructureNotifyMask  SubstructureNotifyMask   SubstructureRedirectMask 
 number of visuals:80
 default visual id:  0x22
 visual:
   visual id:0x22
   class:TrueColor
   depth:24 planes
   available colormap entries:256 per subfield
   red, green, blue masks:0xff, 0xff00, 0xff
   significant bits in color specification:8 bits



Is there a way to make the server having these extensions? Or are there reasons 
standing against this?


—
Christoph

macports suddenly gone on my system

[Christoph Kukulies]

Funny, suddenly I can’t do any longer 

sudo ports selfupdate

kuku@Christophs-MBP ~ % sudo port selfupdate
Password:
sudo: port: command not found
kuku@Christophs-MBP ~ % 

I can’t remember having uninstalled macports.

—
Christoph

Re: Terminal ^D

[Christoph Kukulies]

Thanks. One (me, as being used to xterm) often forgets about a menu bar being 
there. 

> Am 04.05.2020 um 15:10 schrieb Noam Bernstein :
> 
> All these things are also in the Terminal's "View" menu.
>   
>   Noam
> 
—
Christoph

Re: Terminal ^D

[Christoph Kukulies]

> Am 03.05.2020 um 18:01 schrieb Justin C. Walker :
> 
> 
> 
>> On May 3, 2020, at 08:51 , Christoph Kukulies  wrote:
>> 
>> Sorry, probably not a macports issue, but I’m asking nonetheless:
>> 
>> When I inadvertently type ^D (CTRL-D) in a mac Terminal I’m getting a split 
>> screen. Actuallay my intention was - in old unix manner -
>> to close the terminal.
> 
> Version of OS?
> 

Catalina 10.15.4




>> How do I make this split screen go away and make the terminal behave like 
>> before?
> 
> I will hazard the guess that you keyed CMD-D, not CTRL-D.  The former splits 
> the “pane".
> 
> Once you have a split the pane, you should see two little “pane” icons on the 
> right side of the pane in each of the newly split ones.

But, sorry, I don’t see what you call „little pane icons“.

> 
> Two choices: CMD-SHIFT-D will delete one; so will clicking on one of those 
> thingies on the right.
> 
> That’s how it has worked in the past, and on my 10.13 system now.
> 
> HTH.
> 
> Justin
> 
> --
> Justin C. Walker
> Director
> Institute for the Enhancement of the Director's Income
> --
> Fame is fleeting, but obscurity
>   just drags on and on.  F&E
> 
> 
> 

Terminal ^D

[Christoph Kukulies]

Sorry, probably not a macports issue, but I’m asking nonetheless:

When I inadvertently type ^D (CTRL-D) in a mac Terminal I’m getting a split 
screen. Actuallay my intention was - in old unix manner -
to close the terminal.

How do I make this split screen go away and make the terminal behave like 
before?

—
Christoph

Xterm scrolling very slow

[Christoph Kukulies]

I fired up X11 on my MacbookPro Catalina 10.15.4 and ran a Terminal (xterm).

Scrolling looks funny and very slow. Is this a graphic card thing (BLT 
accelerator ?)


—
Christoph

Re: Freecad ports ends in error

[Christoph Kukulies]

Thanks, Marius,
I‘ll give it a try later today.

—
Christoph 

> Am 29.10.2019 um 02:05 schrieb Marius Schamschula :
> 
> Christoph,
> 
> I just updated FreeCAD to version 0.18.4.
> 
> https://git.io/JeuVl
> 
> My build issue turned out to be MacPort’s trace mode. It prevented make from 
> finding the OpenGL header files in the OpenGL.Framework.
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
>> On Oct 28, 2019, at 4:03 PM, Marius Schamschula  
>> wrote:
>> 
>> Christoph,
>> 
>> Freecad is currently broken!
>> 
>> As you found, Freecad 0.17 is looking for an older version of boost.
>> 
>> Further, Freecad 0.17 depends on Qt4, which is 32bit, and hence, not 
>> compatible with Catalina.
>> 
>> Among other things, Freecad 0.18.x is having problems with the demise of 
>> OpenGL on macOS.
>> 
>> Further, work needs to be done upgrading to Python 3.x, as Python 2.7 is 
>> about to be EOL. Unfortunately, there are some serious issues in this 
>> transition.
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>>> On Oct 28, 2019, at 5:51 AM, Christoph Kukulies  wrote:
>>> 
>>> I was trying to build FreeCAD under macports and at the end I’m getting 
>>> this:
>>> 
>>> --->  Verifying checksums for freecad   
>>> 
>>> --->  Extracting freecad
>>> --->  Applying patches to freecad
>>> --->  Configuring freecad
>>> Error: Failed to configure freecad: configure failure: command execution 
>>> failed
>>> Error: See 
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cad_freecad/freecad/main.log
>>>  for details.
>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>>> Error: Processing of port freecad failed
>>> --->  Some of the ports you installed have notes:
>>>   OpenBLAS has the following notes:
>>> This version is built based on a base architecture for convenience, 
>>> which may not be optimized for your system. To build a version 
>>> customized for your machine, use the +native variant
>>>   eigen3 has the following notes:
>>> This product includes software developed by the University of Chicago, 
>>> as
>>> Operator of Argonne National Laboratory.
>>>   py27-cython has the following notes:
>>> To make the Python 2.7 version of Cython the one that is run when you
>>> execute the commands without a version suffix, e.g. 'cython', run:
>>> 
>>> port select --set cython cython27
>>>   py27-matplotlib has the following notes:
>>> The default backend is the interactive Mac OS X backend. Different 
>>> backends
>>> can be specified using the ~/.matplotlib/matplotlibrc file. More details
>>> regarding backends can be found in the matplotlib FAQ:
>>> 
>>> 
>>> 
>>> The main.log contains:
>>> 
>>> :info:configure -- Looking for pthread.h
>>> :info:configure -- Looking for pthread.h - found
>>> :info:configure -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
>>> :info:configure -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
>>> :info:configure -- Found Threads: TRUE
>>> :info:configure CMake Error at 
>>> /opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
>>> (message):
>>> :info:configure   Could NOT find Boost (missing: signals) (found version 
>>> "1.71.0")
>>> :info:configure Call Stack (most recent call first):
>>> :info:configure   
>>> /opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
>>> (_FPHSA_FAILURE_MESSAGE)
>>> :info:configure   /opt/local/share/cmake-3.15/Modules/FindBoost.cmake:2161 
>>> (find_package_handle_standard_args)
>>> :info:configure   CMakeLists.txt:596 (find_package)
>>> :info:configure -- Configuring incomplete, errors occurred!
>>> :info:configure See also 
>>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cad_freecad/freecad/work/build/CMakeFiles/CMakeOutput.log".
>>> :info:configure See also "/opt/local/var/macports/bui:info:configure -- 
>>> Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
>>> :info:configure -- Found Threads: TRUE
>>&g

Freecad ports ends in error

[Christoph Kukulies]

I was trying to build FreeCAD under macports and at the end I’m getting this:

--->  Verifying checksums for freecad   
--->  Extracting freecad
--->  Applying patches to freecad
--->  Configuring freecad
Error: Failed to configure freecad: configure failure: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cad_freecad/freecad/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port freecad failed
--->  Some of the ports you installed have notes:
  OpenBLAS has the following notes:
This version is built based on a base architecture for convenience, 
which may not be optimized for your system. To build a version 
customized for your machine, use the +native variant
  eigen3 has the following notes:
This product includes software developed by the University of Chicago, as
Operator of Argonne National Laboratory.
  py27-cython has the following notes:
To make the Python 2.7 version of Cython the one that is run when you
execute the commands without a version suffix, e.g. 'cython', run:

port select --set cython cython27
  py27-matplotlib has the following notes:
The default backend is the interactive Mac OS X backend. Different backends
can be specified using the ~/.matplotlib/matplotlibrc file. More details
regarding backends can be found in the matplotlib FAQ:



The main.log contains:

:info:configure -- Looking for pthread.h
:info:configure -- Looking for pthread.h - found
:info:configure -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
:info:configure -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
:info:configure -- Found Threads: TRUE
:info:configure CMake Error at 
/opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
(message):
:info:configure   Could NOT find Boost (missing: signals) (found version 
"1.71.0")
:info:configure Call Stack (most recent call first):
:info:configure   
/opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
:info:configure   /opt/local/share/cmake-3.15/Modules/FindBoost.cmake:2161 
(find_package_handle_standard_args)
:info:configure   CMakeLists.txt:596 (find_package)
:info:configure -- Configuring incomplete, errors occurred!
:info:configure See also 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cad_freecad/freecad/work/build/CMakeFiles/CMakeOutput.log".
:info:configure See also "/opt/local/var/macports/bui:info:configure -- 
Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
:info:configure -- Found Threads: TRUE
:info:configure CMake Error at 
/opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 
(message):
:info:configure   Could NOT find Boost (missing: signals) (found version 
"1.71.0")
:info:configure Call Stack (most recent call first):
:info:configure   
/opt/local/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
:info:configure   /opt/local/share/cmake-3.15/Modules/FindBoost.cmake:2161 
(find_package_handle_standard_args)
:info:configure   CMakeLists.txt:596 (find_package)
:info:configure -- Configuring incomplete, 
errold/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_cad_freecad/freecad/work/build/CMakeFiles/CMakeError.log".


Is there a way to fix this or ny comments?

—
Christoph

Catalina ante portas - wine, wine-bottler LTSpice

[Christoph Kukulies]

My macOS wants to update (Mojave->Catalina 10.15).

I’ve heard wine emulator based programs will cease working.

Has anyone heard there will be an escape for this situation?

Best regards,

Christoph Kukulies

Re: telnet

[Christoph Kukulies]

> Am 05.07.2019 um 11:26 schrieb Dr M J Carter :
> 
> On Fri, Jul 05, 2019 at 10:56:28AM +0200, Christoph Kukulies wrote:
> 
>> I’m surprised there is no telnet under standard macOS.
> 
> I'm not: it, and FTP, are horribly insecure.  The corresponding
> server-end daemons are (or should be) turned off on most sites in the
> interests of self-defence, and replaced by use of SSH.

I’m aware of this of course.
Nonetheless telnet is a useful tool when it comes to testing an SMTP connection 
or some other port.
Not that I’m missing it for its excellent user friendlyness and intuitive 
commands.


—
Christoph ^]




> 
>> Is there a macport? and if, what’s the package name?
> 
> $ port search telnet
> inetutils @1.9.4_11 (net)
>Inetutils is a collection of common network programs, including ftp, 
> telnet,
>rsh, rlogin, tftp and the corresponding daemons.
> 
> -- 
> Dr Martin J Carter
> Computer System Administrator
> Astrophysics, University of Oxford

telnet

[Christoph Kukulies]

I’m surprised there is no telnet under standard macOS. Is there a macport? and 
if, what’s the package name?

Thank you

—
Christoph

vi copy/paste - maybe a bit OT

[Christoph Kukulies]

I’m asking it here although the vi in macOS surely isn’t a macport but I’m 
asking anyway:

Whenever I copy/paste a file content in vi (started from a Terminal) using 
CMD-A or select-CMD-C to select all to put it elsewhere into a text receiving 
object (like Notes) using CMD-V, I’m getting the whole history of that terminal 
window. Not only the file contents.

That’s confusing once you forget about that fact. You paste the contents, e.g. 
a certificate, into a webbrowser and later you are wondering about all that 
stuff in thet text widget which you didn’t intend to get there.

I understand why it might be correct that CMD-A copies the whole terminal 
window contents, not only the vi-part, but it’s weird anyway.

Is the a way to circumvent this problem?  

—
Christoph

ImageMagick Display command

[Christoph Kukulies]

I ran in a Terminal the ImageMagick command: 

$ display image.jpg

and got:

display: delegate library support not built-in '' (X11) @ 
error/display.c/DisplayImageCommand/1900.


—
Christoph

/usr/bin/locate , maybe OT - but asking anyway

[Christoph Kukulies]

I’m wondering why the /usr/bin/locate command doesn’t find anything that’s 
located in ~/Documents, when ~/Documents is located on iCloud Drive.

Trying to locate (even after a /usr/libexec/locate.updatedb) doesn’ t look in 
iCloud Drive.

—
Christoph

Wine - is it a macport?

[Christoph Kukulies]

I’m running some Windows applications, preferably LTspiceXVII under winebottler 
(the latter requiring Wine).

At present a box pops up sometimes saying that my Wine version isn’t optimized 
for the macOs (mojave in my cease).

Would I have to do it using macPorts or do I get it elsewhere?

—
Christoph

Re: X11 app - unable to open display ""

[Christoph Kukulies]

Just FWIW:

$ port installed xorg-server gv
The following ports are currently installed:
  gv @3.7.4_0 (active)
  xorg-server @1.20.4_0 (active)


—
Christoph

> Am 22.04.2019 um 12:21 schrieb Ryan Schmidt :
> 
> 
> 
> On Apr 19, 2019, at 05:01, Christoph Kukulies wrote:
> 
>> Thanks. That did the job. I can now start the „gv“ (ghostview) port. But it 
>> illbehaves.
>> Some problem with the event queue maybe. Looks like lots ov expose events 
>> are generated.
>> Textfield in the left is flickering and is counting through all papersizes 
>> there are. Then the fileselector box
>> is flickering slowly. Hardly to operate.
>> 
>> Well, the application isn’t attractive anyway compared to what one is used 
>> of gsview64/32.
>> Not that the letter is the cream of GUI programs but it is usable and 
>> practical. Not more, not less.
> 
> Hmm, sorry to hear that. I'm not seeing those problems (on High Sierra), but 
> I am using an older version of xorg-server at least:
> 
> $ port installed xorg-server gv
> The following ports are currently installed:
>  gv @3.7.4_0+universal (active)
>  xorg-server @1.18.4_3+universal (active)
> 
> 

Re: X11 app - unable to open display ""

[Christoph Kukulies]

Thanks. That did the job. I can now start the „gv“ (ghostview) port. But it 
illbehaves.
Some problem with the event queue maybe. Looks like lots ov expose events are 
generated.
Textfield in the left is flickering and is counting through all papersizes 
there are. Then the fileselector box
is flickering slowly. Hardly to operate.

Well, the application isn’t attractive anyway compared to what one is used of 
gsview64/32.
Not that the letter is the cream of GUI programs but it is usable and 
practical. Not more, not less.

—
Christoph


> Am 17.04.2019 um 11:20 schrieb Chris Jones :
> 
> 
> > sudo port install xorg-server
> 
> log out then back in.
> 
> Then you will have one for sure.
> 
> On 17/04/2019 10:15 am, Christoph Kukulies wrote:
>> Fine. How can I figure out about the configuration of my X11 server? Don’t 
>> know whether I have an X11 server at all.
>> port list tells me I have
>> xorg-server@1.20.4 x11/xorg-server
>> among other lots of xorg-stuff.
>> —
>> Christoph
>>> Am 17.04.2019 um 11:09 schrieb Chris Jones >> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>> 
>>> Hi,
>>> 
>>> Your problem is
>>> 
>>> export DISPLAY=:0
>>> xhost +
>>> 
>>> don't do this.
>>> 
>>> Just run gv, and allow your X11 server to automatically tart, which it 
>>> should, if it is correctly configured.
>>> 
>>> Chris
>>> 
>>> On 17/04/2019 10:06 am, Christoph Kukulies wrote:
>>>> I installed the „gv“ port (ghostview). Worked.  I can give gv on the 
>>>> command line (shell prompt).
>>>> But I’m getting:
>>>> Christophs-MBP:~ kuku$ export DISPLAY=:0
>>>> Christophs-MBP:~ kuku$ xhost +
>>>> xhost:  unable to open display ":0"
>>>> Christophs-MBP:~ kuku$ gv
>>>> gv: Unable to open the display.
>>>> Christophs-MBP:~ kuku$
>>>> I thought, X11 apps can run against the macOS desktop server, can’t they?
>>>> Or do I have to run an extra X11-server?
>>>> —
>>>> Christoph

Re: X11 app - unable to open display ""

[Christoph Kukulies]

Fine. How can I figure out about the configuration of my X11 server? Don’t know 
whether I have an X11 server at all.
port list tells me I have 

xorg-server@1.20.4 x11/xorg-server

among other lots of xorg-stuff.
—
Christoph


> Am 17.04.2019 um 11:09 schrieb Chris Jones :
> 
> Hi,
> 
> Your problem is
> 
> export DISPLAY=:0
> xhost +
> 
> don't do this.
> 
> Just run gv, and allow your X11 server to automatically tart, which it 
> should, if it is correctly configured.
> 
> Chris
> 
> On 17/04/2019 10:06 am, Christoph Kukulies wrote:
>> I installed the „gv“ port (ghostview). Worked.  I can give gv on the command 
>> line (shell prompt).
>> But I’m getting:
>> Christophs-MBP:~ kuku$ export DISPLAY=:0
>> Christophs-MBP:~ kuku$ xhost +
>> xhost:  unable to open display ":0"
>> Christophs-MBP:~ kuku$ gv
>> gv: Unable to open the display.
>> Christophs-MBP:~ kuku$
>> I thought, X11 apps can run against the macOS desktop server, can’t they?
>> Or do I have to run an extra X11-server?
>> —
>> Christoph

X11 app - unable to open display ""

[Christoph Kukulies]

I installed the „gv“ port (ghostview). Worked.  I can give gv on the command 
line (shell prompt).
But I’m getting:

Christophs-MBP:~ kuku$ export DISPLAY=:0
Christophs-MBP:~ kuku$ xhost +
xhost:  unable to open display ":0"
Christophs-MBP:~ kuku$ gv
gv: Unable to open the display.
Christophs-MBP:~ kuku$ 

I thought, X11 apps can run against the macOS desktop server, can’t they?
Or do I have to run an extra X11-server?

—
Christoph

ghostview gsview gsview32

[Christoph Kukulies]

A question: does macports supply something like gsview? Under Windows I’m using 
still the very useful 
PS viewer (ghostscript) gsview32.exe (Version 5.0).

Has this version or another similarly well usable version been ported to macOS 
(macports)?

Thank you.


Christoph

Re: A general philosophical question about MacPorts

[Christoph Kukulies]

> Am 20.02.2019 um 14:50 schrieb S. L. Garwood via macports-users 
> :
> 
> A big thank you to all the people who chimed in and gave me much to think 
> over.
> I have used MacPorts since 10.6.8 - it is based on one of my favorite package 
> managers (FreeBSD ports)
> I’ve been a long time FreeBSD user, fan, and booster (since 386-bsd believe 
> it or not).

OT:


Yeah, 386bsd , Bill Jolitz.

and his mantra lying in this verse:

…

I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I—
I took the one less traveled by,
And that has made all the difference.

(The Road Not Taken - Robert Frost)


—
Christoph

Also a long time FreeBSD user.
> I think for now I’ll keep using MacPorts (in spite of not having boost-1.68) 
> and move off of Linux to a FreeBSD VM for *nix needs.
> I am NOT a big fan of systemd so FreeBSD is a no brainer.
> Again thanks to all for your comments and suggestions.
> 
>> On Feb 20, 2019, at 8:14 AM, Mojca Miklavec  wrote:
>> 
>> On Tue, 19 Feb 2019 at 14:13, S. L. Garwood via macports-users wrote:
>>> 
>>> So my philosophical question is “Why MacPorts these days?”.
>> 
>> If your question is: "Why a package manager for Mac these days", just
>> a few numbers.
>> 
>> We don't have any good analytics data, but our competitor saw more
>> than 6 million installs (not counting those who opted out) of the most
>> popular package in the last year. This at least tells you that there
>> is interest in people using a native package manager. I know that our
>> traffic runs in many terrabytes, but I forgot even the sample numbers.
>> 
>> If you don't care about running your software natively, it's better to
>> switch to Linux and forget about the expensive hardware.
>> 
>> I would have left macOS if I didn't have a package manager available,
>> the computer would be next-to-useless.
>> Even if the software is not packaged (yet), it is orders of magnitude
>> easier to build it for Mac than without the package manager.
>> 
>> Mojca
>> 
>> 
>> Mojca
> 

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

I got it working (port install ola) finally by following the latest suggestion 
in the port output (deactivate py27-protobuf)
Looking forward to what else might be broken after this :-(
At least port install ola went through now.

Thanks again,

Christoph



> Am 13.01.2019 um 09:58 schrieb Christoph Kukulies :
> 
> I did as you suggested: sudo port deactivate protobuf-cpp
> which worked
> 
> Christophs-MacBook-Pro: kuku$ sudo port deactivate protobuf-cpp
> Note: It is not recommended to uninstall/deactivate a port that has 
> dependents as it breaks the dependents.
> The following ports will break: py27-protobuf @2.6.1_2
> Continue? [y/N]: y
> Warning: Deactivate forced.  Proceeding despite dependencies.
> --->  Deactivating protobuf-cpp @2.6.1_0
> --->  Cleaning protobuf-cpp
> Christophs-MacBook-Pro:
> 
> 
> Then I’m getting:
> 
> Christophs-MacBook-Pro: kuku$ sudo port install ola
> --->  Computing dependencies for ola
> The following dependencies will be installed: 
>  automake
>  libftdi0
>  liblo
>  libtool
>  libusb-compat
>  protobuf3-cpp
>  py27-protobuf3
> Continue? [Y/n]: 
> --->  Fetching archive for automake
> Warning: Your DNS servers incorrectly claim to know the address of 
> nonexistent hosts. This may cause checksum mismatches for some ports. See 
> this page for more information: 
> <https://trac.macports.org/wiki/MisbehavingServers 
> <https://trac.macports.org/wiki/MisbehavingServers>>
> --->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2 from 
> https://packages.macports.org/automake 
> <https://packages.macports.org/automake>
> --->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2.rmd160 from 
> https://packages.macports.org/automake 
> <https://packages.macports.org/automake>
> --->  Installing automake @1.16.1_0
> --->  Activating automake @1.16.1_0
> --->  Cleaning automake
> --->  Fetching archive for libusb-compat
> --->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libusb-compat 
> <https://packages.macports.org/libusb-compat>
> --->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2.rmd160 
> from https://packages.macports.org/libusb-compat 
> <https://packages.macports.org/libusb-compat>
> --->  Installing libusb-compat @0.1.5_0
> --->  Activating libusb-compat @0.1.5_0
> --->  Cleaning libusb-compat
> --->  Fetching archive for libftdi0
> --->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libftdi0 
> <https://packages.macports.org/libftdi0>
> --->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libftdi0 
> <https://packages.macports.org/libftdi0>
> --->  Installing libftdi0 @0.20_1
> --->  Activating libftdi0 @0.20_1
> --->  Cleaning libftdi0
> --->  Fetching archive for liblo
> --->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/liblo <https://packages.macports.org/liblo>
> --->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/liblo <https://packages.macports.org/liblo>
> --->  Installing liblo @0.28_0
> --->  Activating liblo @0.28_0
> --->  Cleaning liblo
> --->  Fetching archive for libtool
> --->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libtool <https://packages.macports.org/libtool>
> --->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libtool <https://packages.macports.org/libtool>
> --->  Installing libtool @2.4.6_5
> --->  Activating libtool @2.4.6_5
> --->  Cleaning libtool
> --->  Fetching archive for protobuf3-cpp
> --->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/protobuf3-cpp 
> <https://packages.macports.org/protobuf3-cpp>
> --->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
> from https://packages.macports.org/protobuf3-cpp 
> <https://packages.macports.org/protobuf3-cpp>
> --->  Installing protobuf3-cpp @3.6.1_0
> --->  Activating protobuf3-cpp @3.6.1_0
> --->  Cleaning protobuf3-cpp
> --->  Fetching archive for py27-protobuf3
> --->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/py27-protobuf3 
> <https://packages.macports.org/py27-protobuf3>
> --->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2.

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

I did as you suggested: sudo port deactivate protobuf-cpp
which worked

Christophs-MacBook-Pro: kuku$ sudo port deactivate protobuf-cpp
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break: py27-protobuf @2.6.1_2
Continue? [y/N]: y
Warning: Deactivate forced.  Proceeding despite dependencies.
--->  Deactivating protobuf-cpp @2.6.1_0
--->  Cleaning protobuf-cpp
Christophs-MacBook-Pro:


Then I’m getting:

Christophs-MacBook-Pro: kuku$ sudo port install ola
--->  Computing dependencies for ola
The following dependencies will be installed: 
 automake
 libftdi0
 liblo
 libtool
 libusb-compat
 protobuf3-cpp
 py27-protobuf3
Continue? [Y/n]: 
--->  Fetching archive for automake
Warning: Your DNS servers incorrectly claim to know the address of nonexistent 
hosts. This may cause checksum mismatches for some ports. See this page for 
more information: <https://trac.macports.org/wiki/MisbehavingServers>
--->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2 from 
https://packages.macports.org/automake
--->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2.rmd160 from 
https://packages.macports.org/automake
--->  Installing automake @1.16.1_0
--->  Activating automake @1.16.1_0
--->  Cleaning automake
--->  Fetching archive for libusb-compat
--->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libusb-compat
--->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/libusb-compat
--->  Installing libusb-compat @0.1.5_0
--->  Activating libusb-compat @0.1.5_0
--->  Cleaning libusb-compat
--->  Fetching archive for libftdi0
--->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libftdi0
--->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/libftdi0
--->  Installing libftdi0 @0.20_1
--->  Activating libftdi0 @0.20_1
--->  Cleaning libftdi0
--->  Fetching archive for liblo
--->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/liblo
--->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/liblo
--->  Installing liblo @0.28_0
--->  Activating liblo @0.28_0
--->  Cleaning liblo
--->  Fetching archive for libtool
--->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libtool
--->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/libtool
--->  Installing libtool @2.4.6_5
--->  Activating libtool @2.4.6_5
--->  Cleaning libtool
--->  Fetching archive for protobuf3-cpp
--->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/protobuf3-cpp
--->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/protobuf3-cpp
--->  Installing protobuf3-cpp @3.6.1_0
--->  Activating protobuf3-cpp @3.6.1_0
--->  Cleaning protobuf3-cpp
--->  Fetching archive for py27-protobuf3
--->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/py27-protobuf3
--->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/py27-protobuf3
--->  Installing py27-protobuf3 @3.6.1_0
--->  Activating py27-protobuf3 @3.6.1_0
Error: Failed to activate py27-protobuf3: Image error: 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/google/protobuf/__init__.py
 is being used by the active py27-protobuf port.  Please deactivate this port 
first, or use 'port -f activate py27-protobuf3' to force the activation.
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-protobuf3/py27-protobuf3/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port ola failed
Christophs-MacBook-Pro: kuku$ 


> Am 12.01.2019 um 19:09 schrieb Mojca Miklavec :
> 
> On Sat, 12 Jan 2019 at 17:45, Christoph Kukulies wrote:
>> 
>> Finally I tried:
>> 
>> Christophs-MBP:ola kuku$ sudo port install ola
>> Password:
>> --->  Computing dependencies for ola
>> Error: Can't install protobuf3-cpp because conflicting ports are active: 
>> protobuf-cpp
> 
> That's most likely the result of the manual installation of that port
> when you followed the installation instructions:
> 
># not asking you to repeat this!
>sudo port install pkgconfig cppunit protobuf-cpp libmicrohttpd
> libusb py27-

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

Thanks, Mojca

actually I just want to install the ola port.

Unfortunately I used brew and port install intermixed which is probably not a 
good idea.

Can I get rid of all (undo) I did with brew (homebrew) and repeat that using 
macports?

That would require to obtain a list of what I did using homebrew and redo that 
using macports :-(

—
Christoph


> Am 12.01.2019 um 17:44 schrieb Mojca Miklavec :
> 
> Dear Christoph
> 
> On Sat, 12 Jan 2019 at 17:12, Christoph Kukulies wrote:
>> 
>> Following the steps in
>> 
>> https://www.openlighting.org/ola/mac-install/
> 
> Do you just want to use the port or did you want to help with the
> development of that port?
> 
> It seems that we have the latest version of the software already
> packaged in MacPorts, so unless that's broken (you should let us know
> if it is), by far the easiest way to install it would be via
> 
>sudo port install ola
> 
> and this is probably also what the official documentation should
> suggest trying first.
> 
> 
> I'll try to answer some of the other questions nonetheless:
> 
>> I’m stumbling across some hurdles:
>> 
>> first off: they ask me to install py27-protobuf
>> 
>> and in the next step I should do a python —version and should install the 
>> pyXX-protobuf fitting my python version.
> 
> That's probably a slightly unfortunate wording. What I suspect the
> author meant was that if you happened to have python2.6 installed by
> default (instructions might be of an older date), you would install
> py26-protobuf INSTEAD OF py27-protobuf. Note that python2.6 should no
> longer be used anyway.
> 
> In your case you probably did
>sudo port select python python36
> which gives the python version that's likely too new for ola (I didn't
> check if it supports python 3; the version in MacPorts uses python 2.7
> in any case).
> 
> (Or, reading further from your latest reply, it's more likely that you
> installed python3 via Homebrew? What does "which python" return? If
> you are mixing HomeBrew and MacPorts, you should at least try to
> remove one from the path to make sure that you don't end up with half
> of the binaries from one manager and the other half from another.)
> 
> You could set the environment to use python 2.7 by default (and then
> switch back) with
>sudo port select python python27
> or you can use
>/opt/local/bin/python2.7
> direction when needed.
> 
>> But python —version gives 3.6.7 with me here. I don’t want tp spoil my 
>> python environment, so I did nothing about it.
>> 
>> Then comes the actual reason of my question:
>> 
>> I did a git clone of the project and then I’m instructed to do a
>> 
>> autoreconf -i
>> 
>> but there is no autoreconf.
> 
> It comes with
>sudo port install autoconf
> 
> Mojca

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

Finally I tried:

Christophs-MBP:ola kuku$ sudo port install ola
Password:
--->  Computing dependencies for ola
Error: Can't install protobuf3-cpp because conflicting ports are active: 
protobuf-cpp
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port ola failed
Christophs-MBP:ola kuku$ 
Christophs-MBP:ola kuku$ 



> Am 12.01.2019 um 17:38 schrieb Christoph Kukulies :
> 
> And after a 
> 
> sudo port install autoconf 
> 
> I’m getting 
> 
>  autoreconf -i
> Can't exec "aclocal": No such file or directory at 
> /usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 326.
> autoreconf: failed to run aclocal: No such file or directory
> 
> 
> 
>> Am 12.01.2019 um 17:12 schrieb Christoph Kukulies > <mailto:k...@kukulies.org>>:
>> 
>> Following the steps in
>> 
>> https://www.openlighting.org/ola/mac-install/ 
>> <https://www.openlighting.org/ola/mac-install/>
>> 
>> 
>> I’m stumbling across some hurdles:
>> 
>> first off: they ask me to install py27-protobuf
>> 
>> and in the next step I should do a python —version and should install the 
>> pyXX-protobuf fitting my python version.
>> But python —version gives 3.6.7 with me here. I don’t want tp spoil my 
>> python environment, so I did nothing about it.
>> 
>> Then comes the actual reason of my question:
>> 
>> I did a git clone of the project and then I’m instructed to do a
>> 
>> autoreconf -i
>> 
>> but there is no autoreconf.
>> 
>> Doing a
>> 
>> Christophs-MBP:ola kuku$ locate autoreconf
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch
>>  
>> <http://rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch>
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch
>>  
>> <http://rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch>
>> Christophs-MBP:ola kuku$ 
>> 
>> I’m clueless at this point.
>> 
>> —
>> Christoph
>> 
> 

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

And after a 

sudo port install autoconf 

I’m getting 

 autoreconf -i
Can't exec "aclocal": No such file or directory at 
/usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory



> Am 12.01.2019 um 17:12 schrieb Christoph Kukulies :
> 
> Following the steps in
> 
> https://www.openlighting.org/ola/mac-install/ 
> <https://www.openlighting.org/ola/mac-install/>
> 
> 
> I’m stumbling across some hurdles:
> 
> first off: they ask me to install py27-protobuf
> 
> and in the next step I should do a python —version and should install the 
> pyXX-protobuf fitting my python version.
> But python —version gives 3.6.7 with me here. I don’t want tp spoil my python 
> environment, so I did nothing about it.
> 
> Then comes the actual reason of my question:
> 
> I did a git clone of the project and then I’m instructed to do a
> 
> autoreconf -i
> 
> but there is no autoreconf.
> 
> Doing a
> 
> Christophs-MBP:ola kuku$ locate autoreconf
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch
>  
> <http://rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch>
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch
>  
> <http://rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch>
> Christophs-MBP:ola kuku$ 
> 
> I’m clueless at this point.
> 
> —
> Christoph
> 

Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

Following the steps in

https://www.openlighting.org/ola/mac-install/ 



I’m stumbling across some hurdles:

first off: they ask me to install py27-protobuf

and in the next step I should do a python —version and should install the 
pyXX-protobuf fitting my python version.
But python —version gives 3.6.7 with me here. I don’t want tp spoil my python 
environment, so I did nothing about it.

Then comes the actual reason of my question:

I did a git clone of the project and then I’m instructed to do a

autoreconf -i

but there is no autoreconf.

Doing a

Christophs-MBP:ola kuku$ locate autoreconf
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch
Christophs-MBP:ola kuku$ 

I’m clueless at this point.

—
Christoph

Re: Bringing a package under the hood of Xcode - maybe OT ?

[Christoph Kukulies]

Thanks for the Xcode env below. I solved it straight forward by copying the 
handful of C programs and header files into my Xcode project 
and let Xcode compile them. Though I didn’t get a dynamic library that way, I’m 
able to incorporate it into the app.

What the consequences for LGPL use are is another story. Don’t know yet. Don’t 
know how to distribute iPhone Apps together with LGPL libs anyway yet.


And excuses for being OT again.

—
Christoph


> Am 12.01.2019 um 00:05 schrieb Andrew Udvare :
> 
> 
> 
>> On 2019-01-11, at 16:27, Ryan Schmidt  wrote:
>> 
>> To cross-compile for iOS, you would presumably need to tell the build system 
>> what architecture(s) to build for and what SDK to use. Often, that can be 
>> done by adding the right -arch flags to the CFLAGS, CXXFLAGS, OBJCFLAGS, 
>> OBJCXXFLAGS, and LDFLAGS environment variables, and adding the right 
>> -syslibroot flag (pointing to the iOS SDK you want to use) to the CFLAGS, 
>> CXXFLAGS, OBJCFLAGS, and OBJCXXFLAGS variables, and adding the right 
>> -Wl,-syslibroot, flag (pointing to the right iOS SDK) to the LDFLAGS.
> 
> On current macOS and Xcode, this is done like so:
> 
> env CC=clang CFLAGS='-isysroot 
> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk
>  -target arm-apple-darwin -arch arm64' ./configure 
> --build=x86_64-apple-darwin --host=arm-apple-darwin
> make
> 
> You'll see the dylib file has aarch64 architecture:
> 
> $ file ./artnet/.libs/libartnet.1.dylib
> ./artnet/.libs/libartnet.1.dylib: Mach-O 64-bit arm64 dynamically linked 
> shared library, flags:<|DYLDLINK|NO_REEXPORTED_DYLIBS>
> 
> But this only builds a library (dylib) and on iOS you don't directly load 
> libraries. With the given output from libarinet, if you want it as a separate 
> library, you have to make a framework and bundle that with your app (allowed 
> since iOS 8).
> 
> Any binaries compiled this way will only work on a jailbroken due to lack of 
> code signing.
> 
> --
> Andrew

Bringing a package under the hood of Xcode - maybe OT ?

[Christoph Kukulies]

I have a downloaded a library (open source) - libartnet to be more precise. 
It’s a typical UNIX package with configure and Makefile. It compiled smoothly 
(./configure ; make ) as I tried out on macOS mojave x64 architecture.

I would like to port this to the iPhone architecture. How could I achieve this? 
Is there a way to cross compile it under macOS?

How does one import such large packages to Xcode. Pointers or links welcome as 
well.


—
Christoph

Re: uninstall residues (MacPorts others) in Launcher

[Christoph Kukulies]

> Am 21.12.2018 um 12:01 schrieb Ryan Schmidt :
> 
> 
> 
> On Dec 21, 2018, at 03:43, Christoph Kukulies wrote:
> 
>> I have had this before. uninstall Gimp left residues which seem to prevent 
>> installing Gimp from Gimp.org.
> 
> I'm not sure how installing anything with MacPorts could prevent you from 
> installing something outside of MacPorts... What problem are you experiencing 
> when installing Gimp from Gimp.org?
> 

When opening the Gimp Icon in the installer DMG, it started to „check“ the 
application (whatever it does, maybe the integrity or some checksum, dunno)
but this check hung and hung and didn’t end.

>> Recently I built macports Gimp 2.10.8 with quartz, but it turned out that 
>> this version had issues. Came up with dark theme, drawing white lines on 
>> black background, as simple as mit may sound, seemed to be broken.
> 
> Hmm, not sure what's going on. If you're on Mojave, I recall some other 
> reports of graphics issues in some ports on Mojave. I don't recall what the 
> status of getting that resolved is.

I had other applications, not from macports, LTspiceXVII, that had issues in 
dark theme. Namely, white characters on white background in an item. listbox. 
Switching mojave to daylight theme healed it.

The problems with Gimp seemed to have some resemblance with this. Although I 
must say that the „official“ download for macOS on gimp.org <http://gimp.org/> 
also comes up in that kind of dark mode. Seems to be en vogue these days. 
Energy saving? Imaging how many KWh and thus CO2 you can save in the world when 
every window background color is dark grey instead of white :)

> 
>> Anyway, I did another uninstall Gimp but now I have again (or still, can’t 
>> even tell)
>> in my launcher page a directory, named "MacPorts (andere)“ (others), with 
>> files "IDLE" and "Python Launcher“ in it.
>> 
>> I mislaid the email in which some kind person from this list already pointed 
>> me to the recipe to get totally rid of that, so my plea is: please could 
>> someone give me that link again.
> 
> I don't know why Python's "IDLE" might remain in the Launcher, but several 
> users have reported it before, such as in this ticket:
> 
> https://trac.macports.org/ticket/52160
> 


Thanks. Reading this ticket helped in so far that I just x'd the two files (in 
„dangling“ mode) in that Macports folder and them and the folder went away.


Problem seems gone.

—
Christoph