From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Some simple build simplification patches
Date: Fri, 25 Mar 2011 20:00:43 +0000 [thread overview]
Message-ID: <87r59vas2c.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3d3lff3ma.fsf@unquote.localdomain> (Andy Wingo's message of "Fri, 25 Mar 2011 19:37:33 +0100")
Andy Wingo <wingo@pobox.com> writes:
> On Mon 21 Mar 2011 23:19, Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Following are 4 simple (I believe) patches that simplify the build.
>> Plus the one at the end (#5) that is only very loosely related to this,
>> because of its mentioning of the $GUILE variable, but I think is a
>> useful cleanup anyway.
>
> All sounds fine to me!
Thanks, I've pushed those then.
After doing that, I remembered that Jan had a query about
GUILE_FOR_BUILD, and we didn't yet reach a conclusion in that
conversation. Jan, please do follow up to that, and I will be happy to
revert any GUILE_FOR_BUILD-related changes if we conclude that that's
the right thing.
Regards,
Neil
prev parent reply other threads:[~2011-03-25 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 22:19 Some simple build simplification patches Neil Jerram
2011-03-21 22:19 ` [PATCH 1/5] Remove unused definition of preinstguiletool Neil Jerram
2011-03-21 22:19 ` [PATCH 2/5] GUILE_FOR_BUILD is only needed by meta/guile.in, not by Makefiles Neil Jerram
2011-03-21 22:19 ` [PATCH 3/5] Make explicit that GUILE_FOR_BUILD is only used when cross-compiling Neil Jerram
2011-03-21 22:19 ` [PATCH 4/5] Inline the effect of am/pre-inst-guile Neil Jerram
2011-03-22 20:46 ` Jan Nieuwenhuizen
2011-03-22 22:08 ` Neil Jerram
2011-03-21 22:19 ` [PATCH 5/5] Remove statements about scripts/* that are no longer true Neil Jerram
2011-03-25 18:37 ` Some simple build simplification patches Andy Wingo
2011-03-25 20:00 ` Neil Jerram [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r59vas2c.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).