public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: One test per line, one source per line, etc. etc. etc.
Date: Mon, 28 Jun 2021 14:52:00 -0400	[thread overview]
Message-ID: <xneecl6cvj.fsf@greed.delorie.com> (raw)
In-Reply-To: <f6406204-84f5-adb1-d00e-979ebeebbbde@redhat.com>

"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org> writes:
> Do we have consensus for someone to just cleanup all the makefiles
> to have one source per line, one test per line etc.?

Yes (again) :-)

I have two comments:

1. I use some sort of end-of-list tag, like this:

FILES = \
	a.c \
	b.c \
	$(ENDOFLIST)

or just $E or anything that expands to nothing.  Remnants of an old job
where adding the trailing \ to the previous line caused 100% patch
conflicts.  I'm not tied to any particular method, but I'm very against
the omit-last-slash format.

2. I recommend the files NOT be listed in strict alphabetical order,
when there's a large variance in build times.  List the files that take
longest, first.  Comment it as such, of course.  Leftovers from
libiberty's builds, where a parallel make spent most of its time waiting
for the ONE file that took forver to build, which was last in the
alphabetical list, so was always built by itself.


      parent reply	other threads:[~2021-06-28 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 19:58 Carlos O'Donell
2021-06-27 20:14 ` Florian Weimer
2021-06-27 21:52   ` Carlos O'Donell
2021-06-28  7:24     ` Andreas Schwab
2021-06-28 11:42       ` Carlos O'Donell
2021-06-28  9:22   ` Dmitry V. Levin
2021-06-28 10:05     ` Florian Weimer
2021-06-28 11:45       ` Carlos O'Donell
2021-06-28 18:52 ` DJ Delorie [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=xneecl6cvj.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).