From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: release_1-9-12
Date: Thu, 09 Sep 2010 11:45:10 +0200 [thread overview]
Message-ID: <8739tjl07t.fsf@gnu.org> (raw)
In-Reply-To: 20100909054202.GB31305@yeeloong
Hi!
rixed@happyleptic.org writes:
> I tested it on the various hardware around and the only problem I
> encountered was that on a busybox/ARM some Makefiles are relying on gnu
> touch (using options -r and -t) which was not available under the name
> "touch" but gtouch (installed separately from busybox).
I think the ‘touch -r’ invocations are no longer needed, not sure about
the others. Andy?
> This could have been simplier with a $(TOUCH) make variable. Idealy,
> configure should have tried to find a suitable touch program but I
> don't think there is already a macro for that.
Yes, we could do something like that.
> Anyway, congrats for this release. As a user that's very pleasant that
> guile seams to progress so fast these days.
Thanks for the report & support!
Ludo’.
next prev parent reply other threads:[~2010-09-09 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 5:42 release_1-9-12 rixed
2010-09-09 9:45 ` Ludovic Courtès [this message]
2010-09-10 9:02 ` release_1-9-12 Andy Wingo
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=8739tjl07t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).