Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001309]: Busybox 1.5.0 build crashes when building miscutils/patchset.c under buildroot
Date: Wed, 11 Apr 2007 05:46:18 -0700	[thread overview]
Message-ID: <226d87f12595209fd96a821038362ce8@busybox.net> (raw)


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1309 
====================================================================== 
Reported By:                Ulf Samuelsson
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1309
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             04-11-2007 03:44 PDT
Last Modified:              04-11-2007 05:46 PDT
====================================================================== 
Summary:                    Busybox 1.5.0 build crashes when building
miscutils/patchset.c under buildroot
Description: 
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 "include/sched.h", and they are present in


/usr/include/sched.h 

on my OpenSuse 10.2 PC, but they are not present in the linux-2.6.20.4
tarball

I could not find them in the toolchain includes...


There is a compile error at line 17 as well...

====================================================================== 

---------------------------------------------------------------------- 
 bernhardf - 04-11-07 05:46  
---------------------------------------------------------------------- 
1) this is not a buildroot issue.
2) read the helptext for taskset
3) if you need taskset, use uClibc-trunk 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-11-07 03:44  Ulf Samuelsson New Issue                                    
04-11-07 03:44  Ulf Samuelsson Status                   new => assigned     
04-11-07 03:44  Ulf Samuelsson Assigned To               => buildroot       
04-11-07 05:46  bernhardf      Status                   assigned => closed  
04-11-07 05:46  bernhardf      Note Added: 0002306                          
======================================================================

             reply	other threads:[~2007-04-11 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 12:46 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-30 11:50 [Buildroot] [buildroot 0001309]: Busybox 1.5.0 build crashes when building miscutils/patchset.c under buildroot bugs at busybox.net
2007-04-11 10:44 bugs at busybox.net

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=226d87f12595209fd96a821038362ce8@busybox.net \
    --to=bugs@busybox.net \
    --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