From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: linux-next: sparc64 build failure
Date: Wed, 9 Jul 2008 23:23:33 +0200 [thread overview]
Message-ID: <20080709212333.GA3759@uranus.ravnborg.org> (raw)
In-Reply-To: <20080709211515.0d2c5100.sfr@canb.auug.org.au>
On Wed, Jul 09, 2008 at 09:15:15PM +1000, Stephen Rothwell wrote:
> Hi Sam,
>
> Today's linux-next build (sparc64 allmodconfig) failed like this:
>
> usr/include/asm/auxvec.h:1: included file 'asm-sparc/auxvec.h' is not exported
> usr/include/asm/bpp.h:1: included file 'asm-sparc/bpp.h' is not exported
> usr/include/asm/byteorder.h:1: included file 'asm-sparc/byteorder.h' is not exported
> usr/include/asm/errno.h:1: included file 'asm-sparc/errno.h' is not exported
> usr/include/asm/openpromio.h:1: included file 'asm-sparc/openpromio.h' is not exported
> usr/include/asm/perfctr.h:1: included file 'asm-sparc/perfctr.h' is not exported
My bad - but I do not have time to look into it now.
Too much painting/moving stuff - sorry!
Sam
next prev parent reply other threads:[~2008-07-09 21:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 11:15 linux-next: sparc64 build failure Stephen Rothwell
2008-07-09 21:23 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 9:08 Stephen Rothwell
2008-07-08 9:13 ` David Miller
2008-06-20 0:43 Stephen Rothwell
2008-06-20 0:55 ` David Miller
2008-06-20 1:11 ` Stephen Rothwell
2008-06-20 7:34 ` Sam Ravnborg
2008-06-20 7:53 ` Stephen Rothwell
2008-06-20 8:34 ` Sam Ravnborg
2008-06-21 0:02 ` Stephen Rothwell
2008-05-29 7:53 Stephen Rothwell
2008-05-29 22:01 ` Greg KH
2008-05-30 5:38 ` Stephen Rothwell
2008-05-30 14:10 ` Greg KH
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=20080709212333.GA3759@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.