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

2025-04-28 Thread Bruno Haible via Gnulib discussion list
Hi Evan, Sorry for the long delay. > Attached is a proposed patch to fix the compilation issue, designed by > comparing the 10.4 and 10.5 SDKs. It relies on an implementation detail, but > I think it's safe to say that the PowerPC headers are frozen at this point. Looks good. I've verified that

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 >>> not compile on this machine for reasons described in >>> http

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-23 Thread Bruno Haible
Evan Miller wrote: > At last, the "sigsegv" stackoverflow tests fail: > > ../build-aux/test-driver: line 112: 12956 Illegal instruction "$@" > >$log_file 2>&1 > FAIL: test-sigsegv-catch-stackoverflow1 > ../build-aux/test-driver: line 112: 12963 Illegal instruction "$@" > >$log_file 2>&1

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 Bruno Haible
Evan Miller wrote: > After updating gnulib master, the "make" step now ends with the error: > > gcc -std=gnu99 -DHAVE_CONFIG_H -DEXEEXT=\"\" -I. -I.. > -DGNULIB_STRICT_CHECKING=1 -DIN_GNULIB_TESTS=1 -I. -I. -I.. -I./.. -I../gllib > -I./../gllib -Wno-error -g -O2 -MT test-pthread.o -MD -MP -MF

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] >>char *p = mempcpy (buf, progname, prognamelen); >

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

2021-08-22 Thread Paul Eggert
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] char *p = mempcpy (buf, progname, prognamelen); Evidently some dependencies were missing from the c-stack module.

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-21 Thread Bruno Haible
Evan Miller wrote: > > Oh, I see you're building for an old system (Mac OSX 10.4.11, circa 2007) > > that Apple itself is no longer supporting. Although we don't normally worry > > about such platforms, perhaps you can come up with a patch that clearly > > won't break mainline platforms. > > A

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

2021-08-21 Thread Bruno Haible
Paul Eggert 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). > > Thanks for reporting that. It's a bug in Gnulib's c-stack module, which > I fixed in Gnulib by installing

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

2021-08-18 Thread Paul Eggert
On 8/17/21 7:04 PM, Evan Miller wrote: ./configure LDFLAGS='-L/opt/local/lib' LIBS='-lsigsegv' That workaround is what I was looking for, and will let MacPorts fix its package without waiting for a new Grep release. Thanks. I'm closing the grep bug report as we have a c-stack fix installe

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/ticket/63381 > > Oh, I see you're buil

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

2021-08-17 Thread Paul Eggert
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/ticket/63381 Oh, I see you're building for an old system (Mac OSX 10.4.11, circa 2007) that Apple it

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). > > Thanks for reporting that. It's a bug

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

2021-08-17 Thread Paul Eggert
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). Thanks for reporting that. It's a bug in Gnulib's c-stack module, which I fixed in Gnulib by instal