From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] busybox-1.5.0 miscutils/taskset.c compile errors
Date: Thu, 12 Apr 2007 09:12:05 +0200 [thread overview]
Message-ID: <20070412071205.GC4244@aon.at> (raw)
In-Reply-To: <031901c77c75$55f6e450$254565d5@atmel.com>
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,
prev parent reply other threads:[~2007-04-12 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070412071205.GC4244@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox