Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Zied Guermazi <zied.guermazi@trande.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] get page size using sysconf (_SC_PAGESIZE) instead of PAGE_SIZE
Date: Mon, 2 May 2022 17:46:49 +0100	[thread overview]
Message-ID: <a0ff4906-be40-b4c3-63ed-74428523a21c@palves.net> (raw)
In-Reply-To: <87tuaa7l1v.fsf@igel.home>

On 2022-04-30 14:33, Andreas Schwab wrote:
> On Apr 30 2022, Zied Guermazi wrote:
> 
>> PAGE_SIZE for target system was not defined, in other cases PAGE_SIZE of
>> the host system was used etc... :).
> 
> This file is only used in a native configuration.
> 

Zied, when you said:

  "the issue was first observed when activating this code while compiling on an x86 for an arm target."

are you talking about:

  --build=x86_64-linux --host=aarch64-linux

or:
  --host=x86_64-linux --target=aarch64-linux

?

I agree with Andreas -- linux-btrace.c is only included in the build on x86 hosts, so why are you seeing
this?  Did you tweak gdb/configure.nat to include linux-btrace.c in other configurations?  Or gdb/configure.tgt?
What exactly did you do?

  reply	other threads:[~2022-05-02 16:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 12:16 [PATCH v4 0/1] " Zied Guermazi
2022-04-30 12:16 ` [PATCH 1/1] " Zied Guermazi
2022-04-30 12:29   ` Andreas Schwab
2022-04-30 12:32     ` Zied Guermazi
2022-04-30 12:52       ` Andreas Schwab
2022-04-30 12:58         ` Zied Guermazi
2022-04-30 13:03           ` Andreas Schwab
2022-04-30 13:25             ` Zied Guermazi
2022-04-30 13:33               ` Andreas Schwab
2022-05-02 16:46                 ` Pedro Alves [this message]
2022-05-02 18:01                   ` Zied Guermazi
2022-05-02 18:55                     ` Pedro Alves
2022-05-02 19:16                       ` Zied Guermazi
2022-05-02 16:38   ` Tom Tromey
2022-05-02 16:50     ` Pedro Alves
2022-05-02 17:04       ` Tom Tromey
2022-05-02 17:08         ` Pedro Alves
  -- strict thread matches above, loose matches on Subject: below --
2022-04-24 21:15 [PATCH 0/1] btrace: " Zied Guermazi
2022-04-24 21:15 ` [PATCH 1/1] " Zied Guermazi
2022-04-25  5:03   ` Metzger, Markus T via Gdb-patches
2022-04-25  7:02     ` Zied Guermazi
2022-04-25  7:36       ` Metzger, Markus T via Gdb-patches

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=a0ff4906-be40-b4c3-63ed-74428523a21c@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    --cc=zied.guermazi@trande.de \
    /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