On Mar 15, 2025, at 07:58, Álvaro Herrera wrote:
> It's make. From its info manual:
Oh, that explains it. It hadn’t occurred to me that make could eval strings
passed to it like that, but of course it does.
>
> I'm surprised that you don't need \$\$ though. I wonder if
> make CFLAGS='-Wl,-r
On 2025-Mar-14, David E. Wheeler wrote:
> But, just. WAT. 30 years in this business and shell string escaping
> continues to elude me. I tried lots of different combinations of
> escaping, but this weird double-$ never occurred to me.
It's make. From its info manual:
6.1 Basics of Variable Ref
On Mar 14, 2025, at 17:13, Laurenz Albe wrote:
> It is a quoting issue.
>
> Trial and error showed my that the following works:
>
> make CFLAGS='-Wl,-rpath,\$$ORIGIN'
>
> ... at least when I run it on the shell. Putting it into an RPM spec file
> might require more escaping, no idea.
Confir
On Fri, 2025-03-14 at 12:58 -0400, David E. Wheeler wrote:
> I'm trying to compile an extension with PG_CFLAGS1[1]:
>
> ```sh
> make PG_CFLAGS='-Wl,-rpath,$ORIGIN'
> ```
>
> This works, but for some reason the rpath value is truncated:
>
> ```console
> # chrpath -l src/semver.so
> src/semver.so:
