From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: dwmw2@infradead.org
Subject: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Thu, 12 Mar 2009 04:37:03 -0500 [thread overview]
Message-ID: <200903120437.03837.rob@landley.net> (raw)
So I'm doing this:
make ARCH=m68k headers_install INSTALL_HDR_PATH=walrus
And it doesn't install unistd_mm.h which is included from asm/unistd.h. (The
file is there in arch/m68k/include/asm/unistd_mm.h, it just doesn't get
installed. So any code that #includes <asm/unistd.h> results in a file not
found error for the other one, which is essentially just a wrapper.)
I don't understand what the code's currently doing here well enough to fix it,
specifically where does this file list come from? The file
arch/m68k/include/asm/Kbuild is adding "cachectl.h" to header-y, but there are
31 files getting installed from that directory and only one in there. If the
list was just the contents of the directory, then unistd_mm.h (and
unistd_no.h) would get installed, but they don't. I could add those two to
the Kbuild file after cachectl.h, but is that the _right_ fix? Where are the
other 31 identified? (Is it getting a listing of some _other_ directory?)
Confused,
Rob
next reply other threads:[~2009-03-12 9:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 9:37 Rob Landley [this message]
2009-03-12 9:58 ` make headers_install broken for ARCH=m68k in 2.6.29-rc7 Sam Ravnborg
2009-03-12 20:03 ` Rob Landley
2009-03-12 20:58 ` Sam Ravnborg
2009-03-12 23:24 ` Stephen Rothwell
2009-03-12 21:02 ` Sam Ravnborg
2009-03-12 22:40 ` Geert Uytterhoeven
2009-03-13 3:25 ` Rob Landley
2009-03-13 7:04 ` Greg Ungerer
2009-03-13 8:25 ` Sam Ravnborg
2009-03-13 8:33 ` Geert Uytterhoeven
2009-03-13 8:59 ` Sam Ravnborg
2009-03-13 10:52 ` Greg Ungerer
2009-03-13 12:14 ` Geert Uytterhoeven
2009-03-13 12:14 ` Geert Uytterhoeven
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 20:20 ` Rob Landley
2009-03-16 20:20 ` Rob Landley
2009-03-16 22:08 ` Geert Uytterhoeven
2009-03-16 23:09 ` Greg Ungerer
2009-03-16 23:10 ` Greg Ungerer
2009-03-16 23:10 ` Greg Ungerer
2009-03-18 4:03 ` Rob Landley
2009-03-18 4:03 ` Rob Landley
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 18:12 ` Rob Landley
2009-03-18 18:12 ` Rob Landley
2009-03-18 23:53 ` Greg Ungerer
2009-03-18 23:53 ` Greg Ungerer
2009-03-18 23:53 ` Greg Ungerer
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 8:41 ` Rob Landley
2009-03-18 18:12 ` Rob Landley
2009-03-16 20:20 ` Rob Landley
2009-03-16 12:40 ` Greg Ungerer
2009-03-13 8:25 ` Geert Uytterhoeven
2009-03-13 6:53 ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03 ` Sam Ravnborg
2009-04-01 19:48 ` Lennart Sorensen
2009-04-01 20:23 ` Geert Uytterhoeven
2009-04-01 22:59 ` Lennart Sorensen
2009-04-02 2:14 ` Rob Landley
2009-04-02 21:59 ` Lennart Sorensen
2009-04-03 0:24 ` Rob Landley
2009-04-03 4:10 ` Lennart Sorensen
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=200903120437.03837.rob@landley.net \
--to=rob@landley.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.