Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 621002 - dev-python/bsddb3: not building "error: unrecognized command line option ‘-R’; did you mean ‘-R’?"
Summary: dev-python/bsddb3: not building "error: unrecognized command line option ‘-R’...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-06 11:16 UTC by Nado
Modified: 2018-06-15 18:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log for 6.1.1 (build.log,9.02 KB, text/plain)
2017-06-06 11:18 UTC, Nado
Details
build.log for 6.2.4 (build.log,9.02 KB, text/plain)
2017-06-06 11:18 UTC, Nado
Details
emerge --info (emergeinfo,16.52 KB, text/plain)
2017-06-06 11:26 UTC, Nado
Details
emerge --info from a system building bsddb3 successfully (file_621002.txt,5.07 KB, text/plain)
2017-06-06 11:30 UTC, Nado
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nado 2017-06-06 11:16:55 UTC
I can’t build dev-python/bsddb3 in src_compile phase, this is true for both versions in the tree (6.1.1 and 6.2.4).

Reproducible: Always




I had as python_targets the 2.7 and 3.4 versions enabled.
Comment 1 Nado 2017-06-06 11:18:11 UTC
Created attachment 475338 [details]
build.log for 6.1.1
Comment 2 Nado 2017-06-06 11:18:52 UTC
Created attachment 475340 [details]
build.log for 6.2.4
Comment 3 Nado 2017-06-06 11:26:50 UTC
Created attachment 475342 [details]
emerge --info
Comment 4 Nado 2017-06-06 11:30:15 UTC
Created attachment 475344 [details]
emerge --info from a system building bsddb3 successfully

This output came from a friend which succeeded to build the package without any issue.
Comment 5 Nado 2017-06-06 11:33:42 UTC
Tried with both gcc 6.2 and 6.3, it still fails.
Comment 6 moxian 2017-07-12 21:49:24 UTC
I can reproduce this.

This should be due to python itself being compiled with not-gcc.
Can you try re-emerging dev-lang/python with gcc (`CC=gcc CXX=g++ emerge -av dev-lang/python`), and see if that helps?

That said, it sounds like a python bug. I've filed http://bugs.python.org/msg298248
Comment 7 Nado 2017-08-11 21:11:19 UTC
No, it did not change anything, I emerged python 2 and 3 with CC=gcc CXX=g++ it didnt work.
Comment 8 Nado 2018-06-15 18:43:02 UTC
I finally cleaned my system and got back to a uniform gcc use, and could confirm that by re-emerging python:2.7, python:3.5 and sys-level/db prior to bsddb3, it could be fixed. I can also confirm that one or all of these were directly responsible as I triggered the error again before re-emerging them.

Since clang/gcc mixing are not suggested officially I'll mark this bug as wontfix.