Summary: | app-text/pdftk-1.41-r1 fails when CFLAGS contain flags not understood by gcj | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Printing Team <printing> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | andreas, gentoo, java, lilwyrm, mlspamcb, xmw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log from app-text/pdftk-1.44
emerge --info =app-text/pdftk-1.44 complete environment from failed pdftk-1.44 build Patch against the pdftk ebuild to rectify the issue |
Description
Diego Elio Pettenò (RETIRED)
2009-01-10 20:07:24 UTC
I believe that I am experiencing a related error in the latest version, app-text/pdftk-1.44. Build log and environment to be attached momentarily. Created attachment 298663 [details]
Build log from app-text/pdftk-1.44
Created attachment 298665 [details]
emerge --info =app-text/pdftk-1.44
Created attachment 298667 [details]
complete environment from failed pdftk-1.44 build
The build log shows several errors with the complaint, "gcjh: unrecognized option '-m64'". The option '-m64' does not appear in the `emerge --info` dump, but it is in the environment. I was able to work around this problem by creating /etc/portage/env/pdftk.conf with the contents CFLAGS_amd64="" and then adding app-text/pdftk pdftk.conf to /etc/portage/package.env. With that in place, pdftk-1.44 successfully compiles. I confirm workaround from comment 5 works! pdftk broke (i think after removing gcc:4.4??), revdep-rebuild didn't found it. But it cannot be rebuild without this env trick. 1.44 is stable in the portage tree, so it may affect many people with amd64 config i guess. Same here on amd64 I run paludis and to get like comment 5 i quick and dirty edited my /etc/paludis/bashrc to add export CFLAGS="" export CFLAGS_amd64="" Then i could compile and install pdftk Created attachment 303201 [details, diff]
Patch against the pdftk ebuild to rectify the issue
I believe the gcj should not honour CFLAGS. They're CFLAGS and not JFLAGS. As a quickfix to pdftk however, the attached patch removes the CFLAGS_amd64 altogether from the environment.
I explicitly did not copy the flag filter code from flag-o-matic, as amd64 is set on a profile basis to a single value which is the one causing the problem, see `grep -r m64 /usr/portage/profiles`. I could not imagine any other flags specific to the amd64 architecture that'd need to go in there on a profile basis.
For those users who need a machine reproducible workaround, CFLAGS_amd64 can also be assigned an empty value for this package by executing the following two commands:
mkdir -p /etc/portage/env/app-text
echo 'CFLAGS_amd64=""' >> /etc/portage/env/app-text/pdftk
Please test if this still affects pdftk-1.45 On my system, pdftk-1.45 successfully builds without any environment workarounds to remove CFLAGS_amd64="-m64" . It also successfully builds with blatantly useless flags (tested with CFLAGS_amd64="-my_bologna_has_a_first_name" ). If it makes a difference, I am using gcc 4.6.3 now. 1.x has been dropped from the tree. Please reopen, if it occurs with 2.02. |