Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
	Pedro Alves <palves@redhat.com>,
	Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches <gdb-patches@sourceware.org>,
	Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup
Date: Wed, 12 Aug 2015 18:43:00 -0000	[thread overview]
Message-ID: <20150812184307.GF22245@adacore.com> (raw)
In-Reply-To: <CADPb22QyyO9ni8bAPcweauUPWdH59rFiTDwYf5W6YxY9gwBQiQ@mail.gmail.com>

> I suspect, though I haven't tried, if we remove the
> check-parallel/check-single test, it would be straightforward to
> remove the GNU make requirement and just move the details to a wrapper
> script.

Dependency tracking also requires GNU/Make; would you be able to
take care of that through the wrapper?

> Always invoking runtest by a wrapper script has other benefits.
> 
> I'm not advocating for this, I only ever use GNU make.
> But if the topic comes up, it's not clear to me GNU make
> is an absolute requirement.

It would be nice to list the additional benefits and decide whether
we want to go that route or not, ideally more-or-less independently
of whether we want to require GNU/Make or not.

The reason why I am advocating in favor of requiring GNU/Make is that
we are regularly hindered or doing extra work trying to support non-
GNU/Make, while on the other hand, the community affected by this
proposal only need to update their build procedures to put GNU/Make
on their PATH. And since GCC already requires GNU/Make, I cannot
understand why it would be difficult to do so.

-- 
Joel


  reply	other threads:[~2015-08-12 18:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 20:13 Simon Marchi
2015-08-03 14:23 ` Pedro Alves
2015-08-03 15:16   ` Simon Marchi
2015-08-03 16:34     ` Pedro Alves
2015-08-03 16:38       ` Pedro Alves
2015-08-03 18:10       ` Simon Marchi
2015-08-03 18:42         ` Pedro Alves
2015-08-04 16:11           ` Sergio Durigan Junior
2015-08-04 17:21       ` Joel Brobecker
2015-08-11 17:36         ` Doug Evans
2015-08-11 19:58           ` Joel Brobecker
2015-08-11 20:43             ` Doug Evans
2015-08-11 23:02               ` Joel Brobecker
2015-08-12  9:30           ` Pedro Alves
2015-08-12 16:40             ` Sergio Durigan Junior
2015-08-12 17:22               ` Joel Brobecker
2015-08-12 17:38                 ` Doug Evans
2015-08-12 18:43                   ` Joel Brobecker [this message]
2015-08-12 18:50                     ` Doug Evans
2015-08-12 19:41                       ` Joel Brobecker
2015-08-12 20:23                         ` Doug Evans

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=20150812184307.GF22245@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=sergiodj@redhat.com \
    --cc=simon.marchi@ericsson.com \
    /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