linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Big include file move breaks user mode
Date: Tue, 5 Aug 2008 11:13:56 -0500	[thread overview]
Message-ID: <988452A8-7DC4-4FFE-9E5B-F93E4BB7A847@kernel.crashing.org> (raw)
In-Reply-To: <20080805120916.2f39307c@lappy.seanm.ca>


On Aug 5, 2008, at 11:09 AM, Sean MacLennan wrote:

> Almost all of the includes in include/asm-powerpc where moved to
> arch/powerpc/include/asm. This is breaking almost all of my user mode
> code... so I assume I am doing something very wrong.
>
> Here is a simple program that flushes stdout for no apparent reason ;)
>
> #include <stdio.h>
> #include <sys/ioctl.h>
>
> int main(int argc, char *argv[])
> {
> 	ioctl(1, TCFLSH, 1);
> 	return 0;
> }
>
> This builds and runs fine under x86 and ppc before the include file
> move. After the move, the compile fails because gcc can't find
> asm/ioctls.h which is needed by /usr/include/bits/ioctls.h (let's
> ignore the cross-compile path for now).
>
> The other big one I am hitting is that /usr/include/bits/errno.h
> includes linux/errno.h which includes asm/errno.h which no longer
> exists.
>
> Anybody know how to fix this? I am using the DENX 4.1 toolchain if  
> that
> helps. Also, if there is a better place to post this, let me know. I
> posted here since it only affects powerpc cross compiles... x86 still
> has all the includes in "the right place".
>
> Should include/asm be a link to arch/powerpc/include/asm?

Are you using the headers_install option?  or just point to a kernel  
tree.

- k

  reply	other threads:[~2008-08-05 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 16:09 Big include file move breaks user mode Sean MacLennan
2008-08-05 16:13 ` Kumar Gala [this message]
2008-08-06 14:51 ` Arnd Bergmann
2008-08-06 15:01   ` Sean MacLennan
2008-08-06 17:43     ` René Rebe
2008-08-06 17:44     ` René Rebe
2008-08-06 19:21       ` Kumar Gala

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=988452A8-7DC4-4FFE-9E5B-F93E4BB7A847@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.com \
    /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;
as well as URLs for NNTP newsgroup(s).