Re: gentoo ebuild question
"Kevin S. Clarke" <[email protected]>
| Newsgroups | gmane.comp.java.vm.sablevm.general |
|---|---|
| Message-ID | <[email protected]> |
> Before modifying the am-wrapper, did you try > re-emerging: automake-wrapper > I have version 1 and it is in the script. I just modified it (wasn't sure its package and didn't take the time to look), but looking at "emerge -s automake-wrapper" now it says I have version 1 too. Next step... doing: "emerge automake-wrapper |grep am-wrapper" indicates the official wrapper is: /usr/lib/misc/am-wrapper.sh (looking at that file says it is a modification of the Mandrake file: am-wrapper.pl -- which is what my system was using earlier today). Ah, okay, I see... after my remerge of automake wrapper (just now) automake is linked to the .sh version, but before (in what also claimed to be version 1 (? -- I'm not positive of the timeline)) it was linked to the .pl version. I'll search gentoo's bugzilla to see if I can learn anything. At least it is working now, I guess, and pointing to the right script. > yes, it is possible to remove -O3 in the ebuilds, some package does it. > I am not sure what is Gentoo policy about this, since -O3 might be > considered an agressive optimization flag? I will have to inform myself > on that side. I think the policy is do what you want, but if you change the flags you are responsible (basically, "here is the rope"). Since I know lots of people experiment with them, if it is possible to check for what might be problematic settings, it would be nice (of course, if someone changes it they should be able to realize it needs to be changed back too I guess). Anyway, thanks again for the ebuild... now off to experiment...