Summary: | udev-079-r1 compilation fails under distcc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bob <custom_basses> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | lisa |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bob
2006-01-29 14:46:01 UTC
Try without these CFLAGS -fweb -frename-registers -fforce-addr -fomit-frame-pointer -ftracer -fweb Constructs webs as commonly used for register allocation purposes and assign each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover. It can, however, make debugging impossible, since variables will no longer stay in a ``home register''. -frename-registers Attempt to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimiza- tion will most benefit processors with lots of registers. It can, however, make debugging impossible, since variables will no longer stay in a ``home register''. -fomit-frame-pointer Don't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions. It also makes debugging impossible on some machines. On some machines, such as the VAX, this flag has no effect, because the standard calling sequence automatically handles the frame pointer and nothing is saved by pretending it doesn't exist. The machine-description macro "FRAME_POINTER_REQUIRED" controls whether a target machine supports this flag. Yes, with the "default" cflags, this works just fine for me. Closing, as this looks like user error... |