From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Design idea for subarchs/abivariants
Date: Wed, 28 Nov 2012 22:50:12 +0100 [thread overview]
Message-ID: <20121128215012.GK10895@port70.net> (raw)
In-Reply-To: <20121128120341.ca114e90.idunham@lavabit.com>
* Isaac Dunham <idunham@lavabit.com> [2012-11-28 12:03:41 -0800]:
> I usually do this to cleanup in such cases:
> find src arch -name '*.*o' |xargs rm
> Would adding some similar logic be sensible (at least for the distclean target)?
>
rm -f src/*/*o
actually i have
all:
mclean:
rm -f src/math/*o
in my config.mak so i can easily clean math
and then rebuild with different flags etc
next prev parent reply other threads:[~2012-11-28 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 19:26 Rich Felker
2012-11-28 20:03 ` Isaac Dunham
2012-11-28 21:50 ` Szabolcs Nagy [this message]
2012-11-28 23:57 ` Rich Felker
2012-11-28 20:26 ` John Spencer
2012-11-28 22:38 ` Szabolcs Nagy
2012-11-29 0:10 ` Rich Felker
2012-11-29 0:22 ` Kurt H Maier
2012-11-29 1:21 ` Rich Felker
2012-11-29 8:03 ` Szabolcs Nagy
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=20121128215012.GK10895@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).