[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Alexandre Vassalotti : -- resolution: -> duplicate status: open -> closed superseder: -> GCC detection for runtime_library_dirs when ccache is used ___ Python tracker ___

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Tarek Ziadé : -- versions: -Python 2.6, Python 3.0 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Akira Kitada : -- nosy: +tarek type: compile error -> behavior versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker ___

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Sean Reifschneider: -- assignee: -> loewis nosy: +loewis priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Martin v. Löwis: -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Alexandre Vassalotti added the comment: > The patch is incorrect since find returns -1 on failure. Oops, that is right. I attached the corrected patch. __ Tracker <[EMAIL PROTECTED]> __Index: Lib/

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Seo Sanghyeon added the comment: The patch is incorrect since find returns -1 on failure. This is also a duplicate of #1254718. -- nosy: +sanxiyn __ Tracker <[EMAIL PROTECTED]> __

[issue1032] Improve the hackish runtime_library_dirs support for gcc

Changes by Alexandre Vassalotti: __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/option

[issue1032] Improve the hackish runtime_library_dirs support for gcc

New submission from Alexandre Vassalotti: In distutils.unixccompiler, there is a hack to passing correctly the -R option to gcc (and a few other compilers). However, there is a small bug that causes gcc to not be detected correctly if the compiler name does not start with "gcc" (e.g., "i486-li