This is an auto-filed bug because dev-python/python-debian fails tests. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: If you need further logs, feel free to ask.
Created attachment 640056 [details] build.log build log and emerge --info
Is this one of these fancy environment that remove 'ar' and entirely miss the fact that 'ar' is an archiver that is not necessarily used in toolchain context?
It should use system AR instead of /usr/bin/ar
(In reply to Agostino Sarubbo from comment #3) > It should use system AR instead of /usr/bin/ar Why?
...and how should it determine what 'system AR' is at runtime?
(In reply to Michał Górny from comment #4) > (In reply to Agostino Sarubbo from comment #3) > > It should use system AR instead of /usr/bin/ar > > Why? To give the users to choose which ar implementation use (In reply to Michał Górny from comment #5) > ...and how should it determine what 'system AR' is at runtime? by using AR variable like other build system are doing
(In reply to Agostino Sarubbo from comment #6) > (In reply to Michał Górny from comment #4) > > (In reply to Agostino Sarubbo from comment #3) > > > It should use system AR instead of /usr/bin/ar > > > > Why? > > To give the users to choose which ar implementation use Are we now going to patch all software away from using 'bzip2' so that users may choose a different bzip2 implementation explicitly? > (In reply to Michał Górny from comment #5) > > ...and how should it determine what 'system AR' is at runtime? > > by using AR variable like other build system are doing How can it use AR variable if it is only defined at build time? It's a program, not a build system.
