Summary: | media-libs/gst-plugins-0.6.1 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Claes Mogren <cm> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Claes Mogren
2003-05-19 13:12:58 UTC
does this happen always at the same point ? gstreamer doesn't react very well to optimizations in general. Just did an 'emerge -u gst-plugins' again to test, and it failed at the exact same place as my two earlier attempts. (row 202 in ..-0.6.1/gst/mpeg1enc/chendct.c) Any ideas what flags I shouldn't use? I'll try a simple "-02 -pipe" Hmm.. with CFLAGS="-O2 -pipe" the compiling went just fine. Thanks for the hint foser. But still, why is it so sensitive to optimizations? Everything else I've tried has compiled with no problems at all. Can the ebuild limit the allowed flags somehow? Wonder wich one that caused it to fail in the first place the ebuild already limits useflags heavily and i think that should do in most cases. But such things can be very compiler version dependant. So far i have no other reports, so i think we don't have to cap it even more. Even when it compiles with heavy flags useage it often shows unstable behaviour in the past resulting in a lot of useless bugreports to the gstreamer folks. We just hope that users now are more aware of the fact that optimisations are the first place to look when things go wrong. As to why it is gst that is so sensetive, i'm not sure. I always blame the fact that it's pretty ingenious code pushing the edges of what's possible with maybe a little too few developers to get it rock stable currently. But it's on the right track, seeing from where it started. |