Summary: | distcc path should respect EPREFIX | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Benda Xu <heroxbd> |
Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | prefix |
Priority: | Normal | Keywords: | InVCS, PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 315803 | ||
Attachments: |
portage-2.2.28-distcc-eprefix.patch
portage-2.3.0-scanelf-path.patch |
Description
Benda Xu
2016-05-12 04:55:51 UTC
Created attachment 434030 [details, diff]
portage-2.2.28-distcc-eprefix.patch
Ping portage team. Ping portage team. (In reply to Benda Xu from comment #1) > Created attachment 434030 [details, diff] [details, diff] > portage-2.2.28-distcc-eprefix.patch Actually, mysettings["EPREFIX"] is wrong when dealing with "cross-prefix" situations. So, portage.const.EPREFIX is the right thing to use here (like bug 583754). (In reply to Zac Medico from comment #4) > (In reply to Benda Xu from comment #1) > > Created attachment 434030 [details, diff] [details, diff] [details, diff] > > portage-2.2.28-distcc-eprefix.patch > > Actually, mysettings["EPREFIX"] is wrong when dealing with "cross-prefix" > situations. So, portage.const.EPREFIX is the right thing to use here (like > bug 583754). Nice catch Zac! I just realized it a minute ago. Created attachment 436632 [details, diff]
portage-2.3.0-scanelf-path.patch
Updated, thanks!
Thanks, this is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=67239a3f48989794ffe484206bc6afc40156d9db Included in 2.3.0 release. |