public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "David S. Miller" <davem@sunset.davemloft.net>
Cc: linux-kernel@vger.kernel.org,
	"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
	Andrew Morton <akpm@osdl.org>
Subject: Sparc64 stopped building - sigset_t unrecognized in compat.h
Date: Tue, 10 Oct 2006 11:59:40 -0700	[thread overview]
Message-ID: <20061010115940.4c25ae83.pj@sgi.com> (raw)

Sometime on or about the change to include/linux/compat.h:

    changeset:   39069:fefadae8104d
    parent:      38900:a2856d056930
    user:        David S. Miller <davem@sunset.davemloft.net>
    date:        Tue Oct  3 04:24:18 2006 +0700
    summary:     [SPARC64]: Move signal compat bits to new header file.

which added the line:

    extern void sigset_from_compat(sigset_t *set, compat_sigset_t *compat);

my crosstool compile of sparc64 for 2.6.18-mm3 stopped building.

    $ make init/main.o

fails on the "sigset_t *set", with:

    In file included from include/asm/signal.h:11,
		     from include/linux/signal.h:4,
		     from include/linux/sched.h:67,
		     from include/linux/module.h:9,
		     from init/main.c:13:
    include/linux/compat.h:231: error: parse error before '*' token
    include/linux/compat.h:231: warning: function declaration isn't a prototype
    make[1]: *** [init/main.o] Error 1
    make: *** [init/main.o] Error 2

P.S. -- Looks like I'm not the first to notice.  Adding Dr. von Brand
        and Andrew to my cc list.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

             reply	other threads:[~2006-10-10 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 18:59 Paul Jackson [this message]
2006-10-10 19:36 ` Sparc64 stopped building - sigset_t unrecognized in compat.h David Miller
2006-10-10 19:37 ` Andrew Morton
2006-10-10 19:39   ` Paul Jackson

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=20061010115940.4c25ae83.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=davem@sunset.davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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