From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdbserver: Suffix generated C files with -generated
Date: Tue, 04 Apr 2017 10:44:00 -0000 [thread overview]
Message-ID: <d28ec3f4-d167-d828-fc9a-69bdbb83774a@redhat.com> (raw)
In-Reply-To: <4de294ed1d439274043f4fdb02689664@polymtl.ca>
On 03/31/2017 08:39 PM, Simon Marchi wrote:
>> Do you have any better idea?
Not off hand.
> Huh, I've just noticed that gdb does this already:
>
> rm -f $(DEPDIR)/*
>
> which translates to:
>
> rm -f .deps/*
>
> So I guess it'd make sense to do it as well in gdbserver.
Go for it.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-04-04 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 3:14 [PATCH] " Simon Marchi
2017-03-30 3:31 ` Simon Marchi
2017-03-31 12:24 ` Pedro Alves
2017-03-31 13:35 ` Simon Marchi
2017-03-31 14:56 ` [PATCH v2] " Simon Marchi
2017-03-31 15:13 ` Pedro Alves
[not found] ` <3038cd35b397eeafa1f8f0447630fa8e@polymtl.ca>
2017-03-31 18:46 ` Simon Marchi
2017-03-31 19:39 ` Simon Marchi
2017-04-04 10:44 ` Pedro Alves [this message]
2017-04-04 14:52 ` [PATCH pushed] gdbserver: Clear .deps on clean Simon Marchi
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=d28ec3f4-d167-d828-fc9a-69bdbb83774a@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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