From: mru@users.sourceforge.net (Måns Rullgård)
To: "T. Weyergraf" <kirk@colinet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67 alpha compile failure
Date: 12 Apr 2003 21:42:00 +0200 [thread overview]
Message-ID: <yw1xllyfv6yf.fsf@zaphod.guide> (raw)
In-Reply-To: <kirk-1030412154541.A0214377@hydra.colinet.de>
"T. Weyergraf" <kirk@colinet.de> writes:
> kernel 2.5.67 fails to compile on alpha ( DP264, SMP ):
>
> [...]
> gcc -Wp,-MD,kernel/.sys.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev6 -Wa,-mev6 -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=sys -DKBUILD_MODNAME=sys -c -o kernel/sys.o kernel/sys.c
> kernel/sys.c:226: conflicting types for `sys_sendmsg'
> include/linux/socket.h:245: previous declaration of `sys_sendmsg'
> kernel/sys.c:227: conflicting types for `sys_recvmsg'
> include/linux/socket.h:246: previous declaration of `sys_recvmsg'
> make[1]: *** [kernel/sys.o] Error 1
> make: *** [kernel] Error 2
>
> Obviously, commenting-out those declarations fixes the compile problem and the rest of the
> build passes just fine.
> This problem is new to me. 2.5.64 and 65 do not have it.
>
> My question is: Is commenting-out the declarations the Correct Way (TM) ?
> I don't think so ...
See my message with subject "[PATCH] Fix cond_syscall macro on Alpha".
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-04-12 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 13:45 2.5.67 alpha compile failure T. Weyergraf
2003-04-12 19:42 ` Måns Rullgård [this message]
2003-04-13 22:50 ` 2.5.67 alpha compile failure (solved but nfsd Oopses now) Christian
2003-04-14 11:37 ` nfs-kernel-server Oopses with 2.5.67 Christian
2003-04-14 11:54 ` Måns Rullgård
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=yw1xllyfv6yf.fsf@zaphod.guide \
--to=mru@users.sourceforge.net \
--cc=kirk@colinet.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox