Re: lowdown not helped by snowleopardfixes

The fix: https://trac.macports.org/ticket/55878

Re: lowdown not helped by snowleopardfixes

On 2018-02-21, at 11:31 AM, Jan Stary wrote: > Hm, doesn't the PortGroup add its stuff to LDFLAGS and LDADD > (and whatever else) _after_ the port has done its configure? not usually. eg. this portgroup adds: configure.ldflags-append -lsnowleopardfixes > I am probably missing something

Re: lowdown not helped by snowleopardfixes

On Feb 21 08:46:21, ken.cunningham.web...@gmail.com wrote: > lowdown uses it's own completely unique methods for configure It's a hand written ./configure shell script, as opposed to the auto* hell. https://github.com/kristapsdz/oconfigure Some other portable projects do the same. > and library

Re: lowdown not helped by snowleopardfixes

lowdown uses it's own completely unique methods for configure and library function replacements, I see. It clears out the LDFLAGS during the build, ergo the -lsnowleopardfixes not being honoured it also replaces some functions on it's own, so there might be collisions if -lsnowleopardfixes

Re: lowdown not helped by snowleopardfixes

I'll take a look. The PG adds -lsnowleopardfixes to the ldflags, but thats not showing up in your build for some reason. For some ports, you have to add the flag a different way, via a patch or similar... K > On Feb 21, 2018, at 05:40, Jan Stary wrote: > > Hi Ken, > > when I

lowdown not helped by snowleopardfixes

Hi Ken, when I created the textproc/lowdown port not long ago https://github.com/macports/macports-ports/pull/1241 you kindly advised me to use PortGroup snowleopard_fixes 1.0 so that older MacOS sysem without e.g. strndup(3) can still compile lowdown. However, it seems that the