From: Sam Ravnborg <sam@ravnborg.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Missing unistd_no.h and unistd_mm.h export on m68k
Date: Thu, 5 Feb 2009 06:53:37 +0100 [thread overview]
Message-ID: <20090205055337.GA30333@uranus.ravnborg.org> (raw)
In-Reply-To: <20090204184659.GG26064@csclub.uwaterloo.ca>
On Wed, Feb 04, 2009 at 01:46:59PM -0500, Lennart Sorensen wrote:
> On Wed, Feb 04, 2009 at 01:31:42PM -0500, Lennart Sorensen wrote:
> > On Wed, Feb 04, 2009 at 01:14:53PM -0500, Lennart Sorensen wrote:
> > > make header_install fails to include the files unistd_no.h and
> > > unistd_mm.h on m68k, while those two files are included by unistd.h.
> > >
> > > This patch fixes this by adding these two files to the list of m68k
> > > specific headers to export.
> > >
> > > Signed-off-by: Len Sorensen <lsorense@csclub.uwaterloo.ca>
> > >
> > > Signed
> > > diff --git a/arch/m68k/include/asm/Kbuild b/arch/m68k/include/asm/Kbuild
> > > index 1a922fa..2bb4738 100644
> > > --- a/arch/m68k/include/asm/Kbuild
> > > +++ b/arch/m68k/include/asm/Kbuild
> > > @@ -1,2 +1,2 @@
> > > include include/asm-generic/Kbuild.asm
> > > -header-y += cachectl.h
> > > +header-y += cachectl.h unistd_no.h unistd_mm.h
> >
> > Hmm, seems it is actually much worse than I thought. All _no.h and
> > _mm.h are being missed, making m68k compiles of things like uclibc
> > rather broken. Yuck.
>
> So updated patch that makes uclibc actually compile for m68k.
>
> --
> Len Sorensen
>
>
>
> make header_install fails to include the files *_no.h and
> *_mm.h on m68k, while those files are included by the matching *.h
>
> This patch fixes this by adding these missing files to the list of m68k
> specific headers to export. With this patch, uclibc compiles again.
Hi Len.
Indeed the *_no.h, *_mm.h is missing from Kbuild.h.
But looking at your patch you added much more than the
missing *_no.h, *_mm.h.
When doing this do it in steps:
1) fix make headers_check
This is fixed by adding the *_no.h,*_mm.h for files that
are exported. And that is the files lited in include/asm-generic/Kbuild.asm
plus the single file listed in the m68k Kbuld file.
2) then as a separate patch export the additional files needed to build
ulibc.
Do it file-by-file so you are sure you do not add a single file
that is not needed. We want to have a minimal set of files exported.
And when you prepare your patch please use one line per header file,
as we do in all the ohter Kbuild files.
Sam
next prev parent reply other threads:[~2009-02-05 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 18:14 Lennart Sorensen
2009-02-04 18:31 ` Lennart Sorensen
2009-02-04 18:46 ` Lennart Sorensen
2009-02-04 20:20 ` Lennart Sorensen
2009-02-05 5:53 ` Sam Ravnborg [this message]
2009-02-05 15:51 ` Lennart Sorensen
2009-02-05 15:54 ` Lennart Sorensen
2009-02-05 19:48 ` Sam Ravnborg
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=20090205055337.GA30333@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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
all inboxes | Powered by JetHome®