build errors on 10.13 due previously default macro now undefined

Previously AssertMacros.h defined this by default. #define __ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES 1 Now it does not. There have been a number of build failures due to this, and we're sure to see more. The immediate fix is to redefine the Macro. Longer term is to move the new na

Re: [MacPorts] HighSierraProblems modified

On Sep 27, 2017, at 13:49, Rainer Müller wrote: > On 2017-09-25 12:00, Rainer Müller wrote: >> On 2017-09-20 17:25, m...@macports.org wrote: >>> Can someone confirm this? >> >> I can confirm that option exists, but I do not know what it actually >> does. There is also a 'xcodebuild -checkFirstLa

Re: Fwd: [MacPorts] HighSierraProblems modified

On 2017-09-25 12:00, Rainer Müller wrote: > On 2017-09-20 17:25, m...@macports.org wrote: >> Can someone confirm this? > > I can confirm that option exists, but I do not know what it actually > does. There is also a 'xcodebuild -checkFirstLaunchStatus' which we > could use to issue the appropriate

Re: Building port from GitHub commit rather than tag

Thanks, not sure how I missed that ... > On 27 Sep 2017, at 7:34 pm, Ryan Schmidt wrote: > > > On Sep 27, 2017, at 13:14, Christopher Jones wrote: > >> I am trying to update a port, where I need to use a GitHub commit ID rather >> than a tag to pick up a fix committed after the release for Xc

Re: [macports-ports] 02/02: dict: update to 1.12.1 (and take maintainership)

On 2017-09-27 20:18, Ryan Schmidt wrote: Most projects on SourceForge organize their files in folders. If dict is such a project, then you should specify here which folder the file is in, to avoid redirects. See https://trac.macports.org/wiki/howto/AvoidRedirects Assuming LIBTOOL is the file

Re: Building port from GitHub commit rather than tag

On Sep 27, 2017, at 13:14, Christopher Jones wrote: > I am trying to update a port, where I need to use a GitHub commit ID rather > than a tag to pick up a fix committed after the release for Xcode 9 support. > > I have done this in the past with code like > > # Use git commit to work around X

Re: [macports-ports] 02/02: dict: update to 1.12.1 (and take maintainership)

> On Sep 27, 2017, at 08:13, Leonardo Brondani Schenkel > wrote: > > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/4d93c582d25ea637a6e1b0eb24cb07fadeed99a5 > > commit 4d93c582d25ea637a6e1b0eb24cb07fad

Re: [macports-ports] 01/02: libmaa: new port

On 2017-09-27 20:06, Ryan Schmidt wrote: On Sep 27, 2017, at 08:13, Leonardo Brondani Schenkel wrote: Zero King (l2dy) pushed a commit to branch master in repository macports-ports. https://github.com/macports/macports-ports/commit/62b48a961c07cb4d6236e3b4bd8f411e857b1428 commit 62b48a961

Building port from GitHub commit rather than tag

Hi, I am trying to update a port, where I need to use a GitHub commit ID rather than a tag to pick up a fix committed after the release for Xcode 9 support. I have done this in the past with code like # Use git commit to work around Xcode 9 issue github.setuproot-mirror root 07c9d8d023a

Re: [macports-ports] 01/02: libmaa: new port

> On Sep 27, 2017, at 08:13, Leonardo Brondani Schenkel > wrote: > > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/62b48a961c07cb4d6236e3b4bd8f411e857b1428 > > commit 62b48a961c07cb4d6236e3b4bd8f411e8

Re: [macports-ports] branch master updated: ghc and ghc-bootstrap: specify compiler to clang-4.0

> On Sep 27, 2017, at 12:21, Ken Cunningham > wrote: > > > On 2017-09-27, at 6:20 AM, Ryan Schmidt wrote: >> >> MacPorts automatically adds a build dependency on the compiler it uses, if >> that compiler comes from MacPorts and if that dependency has not already >> been added, so having alr

Re: [macports-ports] branch master updated: mosh: allow build with systems < 10.7

> > This doesn't build on Lion: > > https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/43805 > Noted. I was "sure" 10.7 had that capability, but it clearly doesn't at least on this build. I'll move the system test up to 10.8, once I verify that 10.8 built it. Thanks,

Re: [macports-ports] branch master updated: ghc and ghc-bootstrap: specify compiler to clang-4.0

On 2017-09-27, at 6:20 AM, Ryan Schmidt wrote: > > MacPorts automatically adds a build dependency on the compiler it uses, if > that compiler comes from MacPorts and if that dependency has not already been > added, so having already specified the compiler whitelist you don't then also > need t

Re: Fix Sierra Trac query

On 27/09/17 15:58, Chris Jones wrote: On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has both sierra an

Re: Fix Sierra Trac query

On 27/09/17 15:58, Chris Jones wrote: On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has both sierra an

Re: Fix Sierra Trac query

On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has both sierra and highsierra as keywords... Hmmm... Ma

Re: Fix Sierra Trac query

On 2017-09-27 16:12, Chris Jones wrote: > [[TicketQuery(component=ports&status!=closed&keywords~=sierra > -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has both sierra and highsierra as keywords... Looks like Trac does not support the match operator w

Re: [macports-ports] branch master updated: ghc and ghc-bootstrap: specify compiler to clang-4.0

On Sep 26, 2017, at 14:11, Ken wrote: > Ken (kencu) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/b6060617db664a7ca586df1d8894da2054f7db75 > > The following commit(s) were added to refs/heads/master by this push: > >

Re: MacPorts for macOS High Sierra

On Sep 27, 2017, at 02:23, Robert W. Glatzl wrote: > Is there a schedule for releasing MacPorts for macOS High Sierra? I think the schedule is that Josh will build the package installer within a week. I've just set up the High Sierra buildbot worker, which is now starting to build binaries. I

Re: MacPorts for macOS High Sierra

On 2017-09-27 09:23, Robert W. Glatzl wrote: > Hi MacPort folks! > > Is there a schedule for releasing MacPorts for macOS High Sierra? You can already use MacPorts on High Sierra, there is just no signed .pkg installer yet. Install from source: https://guide.macports.org/#installing.macports.sou

Re: [macports-ports] branch master updated: mosh: allow build with systems < 10.7

> On Sep 26, 2017, at 19:00, Ken wrote: > > Ken (kencu) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5aaf07f3a5a380ad25bbf09b0e883509a91d > > The following commit(s) were added to refs/heads/master by this push: >

MacPorts for macOS High Sierra

Hi MacPort folks! Is there a schedule for releasing MacPorts for macOS High Sierra? -- Robert W. Glatzl robert.gla...@gmx.net

Re: buildbot fetch of ghc fails on 10.8 or less due to SSL error

On Sep 26, 2017, at 14:56, Ken Cunningham wrote: > I have not seen this one here at home when installing ghc-bootstrap or ghc, > but I presume it's due to the older SSL in MacPorts causing trouble: > >