At Thu, 7 Apr 2005 23:46:51 -0700, David Mosberger wrote: > GOTO> I fear to change this interface until sarge release because there > GOTO> might be another packages that uses sched_setaffinity. > > Well, yes, schedutils probably would need updating. I don't know of > anything else, though. We only care about the Debian packages for > sarge, I assume, right? If so, couldn't someone do a trivial find > across all sources for sched_{s,g}et_affinity? I'd be happy to > volunteer to fix all the packages that are affected (I'm not too > worried, the number will be very small, I'm sure of that).
Yes, fixing this issue is not difficult. The problem I concerned is the symbol GLIBC_PRIVATE is defined as GLIBC_2.3.4, not the current symbol GLIBC_2.3.3. I'm not certain this change does not cause any problems. > GOTO> I tender not to include the patch. I would like to call your opinion > GOTO> about Bastian's patch. > > That would really be unfortunate because it will mean that Debian is > incompatible with all other modern distributions. It's very likely > that it will cause a lot more grief down the road because new software > will break. For example, recent LMbench3 releases started to use > sched_setaffinity() and of course they use the correct (new) > interface... Indeed, but I would like to clear about the change of GLIBC_PRIVATE... Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]