From: Stelian Ionescu <sionescu@cddr.org>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] Weblocks build failure
Date: Wed, 17 Nov 2010 13:14:42 +0100 [thread overview]
Message-ID: <1289996082.9522.0.camel@blackhole> (raw)
In-Reply-To: <AANLkTinhFfGL7dNqPz8TMXNBjHRAOQxX6ZKmWnVZYNMu@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Tue, 2010-11-16 at 17:42 -0600, Mike Summers wrote:
> One more build issue (using the current overlay), looks like kmrcl is
> looking for an older (1.102) version... only 1.103 is
> on http://files.b9.com/kmrcl/
Fixed, thanks :)
--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-17 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 17:35 [gentoo-lisp] Weblocks build failure Mike Summers
2010-11-16 18:15 ` Stelian Ionescu
2010-11-16 22:31 ` Mike Summers
2010-11-16 23:42 ` Mike Summers
2010-11-17 12:14 ` Stelian Ionescu [this message]
2010-11-17 17:04 ` Mike Summers
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=1289996082.9522.0.camel@blackhole \
--to=sionescu@cddr.org \
--cc=gentoo-lisp@lists.gentoo.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