There are a few changes in glibc-2.10 that might make your software fail to build with it, please refer to my blog post [1] if you're not sure what the problem is. And no I don't usually provide emerge --info with these bugs because they are caused by glibc-2.10! Thanks, Diego [1] http://blog.flameeyes.eu/2009/05/24/c-libraries-galore
Created attachment 193294 [details] Build log
Created attachment 197171 [details, diff] bumps ebuild to EAPI=2 and renames local strndup This small change tries to bump the ebuild into EAPI-2 age and fixes the locally specified strndup by renaming it.
If it's doing what it seems to be doing (otherwise it would have been broken on older glibc too), wouldn't it make more sense to simply _use_ the system copy instead of reinventing it, if present?
(In reply to comment #3) > If it's doing what it seems to be doing (otherwise it would have been broken on > older glibc too), wouldn't it make more sense to simply _use_ the system copy > instead of reinventing it, if present? > I tried that. kkstrtext.cc:434: error: cast from ‘void*’ to ‘int’ loses precision kkstrtext.cc:434: error: cast from ‘void*’ to ‘int’ loses precision This is the result.
Created attachment 200710 [details, diff] Doesn't really work but adding for reference.
actually it fails even if they're just renamed so letting this one stay masked
Bye.