| Summary: | sci-electronics/alliance-5.0.20060329 failed - incompatible type for argument 2 of `chktab' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Leo <leosgb> |
| Component: | New packages | Assignee: | Denis Dupeyron (RETIRED) <calchan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | sci |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Leo
2006-05-24 21:59:27 UTC
Hi Leo, The package compiles fine here on a P4. Could you please recompile with CFLAGS="-O2 ...." rather than "-O3" and report back? Thanks, Markus Sure, will try it again tonight and post the results here. Thanks. Hi, I am sorry my make.conf has -03 as default. How can I change it for this package only (or should I change it for all my packages)? Is there any reason for it not accept 03 optimization? Thanks! (In reply to comment #3) > I am sorry my make.conf has -03 as default. How can I change it for this > package only (or should I change it for all my packages)? Is there any reason > for it not accept 03 optimization? If it's only to try a different set of CFLAGS when building a certain package, all you need is pass them at the command line when you emerge the package. In your case you would do this : CFLAGS="-O2 -march=pentium-m -pipe" CXXFLAGS="-O2 -march=pentium-m -pipe" emerge alliance (the above command is all on the same line) And to answer your second question, yes, some packages don't like some of the more aggressive optimizations, and we can filter them in ebuilds when necessary. Note 1. Specifying '-march=pentium-m' implies '-mtune=pentium-m', so you really don't need the -mtune option in your CFLAGS. Note 2. Your emerge info shows CXXFLAGS="", which is... hum... stupid ;o) You may want to fix that and set CXXFLAGS="${CFLAGS}" in your /etc/make.conf Note 3. You have set the status of this bug to 'RESOLVED FIXED'. Does this mean you have tried with -O2 and that it worked, or did you change the status by mistake ? I reopen the bug until this is clarified. Denis. Thanks! No it did work with -02. I am making all the suggested changes right now. Thank you again and sorry for all this confusion. (In reply to comment #5) > Thanks! No it did work with -02. I am making all the suggested changes right > now. Thank you again and sorry for all this confusion. OK, but you shouldn't close the bug. We do so once the problem is fixed. And in this case, the problem is not you using -O3, but alliance not building with -O3. What needs to be done is to replace -O3 by -O2 in the ebuild, so that people like you who use -O3 in their make.conf can still emerge alliance. I will do so after the usual verifications. So, please keep opening bugs, we love them, but let us close them. And thanks for your input, as always. Denis. Oh sorry! I agree with you I dont know why I keep closing it maybe excitement :) Since I closed it when I replied I just reopened the bug, ok? Dont worry about bugs coming I am here to find them! hehehe I am trying to start using Alliance now. Thanks for all your help. Fixed. |
