Ciaran McCreesh wrote:
On Thu, 29 Jan 2009 22:25:58 -0500
Richard Freeman <[email protected]> wrote:
Ciaran McCreesh wrote:
This looks a lot like your compiler being wonky. What does paludis
--info paludis say?
Yup - I agree. Take note that effective CFLAGS are at the bottom of
the listing (I have a case statement in my /etc/paludis/bashrc that
uses conservative settings for problematic packages).
The error occurs with both sets of CFLAGS.
Does it occur with a sensible set of CFLAGS?
Apparently it builds with -O2 only. Why -Os and -frename-registers and
-fweb would cause problems isn't obvious to me - those are pretty safe
settings 99% of the time (actually, the full list of CFLAGS works 99% of
the time for that matter). If paludis doesn't build with anything other
than -O2 perhaps it would make sense to filter the flags in the ebuild?
Those reduced flags are pretty common for amd64.
I do realize that the output suggests that this is a compiler bug of
some sort (again, nothing in those flags would be something likely to
cause problems unless you wrote self-modifying code or something crazy
like that). I can live with it... :)
_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user
