mac build

I posted this to mythtv-users, but I wondered in anyone had any interest. The obvious first step is wrapping John's work in a port. - John (Hoyt) did a stellar job getting the macos/ansible build proceess to work and in no way is this critique any

Re: qt5-qtwebengine on macOS 10.13, Xcode version

On Dec 28, 2020, at 23:05, Ken Cunningham wrote: > On Dec 28, 2020, at 3:35 PM, Ryan Schmidt wrote: > >> On Dec 27, 2020, at 10:11, Ken Cunningham wrote: >> >>> However, I would float the idea it's time the buildbot and all 10.13 users >>> moved to Xcode 10. >>> >>> Xcode 10's issues have

Re: qt5-qtwebengine on macOS 10.13, Xcode version

> On Dec 28, 2020, at 3:35 PM, Ryan Schmidt wrote: > > > > On Dec 27, 2020, at 10:11, Ken Cunningham wrote: > >> However, I would float the idea it's time the buildbot and all 10.13 users >> moved to Xcode 10. >> >> Xcode 10's issues have largely been worked around by this point it

Re: How to build a port with a different compiler

Please Reply All so that the conversation stays on the list. On Dec 28, 2020, at 20:04, Tom wrote: > Because nearly no port is building here, I wanted to try a different > compiler. But that is not the problem. > And because of this error: > > Warning: The macOS 11.1 SDK does not appear to be

macOS 11.1 SDK does not appear to be installed

Sorry, if this question has already been answered. I updated my system to Big Sur and followed the MacPorts migration instructions and updated Xcode to version 12.3. However, when I try to build ports in MacPorts, I now get the following warnings. Warning: The macOS 11.1 SDK does not appear

Re: qt5-qtwebengine on macOS 10.13, Xcode version

On Dec 27, 2020, at 10:11, Ken Cunningham wrote: > However, I would float the idea it's time the buildbot and all 10.13 users > moved to Xcode 10. > > Xcode 10's issues have largely been worked around by this point it seems, > although there a couple of stragglers still. I intentionally

Re: macOS symbol/conditional for Makefiles (porting)

On Dec 28, 2020, at 06:12, Christoph Kukulies wrote: > 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

Re: How to build a port with a different compiler (was: Re: macports-users Digest, Vol 172, Issue 20)

On Dec 27, 2020, at 20:06, Tom wrote: > how can I build a port with a MacPorts gcc compiler? > For example gcc9. Normally, ports choose what compiler to use and you should not attempt to override it. Why do you want to?

Re: ARM gdb compilation fails with implicit function declaration error ioctl

Don't forget to Reply All so the conversation stays on the list. On Dec 26, 2020, at 05:06, Christoph Kukulies wrote: > There were times in history where implicit function declarations were not > considered as an error (consulting my book „The C programming language by > Kernighan/Ritchie“ >

Re: macOS symbol/conditional for Makefiles (porting)

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

Re: macOS symbol/conditional for Makefiles (porting)

> Does macOS supply any built-in variable for building that if block? See and similar examples for ways of detecting and branching on the OS in Makefiles. Ken

Re: macOS symbol/conditional for Makefiles (porting)

The following script will show you the predefined symbols. #! /bin/sh EMPTY_FILE="${TMPDIR:-/tmp}/t$$.c" rm -f "${EMPTY_FILE}" touch "${EMPTY_FILE}" clang ${1+"${@}"} -E -dM "${EMPTY_FILE}" rm -f "${EMPTY_FILE}" You can change clang to gcc, or to the full path of either, and it will show you

macOS symbol/conditional for Makefiles (porting)

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 +=

Re: macports-users Digest, Vol 172, Issue 20

Hi Tom On 12/28/20 3:06 AM, Tom wrote: Hi, how can I build a port with a MacPorts gcc compiler? For example gcc9. Regards usually, the only think you need is configure.compiler= e.g: port install configure.compiler=macports-gcc-9 Riccardo