Summary: | sys-devel/distcc-3.1-r4: with e.g. portage-2.2_rc75 or 2.1.9, symlinks get installed into the wrong place | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Christian Franke <nobody-gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cluster, DummyUnit, matsuu |
Priority: | High | Keywords: | InVCS, REGRESSION |
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925 | ||
Attachments: |
build output
Workaround to build build distcc with >=portage-2.1.9 |
Description
Christian Franke
2010-09-08 11:57:45 UTC
Created attachment 246448 [details]
build output
I have the same issue on my amd64 box - symlinks are installed into root directory. Should i post a new bug for it? (In reply to comment #2) > I have the same issue on my amd64 box - symlinks are installed into root > directory. Should i post a new bug for it? > It seems that it is bug in portage-2.1.9.2. A DCCC_PATH variable setted at beginning of ebuild are not seen in src_install() and it also missing in /var/tmp/portage/sys-devel/distcc-3.1-r4/build-info/environment.bz2 I found that this strange behavior caused by underscore in variable name. So I deleted underscores from variable names in ebuild (see following patch) and distcc was emerged correctly: symlinks was on their right place: /usr/lib64/distcc/bin P.S. Downgrading to stable portage-2.1.8.3 also fixes this issue. Created attachment 246706 [details, diff]
Workaround to build build distcc with >=portage-2.1.9
> I found that this strange behavior caused by underscore in variable name. This is wrong. DCCC_PATH is explicitly filtered by portage, underscore doesn't matter. Commit introduced this bug: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2da227e57f695dc173b22802443084c5fec539b0 I was lead to believe this was an ARM problem by a stupid mistake of mine. I updated the summary to be more appropriate. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c8d1bcd28c29802dc2bc1f7ac9d6df475ff4700d This is fixed in 2.1.9.6 and 2.2_rc82. |