Re: pltcl crash on recent macOS

2022-06-23 Thread Peter Eisentraut
On 20.06.22 12:36, Peter Eisentraut wrote: On 14.06.22 05:05, Tom Lane wrote: I'd be okay with just dropping the -lc from pl/tcl/Makefile and seeing what the buildfarm says.  The fact that we needed it in 1998 doesn't mean that we still need it on supported versions of Tcl; nor was it ever any

Re: pltcl crash on recent macOS

2022-06-20 Thread Peter Eisentraut
On 14.06.22 05:05, Tom Lane wrote: I'd be okay with just dropping the -lc from pl/tcl/Makefile and seeing what the buildfarm says. The fact that we needed it in 1998 doesn't mean that we still need it on supported versions of Tcl; nor was it ever anything but a hack for us to be overriding what

Re: pltcl crash on recent macOS

2022-06-14 Thread Peter Eisentraut
On 13.06.22 23:32, Thomas Munro wrote: Hrmph, I changed my CC to "ccache gcc-mp-11" (what MacPorts calls GCC 11), and I still can't reproduce the problem. I still get "(from executable)". In your original quote you showed "gcc", not "gcc-11", which (assuming it is found as /usr/bin/gcc) is just

Re: pltcl crash on recent macOS

2022-06-13 Thread Tom Lane
Peter Eisentraut writes: > Switching the order of -bundle_loader and -lc did not help. Meh. Well, it was worth a try. I'd be okay with just dropping the -lc from pl/tcl/Makefile and seeing what the buildfarm says. The fact that we needed it in 1998 doesn't mean that we still need it on support

Re: pltcl crash on recent macOS

2022-06-13 Thread Thomas Munro
On Tue, Jun 14, 2022 at 8:21 AM Peter Eisentraut wrote: > The difference is that I use CC=gcc-11. I have change to CC=cc, then it > works (nm output shows "from executable"). So it's gcc that gets thrown > off by the -lc. Hrmph, I changed my CC to "ccache gcc-mp-11" (what MacPorts calls GCC 11)

Re: pltcl crash on recent macOS

2022-06-13 Thread Peter Eisentraut
On 13.06.22 18:01, Tom Lane wrote: Having said that, I wonder whether the position of the -bundle_loader switch in the command line is relevant to which way the hash_search reference is resolved. Seems like we could put it in front of the various -l options if that'd help. Switching the order

Re: pltcl crash on recent macOS

2022-06-13 Thread Tom Lane
Peter Eisentraut writes: > The difference is that I use CC=gcc-11. I have change to CC=cc, then it > works (nm output shows "from executable"). So it's gcc that gets thrown > off by the -lc. Hah, that makes sense. So does changing the option order help? regards, tom

Re: pltcl crash on recent macOS

2022-06-13 Thread Peter Eisentraut
On 13.06.22 13:27, Thomas Munro wrote: On Mon, Jun 13, 2022 at 6:53 PM Peter Eisentraut wrote: frame #1: 0x7ff803a28751 libsystem_c.dylib`hash_search + 215 frame #2: 0x000110357700 pltcl.so`compile_pltcl_function(fn_oid=16418, tgreloid=0, Hmm, I can’t reproduce that…. alt

Re: pltcl crash on recent macOS

2022-06-13 Thread Tom Lane
Thomas Munro writes: > On Mon, Jun 13, 2022 at 6:53 PM Peter Eisentraut > wrote: >> frame #1: 0x7ff803a28751 libsystem_c.dylib`hash_search + 215 >> frame #2: 0x000110357700 >> pltcl.so`compile_pltcl_function(fn_oid=16418, tgreloid=0, > Hmm, I can’t reproduce that…. I can't either, altho

Re: pltcl crash on recent macOS

2022-06-13 Thread Thomas Munro
On Mon, Jun 13, 2022 at 6:53 PM Peter Eisentraut wrote: > frame #1: 0x7ff803a28751 libsystem_c.dylib`hash_search + 215 > frame #2: 0x000110357700 > pltcl.so`compile_pltcl_function(fn_oid=16418, tgreloid=0, Hmm, I can’t reproduce that…. although that symbol is present in my libS