21 Jul
2012
21 Jul
'12
1:13 a.m.
On 07/20/2012 04:45 PM, Darrell Anderson wrote:
Yes, damn, that bothers me. Why in the heck would a glibc update cause things to
break (wait... don't answer that...), meaning the SOB should be backwards
compatible unless it follows the same vein as gcc and tightened the
syntax/semantics a bit more. I have an email out on the Arch list as well
regarding build failures with the new glibc and whether the type I'm seeing are
expected.
--
David C. Rankin, J.D.,P.E.
Yes, but what should the contents of a properly built
package contain?
Now you are asking trick questions... Short answer - I'll have to look. If it is
a properly installed package, then you should see this in kcontol:
http://www.3111skyline.com/dl/dt/trinity/ss/kdm_theme.jpg
> Why are
you not getting a tdmtheme.moc failure??
I don't know and I looked behind the
curtain too. :-) Possibly because glibc
2.15 installed rather than 2.16?