Summary: | [fPIC] media-sound/lastfmplayer-1.1.3 relocation error during build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jose daLuz <jdaluz> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bug.hunter, den_m, kevin.bowling, matrixhax0r |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
suggested new ebuild
suggested patch for new ebuild |
Description
Jose daLuz
2007-02-12 00:57:41 UTC
Hey David, my young friend ... this is your call ;) Please try the following attachments (ebuild + patch) and report back! Created attachment 109919 [details]
suggested new ebuild
Created attachment 109921 [details, diff]
suggested patch for new ebuild
Thanks, the patch works for me! This hack that fixed this was in the patch that was applied to the previous version. I told upstream about it, but it looks like they haven't fixed it. David ... apparently upstream is ignoring your interventions: Should we make more noise? Stefan ... in the time being I would suggest that you take out the `~amd64' flag for new builds, ie make an appropiate entry in `package.mask' with a call to test it on our arch: What do you think? Not so fast, guys. There's no need to mask the package, because it's fixed already. Huh? -> ... suggest that you take out the `~amd64' flag for *new* builds ... i suggest that the maintainer just keeps the existing patch as long as the issue exists. really no reason to drop keywords because of a known issue Again ... David (aka our `upstream-struggler') should speak here: This mess is drifting from a `known issue' to a state of `bad habit' ... but you sound reasonable, thank you Simon! Btw, thus you have closed this bug I hope that you are on your way to make the appropriate commitment to our portage-tree ;) Well, I just told upstream about this bug. Hopefully they'll get around to fixing this. *** Bug 166626 has been marked as a duplicate of this bug. *** |