both the latest perl und wireshark do not declare the minimal-USE flag, yet the latter does not build when that USE flag is set while compiling perl. but I was told that is not a bug. hmm, if I tell such a story to my boss, I have to worry for my job. than I was told, I am not allowed to set such a USE-flag, without further explanations why. now I wonder which USE flags are allowed to be set in /etc/make.conf and what is the meaning of that file, if it should not be used for setting USE-flags globally !! so I should reemerge perl so the code of the wireshark ebuild works. makes no sense to me. than I tried to understand the ebuild from wireshark and it its "notdependency" to the minimal USE-flag. the reason for this is bug with number 119208. looking up that bug I find a resolved bug about 'wolfgl doesn't compile with GCC4'. such code is not understandable for an outsider like me. so it is really difficult get a step into the project. I also made the effort to browse through ebuild docu and write up a little patch. it is not a big deal, I can keep the fixed ebuild in my overlay-portage. but I think to keep a system robust and stable. and instead of writing this I should write 3 more reports on ebuilds don't compile with gcc4. so here the reference to the patch bug = 146655
There's no minimal flag in latest stable perl, already told you. *** This bug has been marked as a duplicate of 146655 ***
Needs to be reopened and the ebuild fixed.
The ebuild needs to be fixed, see Bug 146655 for related discussion.
Created attachment 96671 [details, diff] wireshark-0.99.3.ebuild.diff I mimicked eutil.eclass to check first whether perl has a minimal USE-flag. tested it against my current setup and it compiled. then putting minimal into the IUSE of perl let the emerge die.
Comment on attachment 96671 [details, diff] wireshark-0.99.3.ebuild.diff We didn't fix the eclass to work around the fix in ebuilds. ;)
Created attachment 96672 [details, diff] wireshark-0.99.3.ebuild.diff Correct fix.
Ok, that works with me as well. but can please give me a hint why you want to have the check "manual" instead of "automated". is it to again the nature of the minimal flag, that you do not know what it concrete means in the future versions of perl ? is that also the reason why the first proposed patch for the eutil.eclass was rejected ? thanx
(In reply to comment #7) You need to ask vapier why my patch was rejected.
I'm also seeing this issue while emerging openldap.
(In reply to comment #9) > I'm also seeing this issue while emerging openldap. Different ebuild and already fixed, emerge --sync.
*** Bug 147315 has been marked as a duplicate of this bug. ***
*** Bug 147339 has been marked as a duplicate of this bug. ***
*** Bug 147359 has been marked as a duplicate of this bug. ***
Fixed wireshark ebuild in CVS
I know this bug is closed but, I wanted to document my findings someplace incase someone else if having issues. Even well after the updated ebuild made it in, I still was getting the error. As it turns out, I had two perl versions installed (5.6.1-r4, 5.8.8-r2). Unmerging 5.6.1-r4 allowed wireshark to work.
(In reply to comment #10) > (In reply to comment #9) > > I'm also seeing this issue while emerging openldap. > > Different ebuild and already fixed, emerge --sync. > > I just did emerge --sync, emerged portage and got the same error again with openldap. Which version is it fixed? I am not using the -minimal flag either and never have so I dont understand why this is an issue.
