* [Buildroot] busybox-1.5.0 miscutils/taskset.c compile errors [not found] ` <200704112118.19272.vda.linux@googlemail.com> @ 2007-04-11 20:07 ` Ulf Samuelsson 2007-04-12 7:12 ` Bernhard Fischer 0 siblings, 1 reply; 2+ messages in thread From: Ulf Samuelsson @ 2007-04-11 20:07 UTC (permalink / raw) To: buildroot > On Wednesday 11 April 2007 12:29, Ulf Samuelsson wrote: >> It seems that there is some undefined defines's in the "taskset.c" >> >> CPU_ISSET >> CPU_SETSIZE >> CPU_ZERO >> CPU_SET >> >> They are supposed to be set in "sched.h", and they are present in >> >> /usr/include/sched.h >> >> on my OpenSuse PC, but they are not present in linux-2.6.20.4 tarball >> >> I could not find them in the toolchain includes... > > my copy of glibc 2.4 supplies /usr/include/sched.h, and it does contain > those defines. > -- > vda > The buildroot toolchain is built using uclibc so maybe it is an uclibc problem then? Then definitely, buildroot busybox configs should not enable building "taskset.c"... Best Regards Ulf Samuelsson ^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] busybox-1.5.0 miscutils/taskset.c compile errors 2007-04-11 20:07 ` [Buildroot] busybox-1.5.0 miscutils/taskset.c compile errors Ulf Samuelsson @ 2007-04-12 7:12 ` Bernhard Fischer 0 siblings, 0 replies; 2+ messages in thread From: Bernhard Fischer @ 2007-04-12 7:12 UTC (permalink / raw) To: buildroot On Wed, Apr 11, 2007 at 10:07:23PM +0200, Ulf Samuelsson wrote: > > >> On Wednesday 11 April 2007 12:29, Ulf Samuelsson wrote: >>> It seems that there is some undefined defines's in the "taskset.c" >>> >>> CPU_ISSET >>> CPU_SETSIZE >>> CPU_ZERO >>> CPU_SET >>> >>> They are supposed to be set in "sched.h", and they are present in >>> >>> /usr/include/sched.h >>> >>> on my OpenSuse PC, but they are not present in linux-2.6.20.4 tarball >>> >>> I could not find them in the toolchain includes... >> >> my copy of glibc 2.4 supplies /usr/include/sched.h, and it does contain >> those defines. >> -- >> vda >> > >The buildroot toolchain is built using uclibc so maybe it is an uclibc problem then? >Then definitely, buildroot busybox configs should not enable building "taskset.c"... The user should not choose to use stuff that does not work for their config. taskset works perfectly well with uClibc trunk, so, as said, if you need taskset then use uClibc-trunk otherwise turn it off. Keep in mind that buildroot's config is supposed to be set by the user depending on their needs. It's really a "doctor, it hurts when i.." (non-)issue. kind regards, ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-04-12 7:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <010001c77c24$e9ee8ba0$254565d5@atmel.com>
[not found] ` <200704112118.19272.vda.linux@googlemail.com>
2007-04-11 20:07 ` [Buildroot] busybox-1.5.0 miscutils/taskset.c compile errors Ulf Samuelsson
2007-04-12 7:12 ` Bernhard Fischer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox