From: Ron Mercer <ron.mercer@qlogic.com>
To: netdev@vger.kernel.org
Cc: ron.mercer@qlogic.com, davem@davemloft.net
Subject: net-2.6 build error on powerpc
Date: Thu, 8 Oct 2009 08:20:44 -0700 [thread overview]
Message-ID: <20091008152044.GA15390@linux-ox1b.qlogic.org> (raw)
I recently grabbed the latest net-2.6 kernel for a powerpc test box and
got this compile error.
CC arch/powerpc/kernel/cputable.o
CC arch/powerpc/kernel/ptrace.o
CC arch/powerpc/kernel/syscalls.o
CC arch/powerpc/kernel/irq.o
CC arch/powerpc/kernel/align.o
CC arch/powerpc/kernel/signal_32.o
CC arch/powerpc/kernel/pmc.o
CC arch/powerpc/kernel/vdso.o
cc1: warnings being treated as errors
arch/powerpc/kernel/vdso.c:78: warning: alignment of
âso_data_storeâs greater than maximum object file
alignment. Using 32768
make[1]: *** [arch/powerpc/kernel/vdso.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
[root@localhost linux-2.6-net.git]#
Any suggestions would be appreciated.
next reply other threads:[~2009-10-08 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 15:20 Ron Mercer [this message]
2009-12-16 8:37 ` net-2.6 build error on powerpc Zhiyong Wu
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=20091008152044.GA15390@linux-ox1b.qlogic.org \
--to=ron.mercer@qlogic.com \
--cc=davem@davemloft.net \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox