unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: guile-devel@gnu.org
Subject: Some simple build simplification patches
Date: Mon, 21 Mar 2011 22:19:16 +0000	[thread overview]
Message-ID: <1300745961-4287-1-git-send-email-neil@ossau.uklinux.net> (raw)


Hi all,

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.

For me, these are part of working towards understanding and simplifying
cross-compilation, and the next step is seeing if we really need the
setting and using (in a few places only) of the $GUILE variable.

Any comments / objections?

Thanks,
    Neil


PS. It's also my first try of using git send-email to send patches to
the Guile list, so here's hoping that that works out...



             reply	other threads:[~2011-03-21 22:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 22:19 Neil Jerram [this message]
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

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=1300745961-4287-1-git-send-email-neil@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.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).