Re: app PortGroup enhancements, and request for someone to test with +quartz variant for a few gtk apps

On 2018-03-22, at 8:24 AM, Kenneth F. Cunningham wrote: > 2. an option to hide the sometimes forever bouncing dock icon > > options app.hide_dock_icon > default app.hide_dock_icon no > > > For the +x11 versions, you would want both of these options to be "ye

Re: Error writing data to TLS socket: The specified session has been invalidated for some reason.

On 2019-01-27, at 10:33 AM, Ryan Schmidt wrote: > On Jan 27, 2019, at 06:24, Marius Schamschula wrote: > >> On Jan 26, 2019, at 9:03 PM, Ken Cunningham wrote: >> >>> Running the test suite on gnutls on 10.6.8 shows one failure: >>> >>> FAIL: srp >> >> For gnutls 3.6.6 the test suite runs cle

obsolete PG

Dear friends, Apparently I have used the obsolete PG incorrectly. I'm sorry about that -- first time I used it. I hope I have fixed things up correctly now. Best, Ken

Re: implementation of configure.env-append

On 2019-10-09, at 1:28 PM, Ryan Schmidt wrote: > do whatever additional work is necessary to communicate that variable to the > build system, e.g. by using `build.args-append LDFLAGS="${configure.ldflags} > [get_canonical_archflags ld]"` or whatever. > Perhaps I'll try a new approach to thi

Re: Pick up SDKROOT as the sysroot fallback.

> Chris, > FYI, this has already been committed upstream. > > https://gcc.gnu.org/ml/gcc-cvs/2019-10/msg00148.html > > Jack Yes, this plan is coming along nicely -- some of us know how this came to pass :> I sent that link to Josh a while back when it came out, as support for passin

Re: Index Broken on 10.5

Leopard Intel can run clang-7.0, and nothing newer at present. When I get time, I will probably fix newer clangs. See for my suggestions on how to run Leopard Intel successfully on macports at present. Ken

Re: installing MacPorts 2.6.2 on Ubuntu Linux 20.04

You could be correct. For some years, Portfile authours have been asked to always account for the fact that MacPorts was designed to be cross-platform, and to take steps to make sure the Portfiles remain so. That's all the "platform darwin" stuff in all the Portfiles and in base. I was just cu

python 3.8 config not returning all libs?

Trying to debug an upgrade to libpeas to use python38, it was failing to link libpython3.8 into the build. Something strange happening in the python config: $ python3.8-config --libs -ldl -framework CoreFoundation $ python3.7-config --libs -lpython3.7m -ldl -framework CoreFoundation Ken

cxx11 1.1 port group / -stdlib=macports-libstc++ may not be setting up paths correctly for i386 builds

Yeah, well this one may well be NTBF, but I thought I would mention it. During a recent buildbot build of Pingus using the cxx11 1.1 PortGroup on i386, the build fails with an error suggesting that when building with clang-4.0 against libstdc++ from libgcc6, in i386 mode, the proper flavour head

Re: [macports-ports] branch master updated: snowleopardfixes: new port to deal with missing functions in Snow Leopard

On 2017-07-21, at 4:21 AM, Ryan Schmidt wrote: > "variant universal {}" declares that a universal variant should be offered to > the user, and that it requires no additional code as compared to the regular > build. > > "PortGroup muniversal 1.0" defines a universal variant that builds multip

would someone have a moment to trigger a new build of pingus on 10.6.i386.legacy-builder?

so we can see if Marcus' new fixes have repaired this defect? Thanks! Ken

Re: would someone have a moment to trigger a new build of pingus on 10.6.i386.legacy-builder?

excellent -- thanks! K On 2017-07-27, at 8:30 PM, Ryan Schmidt wrote: > On Jul 27, 2017, at 09:22, Kenneth F. Cunningham wrote: > >> so we can see if Marcus' new fixes have repaired this defect? >> >> <https://build.macports.org/builders/ports-10.6_

Re: Add --disable-tls to GCC?

I use gcc6 to compile software needing TLS on systems < 10.9 with success (i.e. the_silver_searcher, others). every time I have tried clang with -femulated-tls it has segfaulted (not many times). K

Re: Possible patch for sox build failure on 10.7

On 2017-08-09, at 1:05 AM, Joshua Root wrote: > Perhaps someone with access to a 10.7 machine could try this. > > - Josh > Yep, that should do it. Deactivating MacPorts grep, sox build fails - activating MacPorts grep fixes the build on 10.7. I have other things installed that get pulled in

Re: Possible patch for sox build failure on 10.7

I can work with you on this. I'll build a failing version and email you the entire log off-list tonight. Ken On 2017-08-09, at 9:55 AM, Jan Stary wrote: > On Aug 09 08:44:02, ken.cunningham.web...@gmail.com wrote: >> >> On 2017-08-09, at 1:05 AM, Joshua Root wrote: >> >>> Perhaps someone with

Re: Changing default cxx_stdlib to libc++

On 2018-03-10, at 3:38 AM, db wrote: > How will I know about the lib change and the availability of binaries? > Besides rebuilding from source from time to time, I only do port sync. I think I"m likely not going to change anything on my LibcxxOnOlderSystems 10.6.8 system for a while, db. It w

Re: Changing default cxx_stdlib to libc++

On 2018-03-10, at 9:06 AM, Kenneth F. Cunningham wrote: > I'll probably keep building against a current lib curl installed via > /opt/bootstrap as well, just 'cause it works. I meant to say I'll keep building MacPorts against a current libcurl... > Best, > > Ken

Re: Changing default cxx_stdlib to libc++

On 2018-03-10, at 12:23 PM, db wrote: > On 10 Mar 2018, at 18:06, "Kenneth F. Cunningham" > wrote: >> I think I"m likely not going to change anything on my LibcxxOnOlderSystems >> 10.6.8 system for a while, db. It will continue to work just as it does now,

a plea to change the default std lib clang adds if none is specified on the build line

1 minute summary, no gobbledygook: When clang sees a build line, if there is no -stdlib=Something specified, it adds -stdlib=libstdc++ on systems up to 10.8, and -stdlib=libc++ on 10.9 and above. If the older OS is set up to use -stdlib=libc++, then all these ports break, and need painful man

Re: a plea to change the default std lib clang adds if none is specified on the build line

On 2018-03-11, at 5:39 PM, Mojca Miklavec wrote: > > This is pretty similar to https://trac.macports.org/ticket/53634 > except that I don't have a patch for that. > > Mojca I think the clang'ers have taken care of that for you. They skipped making the default c++11 and jumped to c++14, though

Re: a plea to change the default std lib clang adds if none is specified on the build line

On 2018-03-11, at 8:07 PM, Kenneth F. Cunningham wrote: > <https://reviews.llvm.org/D40948> > > This is committed to trunk. I'm not sure if this made it into clang-6.0 or > not, but there was a lot of talk about making sure it did. > Must be. That commit was r3202

Re: Changing default cxx_stdlib to libc++

On 2018-03-12, at 3:42 PM, Mojca Miklavec wrote: > On 12 March 2018 at 22:32, Michael wrote: >> On 2018-03-08, at 9:32 AM, Ken Cunningham wrote: >> >>> Thank God. >>> >>> 10.6.8, agree. >> >> So PPC machines will not get this upgrade? > > PPC and libc++ don't particularly like each other. Tr

Re: Changing default cxx_stdlib to libc++

On 2018-03-12, at 4:26 PM, Kenneth F. Cunningham wrote: > > > It _could_ be done in 10.5 Intel, but that makes not much sense. Nobody > should be running 10.5 intel anyway, and if we made the libc++ switch in 10.5 > intel we'd be endlessly trying to figure out if we

Re: Changing default cxx_stdlib to libc++

On 2018-03-12, at 5:21 PM, Michael wrote: > Is there a reason for a universal binary on PPC anymore? > > Anyone running a PPC binary today will either be on a PPC machine (10.5), or > an Intel machine with Rosetta (10.6). > They either want a 10.5 PPC binary, or a 10.6 Intel binary. > > So is

app portgroup bouncing icon weirdness …

I have made some suggestions to the app PortGroup that I think would be helpful, launch via a bash script and fixing up the PATH by default. Ryan has input several excellent suggestions, and I've incorporated those. My goal is to make the app PG so easy to use, you only have to include the PG an

Re: app portgroup bouncing icon weirdness …

On 2018-03-16, at 1:04 PM, Eric Le Lay wrote: > For gPodder +x11 [1], I've added an entry in Info.plist to > prevent an icon in the dock. > With +quartz, it uses the py27-gtk-osx-application library to behave like a > proper Mac app. > > [1] > https://github.com/macports/macports-ports/blob/

Re: app portgroup bouncing icon weirdness …

On 2018-03-16, at 3:47 AM, Ryan Schmidt wrote: > > > Right. The app portgroup is intended for "proper Mac apps". > > https://lists.macports.org/pipermail/macports-dev/2011-August/015788.html > > I notice over the years that the topic of extending the app PortGroup to support gtk/x11 applica

app PortGroup support gtk/x11 apps (was Re: app portgroup bouncing icon weirdness … )

On 2018-03-17, at 11:41 AM, Kenneth F. Cunningham wrote: > With those two things, it seems most of the gtk/x11 apps would launch > reasonably and not have a distracting bouncing icon. A new PR for this enhancement to the app PG is here: <https://github.com/macports/macports-ports/

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-20, at 5:57 PM, Rainer Müller wrote: > Do we have any better way to specify the need for clang >= 3.8? > > If there is no way, we should probably just disable the 64-bit build of wine > for macOS <= 10.8. We are just about to have all these systems (10.6 to 10.8) build everything wi

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-20, at 6:11 PM, Ryan Schmidt wrote: > > There is no timetable for this yet, but it's certainly months from now. > Really? I was really hoping it would be two or three weeks, at most. Too bad. Is there anything I can do to speed this up to help out? The longer we wait, the more

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-20, at 5:57 PM, Rainer Müller wrote: >> -compiler.blacklist-append {clang < 800} >> +compiler.blacklist-append {clang < 800} \ >> +macports-clang-3.3 \ >> +macports-clang-3.4 \ >> +

app PortGroup enhancements, and request for someone to test with +quartz variant for a few gtk apps

Hello, With Ryan's help we've made two enhancements to the app PortGroup 1. an optional bash launch script that doesn't pass -psn, and sets up the PATH prior to launch options app.use_launch_script default app.use_launch_script no 2. an option to hide the sometimes forever bouncing dock icon

Re: Consequences of using MacPorts GCC as a fallback compiler on PowerPC

On 2018-03-22, at 5:11 PM, Ryan Schmidt wrote: > There are already ports out there, and installed on user systems, and > binaries being distributed that were built by our buildbot, that were built > with a MacPorts gcc without -D_GLIBCXX_USE_CXX11_ABI=0 set. These would be > ports that do not

Re: Consequences of using MacPorts GCC as a fallback compiler on PowerPC

On 2018-03-23, at 1:44 AM, Mojca Miklavec wrote: > > Additional question for Ken: if we do (b) and keep using gcc6(?), do > we then even need any special (buildbot) setup for C++11 builds like > we plan to do for libc++-based builders? Once the 10.6 to 10.8 buildbots are configured for libc++ an

Re: Consequences of using MacPorts GCC as a fallback compiler on PowerPC

On 2018-03-23, at 12:02 PM, Mojca Miklavec wrote: > > I still like the convention of marking ports as "requires C++11" much > more than "please blacklist gcc 3.0 and gcc 4.2". > It's elegant, but also opens endless issues about C11 or C14 or C17 or c++17 and brings much confusion, IMHO. On In

Re: ABI 4?

On 2018-03-25, at 10:30 AM, Michael wrote: > Can someone give me a quick description of ABI 4 versus ABI 5? Google gives > me a document about plants. > Caveats: 1. I'm not an expert on this. 2. There are experts who might read this and may shame me. My Understanding: Most of it comes from