From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Sanity
Date: Tue, 7 Feb 2012 22:22:16 +0400 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1202072213140.10788@linmac> (raw)
This is a 32bit machine, the target is i386-softmmu, yet,
libhw32 is mostly empty and libhw64 is populated, furthermore[1]:
$ rm libhw64/ac97.o
$ make V=1
make BUILD_DIR=/home/malc/x/bld/qemu/master -C libhw64 V="1" TARGET_DIR="libhw64/" all
make[1]: Entering directory `/home/malc/x/bld/qemu/master/libhw64'
ccache gcc -fno-working-directory -I/home/malc/x/rcs/git/qemuorg/slirp -I. -I/home/malc/x/rcs/git/qemuorg -I/home/malc/x/rcs/git/qemuorg/fpu -Werror -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -I/usr/include/libpng14 -DTARGET_PHYS_ADDR_BITS=64 -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/home/malc/x/rcs/git/qemuorg/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -MMD -MP -MT ac97.o -MF ./ac97.d -O -g -U_FORTIFY_SOURCE -fno-stack-protector -c -o ac97.o /home/malc/x/rcs/git/qemuorg/hw/ac97.c
make[1]: Leaving directory `/home/malc/x/bld/qemu/master/libhw64'
Why does it say the same thing many times (-pthread -I/usr/include/glib-2.0...),
is gcc suffering from ADD or something?
[1] Just an example.
--
mailto:av1474@comtv.ru
next reply other threads:[~2012-02-07 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 18:22 malc [this message]
2012-02-07 22:11 ` [Qemu-devel] Sanity Stefan Weil
2012-02-07 22:18 ` Andreas Färber
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=alpine.LNX.2.00.1202072213140.10788@linmac \
--to=av1474@comtv.ru \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).