[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Ned Deily added the comment: See also Issue31354, Issue35351, and Issue35257. -- versions: +Python 3.6 ___ Python tracker ___ ___

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Ned Deily added the comment: New changeset f83ee476d48dbeb90ddf3526b04936a49a87973a by Ned Deily (stratakis) in branch '3.6': bpo-28015: Support LTO build with clang (GH-9908) (GH-10922) https://github.com/python/cpython/commit/f83ee476d48dbeb90ddf3526b04936a49a87973a -- nosy:

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by Charalampos Stratakis : -- pull_requests: +10161 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by Charalampos Stratakis : -- pull_requests: +10161, 10162, 10163 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by Charalampos Stratakis : -- pull_requests: +10161, 10162 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Charalampos Stratakis added the comment: The workaround indeed works. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Benjamin Peterson added the comment: Probably that's fine, but can #31625 be easily worked around by, e.g., using make AR=llvm-ar RANLIB=llvm-ranlib? -- nosy: +benjamin.peterson ___ Python tracker

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Charalampos Stratakis added the comment: The issue with the 3.6 branch is https://bugs.python.org/issue31625 which hasn't been backported to 3.6. Would it make sense to backport it? I have the backports ready locally but not sure if pushing https://bugs.python.org/issue31625 to 3.6 is

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

STINNER Victor added the comment: The issue has been fixed in Python 3.7 and master. If someone is volunteer to backport it to older version, please go ahead :-) But according to serge-sans-paille, it's non trivial and I'm not sure that it's worth it. Sorry, usually we focus on the master

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

miss-islington added the comment: New changeset 69a3f153a92fd8c86080e8da477ee50df18fc0d1 by Miss Islington (bot) in branch '3.7': bpo-28015: Support LTO build with clang (GH-9908) https://github.com/python/cpython/commit/69a3f153a92fd8c86080e8da477ee50df18fc0d1 -- nosy:

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by miss-islington : -- pull_requests: +9417, 9418 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by miss-islington : -- pull_requests: +9417 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

STINNER Victor added the comment: New changeset 5ad36f9b21a3aa3b2265b1b43d73522cc3322df2 by Victor Stinner (serge-sans-paille) in branch 'master': bpo-28015: Support LTO build with clang (GH-9908) https://github.com/python/cpython/commit/5ad36f9b21a3aa3b2265b1b43d73522cc3322df2 --

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

STINNER Victor added the comment: I confirm that it's currently broken. Test on Fedora 28, clang version 6.0.1 (tags/RELEASE_601/final): $ ./configure --with-pydebug CC=clang --with-lto && make (...) checking for x64 gcc inline assembler... yes checking whether float word ordering is

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

serge-sans-paille added the comment: Looks like a package dependency issue: installing ``llvm-dev`` package should fix the problem. Or in that particular case ``llvm-3.8-dev``. -- nosy: +serge-sans-paille ___ Python tracker

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

Change by Roundup Robot : -- keywords: +patch pull_requests: +9267 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue28015] configure --with-lto builds fail when CC=clang on Linux, requires gold linker

New submission from Gregory P. Smith: The error message you will see when building may look something like: clang -pthread -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fprofile-instr-generate -flto Parser/acceler.o Parser/grammar1.o Parser/listnode.o Parser/node.o Parser/parser.o