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 0001490]: kernel-headers 2.6.12 unsuitable for ARM EABI
Date: Fri, 7 Sep 2007 11:52:06 -0700	[thread overview]
Message-ID: <745a045e13b7bbff5b2140a8337e0ffa@busybox.net> (raw)


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1490 
====================================================================== 
Reported By:                ikonst
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1490
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             09-06-2007 05:46 PDT
Last Modified:              09-07-2007 11:52 PDT
====================================================================== 
Summary:                    kernel-headers 2.6.12 unsuitable for ARM EABI
Description: 
When trying to compile uClibc with kernel-headers 2.6.12 on ARM EABI
platform, an error occurs when building libc/misc/sysvipc/msgget.os (from
libc/misc/sysvipc/msgq.c), since the kernel headers undefines the __NR_ipc
syscall on ARM EABI and also doesn't define __NR_msgctl (claiming that
there's a multiplexer syscall which should be used instead). In any case,
it's a mess which is not present in modern (e.g. 2.6.21) kernel headers.
====================================================================== 

---------------------------------------------------------------------- 
 bernhardf - 09-07-07 11:52  
---------------------------------------------------------------------- 
BR2_DEPRECATED should be obvious enough. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-06-07 05:46  ikonst         New Issue                                    
09-06-07 05:46  ikonst         Status                   new => assigned     
09-06-07 05:46  ikonst         Assigned To               => buildroot       
09-06-07 05:46  ikonst         File Added:
buildroot-arm-eabi-kernel-headers.patch                    
09-07-07 11:52  bernhardf      Status                   assigned => closed  
09-07-07 11:52  bernhardf      Note Added: 0002728                          
======================================================================

             reply	other threads:[~2007-09-07 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 18:52 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-06 12:46 [Buildroot] [buildroot 0001490]: kernel-headers 2.6.12 unsuitable for ARM EABI 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=745a045e13b7bbff5b2140a8337e0ffa@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