Re: gnulib fails for build on Mac OS X 10.4: get_ppid_of.c:36:22: error: libproc.h: No such file or directory

2021-12-13 Thread Evan Miller
I'm sorry I missed out on this discussion but the patch below is problematic. proc_pidinfo is a system function not available on 10.4. When compiling with the 10.5 SDK and deploying to 10.4, a run-time link error will result on 10.4 using the patch. Generally, it is preferable to use MAX_ALLOWE

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-23 Thread Evan Miller
> On Aug 17, 2021, at 22:04, Evan Miller wrote: > > >> On Aug 17, 2021, at 18:53, Paul Eggert wrote: >> >> On 8/17/21 1:02 PM, Evan Miller wrote: >> >>> Thanks for the patch. At present, the non-libsigsegv implementation does >>> n

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-23 Thread Evan Miller
> On Aug 23, 2021, at 05:49, Bruno Haible wrote: > > That's what I suspected, for the reasons mentioned in [1]. > > Now, to check that with libsigsegv it works fine: > > make distclean > > ./configure CPPFLAGS=-Wall --with-libsigsegv > --with-libsigsegv-prefix=/opt/local > (use the prefi

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-22 Thread Evan Miller
> On Aug 22, 2021, at 21:15, Bruno Haible wrote: > > You can ignore this error — which merely indicates that the POSIX threads on > macOS 10.4 are incomplete and gnulib does not work around this particular > issue — and comment out the test-pthread and test-pthread-rwlock from the > gltests/Mak

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-22 Thread Evan Miller
> On Aug 22, 2021, at 16:42, Paul Eggert wrote: > > On 8/22/21 4:19 AM, Evan Miller wrote: >> c-stack.c: In function 'die': >> c-stack.c:106:17: warning: implicit declaration of function 'mempcpy' >> [-Wimplicit-function-declaration] >>

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-22 Thread Evan Miller
> On Aug 21, 2021, at 19:46, Bruno Haible wrote: > > Run these commands: > > ./gnulib-tool --create-testdir --dir=testdir1 --single-configure c-stack > cd testdir1 > ./configure > make > make check > > If they fail, then you do need the libsigsegv library. FWIW the first step fails pro

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-17 Thread Evan Miller
> On Aug 17, 2021, at 18:53, Paul Eggert wrote: > > On 8/17/21 1:02 PM, Evan Miller wrote: > >> Thanks for the patch. At present, the non-libsigsegv implementation does not >> compile on this machine for reasons described in >> https://trac.macports.org/tick

Re: bug#50098: Configuring --with-libsigsegv results in link error

2021-08-17 Thread Evan Miller
> On Aug 17, 2021, at 15:12, Paul Eggert wrote: > > On 8/17/21 11:06 AM, Evan Miller wrote: >> Using grep 3.7 (as well as master), I'm seeing undefined symbol errors after >> pointing the build to use a local installation of libsigsegv (version 2.13). > > T