From: Michael Tokarev <mjt@tls.msk.ru>
To: Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Building tools on unsupported cpu/arch
Date: Sat, 30 Apr 2022 20:08:45 +0300 [thread overview]
Message-ID: <18da14fc-c582-c6f6-8d3d-bf3b47d2a15c@msgid.tls.msk.ru> (raw)
In-Reply-To: <61fb585e-3ca6-b218-750c-9e833edd9f3f@linaro.org>
30.04.2022 19:57, Richard Henderson wrote:
..
>> What's the way to build tools on an unsupported architecture these days?
>
> Hmm, well, there isn't a way. This seems like a bug in common-user/meson.build.
> We should not add this include directory if neither linux-user and bsd-user are enabled.
Aftr adding an if similar to linux-user/meson.build (with this condition), it
fails down the line anyway:
cc -Ilibui-sdl.a.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/SDL2 -I/usr/include/pixman-1 -I/usr/include/glib-2.0
-I/usr/lib/hppa-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem
/home/mjt/qemu-7.0+dfsg/linux-headers -isystem linux-headers -iquote . -iquote /home/mjt/qemu-7.0+dfsg -iquote /home/mjt/qemu-7.0+dfsg/include -iquote
/home/mjt/qemu-7.0+dfsg/disas/libvixl -iquote /home/mjt/qemu-7.0+dfsg/tcg/tci -pthread -U_FORTIFY_SOURCE -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv
-Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -g -O2
-ffile-prefix-map=/home/mjt/qemu-7.0+dfsg=. -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_REENTRANT -Wno-undef -DBUILD_DSO
-MD -MQ libui-sdl.a.p/ui_x_keymap.c.o -MF libui-sdl.a.p/ui_x_keymap.c.o.d -o libui-sdl.a.p/ui_x_keymap.c.o -c ../../ui/x_keymap.c
In file included from ../../ui/x_keymap.c:15:
../../ui/trace.h:1:10: fatal error: trace/trace-ui.h: No such file or directory
1 | #include "trace/trace-ui.h"
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
This is, again, --disable-system --disable-user --enable-tools,
so it should not, I guess, compile ui-sdl. Or should it?
Thanks,
/mjt
next prev parent reply other threads:[~2022-04-30 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 14:11 Building tools on unsupported cpu/arch Michael Tokarev
2022-04-30 16:57 ` Richard Henderson
2022-04-30 17:08 ` Michael Tokarev [this message]
2022-06-20 10:31 ` Thomas Huth
2022-06-20 10:54 ` Michael Tokarev
2022-06-20 12:07 ` Thomas Huth
2022-07-18 7:39 ` Thomas Huth
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=18da14fc-c582-c6f6-8d3d-bf3b47d2a15c@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).