From: Richard Zak <richard.j.zak@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] Fix for Haiku
Date: Sun, 4 Jul 2021 10:26:04 -0400 [thread overview]
Message-ID: <CAOakUfPL0D+BC8DTmLSkPMC+okRaAasH1vC5dSbvSjEUEAZuNQ@mail.gmail.com> (raw)
In-Reply-To: <4567246f-062b-9d6e-38b6-33dc0ab0099e@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
I'll re-submit with better comments, and this variable is defined on Haiku,
presumably for support for old Be OS applications, to indicate the
architecture of the CPU. On my 64-bit system, it's value is "x86_64",
32-bit it's "x86".
În dum., 4 iul. 2021 la 09:51, Philippe Mathieu-Daudé <f4bug@amsat.org> a
scris:
> On 7/4/21 12:00 PM, Philippe Mathieu-Daudé wrote:
> > On 7/3/21 11:12 PM, Richard Zak wrote:
> >> Fix for path to env
> >>
> >> Signed-off-by: Richard Zak <richard.j.zak@gmail.com
> >> <mailto:richard.j.zak@gmail.com>>
> >> ---
> >> Makefile | 4 ++++
> >> 1 file changed, 4 insertions(+)
> >>
> >> diff --git a/Makefile b/Makefile
> >> index 30f19d33bb..ced9b97372 100644
> >> --- a/Makefile
> >> +++ b/Makefile
> >> @@ -14,7 +14,11 @@ SRC_PATH=.
> >> # we have explicit rules for everything
> >> MAKEFLAGS += -rR
> >>
> >> +ifneq ($(BE_HOST_CPU),)
> >
> > Where is this variable defined and what is it for?
>
> IIUC it is defined by BeOS, and Haiku is based on it,
> so also defines it. Is that correct?
>
--
Regards,
Richard J. Zak
Professional Genius
PGP Key: https://keybase.io/rjzak/key.asc
[-- Attachment #2: Type: text/html, Size: 2003 bytes --]
prev parent reply other threads:[~2021-07-04 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 21:12 [PATCH 2/2] Fix for Haiku Richard Zak
2021-07-04 7:16 ` Thomas Huth
2021-07-04 10:00 ` Philippe Mathieu-Daudé
2021-07-04 13:51 ` Philippe Mathieu-Daudé
2021-07-04 14:26 ` Richard Zak [this message]
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=CAOakUfPL0D+BC8DTmLSkPMC+okRaAasH1vC5dSbvSjEUEAZuNQ@mail.gmail.com \
--to=richard.j.zak@gmail.com \
--cc=f4bug@amsat.org \
--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).