Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: I want my <asm/ucontext.h>
Date: Thu, 31 Jul 2008 23:14:31 +0200	[thread overview]
Message-ID: <48922B37.9070807@gmx.net> (raw)
In-Reply-To: <4892166E.2050206@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

Hi,
forget these patches. asm/ucontext.h isnt needed so much. Newer Debian's
do not have it also.

I modified the source file to include <ucontext.h> (from glibc) instead
and this works without problems.

Regards
Robert

Robert Schuster schrieb:
> Hi,
> I am currently writing a recipe for Sun's phoneme and this wants to
> 
> #include <asm/ucontext.h>
> 
> Unfortunately this file is not part of our newer linux-libc-header
> packages anymore. The problem is as follows:
> 
> In the recipes for versions earlier than 2.6.18 we copied the kernel's
> include/asm-$ARCH/ files manually. In later kernels we relied upon 'make
> install_headers'. Now the kernels Kbuild files do not mention ucontext.h
> and as such it is not installed.
> 
> In the attached patch I added the installation of ucontext.h for all
> newer linux-libc-headers recipes.
> 
> Please write if that is OK for .dev.
> 
> Regards
> Robert
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

      reply	other threads:[~2008-07-31 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 19:45 RFC: I want my <asm/ucontext.h> Robert Schuster
2008-07-31 21:14 ` Robert Schuster [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=48922B37.9070807@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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