From: Kip Macy <kip.macy@gmail.com>
To: xen-devel@lists.xensource.com
Subject: c99 compliance
Date: Tue, 12 Apr 2005 10:34:54 -0700 [thread overview]
Message-ID: <b1fa2917050412103464918094@mail.gmail.com> (raw)
In trying to bring freebsd up to date with -unstable I hit the following:
kmacy@bldf2 make kernel
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I.
-I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq
-I../../../contrib/ipfilter -I../../../contrib/pf
-I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd
-I../../../contrib/ngatm -I../../include/xen-public -D_KERNEL -include
opt_global.h -fno-common -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding
-Werror ../../../cam/cam.c
In file included from ./machine/hypervisor-ifs.h:14,
from ./machine/xen-os.h:56,
from ./machine/cpufunc.h:48,
from ../../../sys/systm.h:42,
from ../../../cam/cam.c:35:
./machine/xen-public/xen.h:186: warning: declaration does not declare anything
./machine/xen-public/xen.h:192: warning: declaration does not declare anything
In file included from ./machine/hypervisor-ifs.h:15,
from ./machine/xen-os.h:56,
from ./machine/cpufunc.h:48,
from ../../../sys/systm.h:42,
from ../../../cam/cam.c:35:
./machine/xen-public/io/domain_controller.h:45: warning: declaration
does not declare anything
./machine/xen-public/io/domain_controller.h:49: warning: declaration
does not declare anything
*** Error code 1
Stop in /amd/ayr/vol/users2/home/kmacy/xen/050322/xeno-unstable.bk/freebsd-5.3-xenU/i386-xen/compile/XENCONF.
Compiling without -std=c99 works ok. Would it be reasonable to ask
that we stick -std=c99 into the makefiles?
kmacy@bldf2 cc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.2 [FreeBSD] 20040728
-Kip
reply other threads:[~2005-04-12 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b1fa2917050412103464918094@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.