[Bug 133] setting CFLAGS usually breaks inlined
[email protected] Sun, 10 Jul 2005 20:50:24 -0400
| Newsgroups | gmane.comp.java.vm.sablevm.bugs |
|---|---|
| Message-ID | <[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=133 ------- Additional Comments From [email protected] 2005-07-10 20:50 ------- ./configure set -O2 by default if no CFLAGS specified - so SableVM behave correctly with default flags... Yes, always adding -finline or adding -O2 could avoid some breakage if the user modified the CFLAGS but I don't think they are really solutions. We might want to print a warning if user passes its own CFLAGS to ./configure. About the -I options, this is a C preprocessor option, no? Then it should be specified with CPPFLAGS and not CFLAGS. About: "gentoo deals with this very same problem by stripping unsafe flags from a user's CFLAGS." The actual Gentoo way about that is to remove flags: - that are part of -O2 and that breaks the build since -O2 is considered conservative - when devs get too many bug reports related to flags used then some devs will remove them but they don't really have to do it. So the Gentoo way is to do nothing about SableVM. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are the QA contact for the bug, or are watching the QA contact.