gh-136677: Introduce executable specific linker flags to configure

[rueteh]

Introduce two new flags EXE_LDFLAGS and PY_CORE_EXE_LDFLAGS to contain executable target specific linker options for building the python interpreter as well as other executables.

• Issue: Introduce seperate LDFLAGS for executable and shared library build targets #136677

Notes

If provided, this effectively means that PY_CORE_LDFLAGS (as well as the chain of flags used by this variable) is exclusively used to build shared libraries / bundles. In addition, any common linker flags applicable to both types of targets would also need to be supplied to EXE_LDFLAGS and LDFLAGS.

---

📚 Documentation preview 📚: https://cpython-previews--137296.org.readthedocs.build/

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[FFY00]

@rueteh thanks for the PR!

It looks alright to me, but perhaps @vstinner could have an extra look before merging 😊

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 FreeBSD Refleaks 3.x (tier-3) has failed when building commit 4e45c9c.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1613/builds/2905) and take a look at the build logs.
4. Check if the failure is related to this commit (4e45c9c) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1613/builds/2905

Test leaking resources:

• test_events: references
• test_events: memory blocks

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/test/support/__init__.py", line 947, in gc_collect
    gc.collect()
    ~~~~~~~~~~^^
ResourceWarning: unclosed <socket.socket fd=10, family=2, type=1, proto=6, laddr=('127.0.0.1', 25902), raddr=('127.0.0.1', 25903)>
Task was destroyed but it is pending!
task: <Task pending name='Task-3624' coro=<BaseSelectorEventLoop._accept_connection2() done, defined at /buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py:217> wait_for=<Future pending cb=[Task.task_wakeup()]>>
Warning -- Unraisable exception
Exception ignored while calling deallocator <function _SelectorTransport.__del__ at 0x8455fcb90>:
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py", line 873, in __del__
    _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
    ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ResourceWarning: unclosed transport <_SelectorSocketTransport closing fd=10>
k


Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/test/support/__init__.py", line 947, in gc_collect
    gc.collect()
    ~~~~~~~~~~^^
ResourceWarning: unclosed <socket.socket fd=9, family=2, type=1, proto=6, laddr=('127.0.0.1', 39196), raddr=('127.0.0.1', 39197)>
Task was destroyed but it is pending!
task: <Task pending name='Task-2445' coro=<BaseSelectorEventLoop._accept_connection2() done, defined at /buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py:217> wait_for=<Future pending cb=[Task.task_wakeup()]>>
Warning -- Unraisable exception
Exception ignored while calling deallocator <function _SelectorTransport.__del__ at 0x840397650>:
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py", line 873, in __del__
    _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
    ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ResourceWarning: unclosed transport <_SelectorSocketTransport closing fd=9>
k

[FFY00]

It seems like test_regrtest is failing on the buildbot with ENV_CHANGED. I don't think is related to this, but let's keep an eye on main.

[FFY00]

Seems to be fine.