Author bapt
Recipients bapt, dstufft, eric.araujo
Date 2018-01-19.13:15:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516367732.86.0.467229070634.issue32597@psf.upfronthosting.co.za>
In-reply-to
Content
When building modules and trying to set the proper linker flags for the library runtime path, the detection of the compiler is wrong. the issue: 
https://bugs.python.org/issue20767 was showing the issue and imho badly fixed.

Clang behave like gcc regarding how it passes flags to the linker: -Wl,... so clang and gcc should be treated exactly the same way and no specific code should be added for FreeBSD

Here https://github.com/python/cpython/blob/master/Lib/distutils/unixccompiler.py#L237, it should accept both clang and gcc,

This block https://github.com/python/cpython/blob/master/Lib/distutils/unixccompiler.py#L230 should be removed

The issue is not only on FreeBSD but on any system which compiler is clang. side note, the detection of gcc looks at first glance wrong, as on many system gcc is installed as cc sometime.
History
Date User Action Args
2018-01-19 13:15:32baptsetrecipients: + bapt, eric.araujo, dstufft
2018-01-19 13:15:32baptsetmessageid: <1516367732.86.0.467229070634.issue32597@psf.upfronthosting.co.za>
2018-01-19 13:15:32baptlinkissue32597 messages
2018-01-19 13:15:32baptcreate