From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: ceph-devel@vger.kernel.org
Cc: Gary Lowell <gary.lowell@inktank.com>,
Noah Watkins <jayhawk@cs.ucsc.edu>, Sage Weil <sage@inktank.com>
Subject: Re: [PATCH] configure.ac: check for org.junit.rules.ExternalResource
Date: Thu, 10 Jan 2013 08:55:31 +0100 [thread overview]
Message-ID: <50EE73F3.6050705@bisect.de> (raw)
In-Reply-To: <BB8FDF50-D01D-4B4A-A201-8AEA43FFFA2D@inktank.com>
Am 10.01.2013 05:32, schrieb Gary Lowell:
> I have this patch, and the ones from Friday in the wip-rpm-update branch. Everything looks good except that we have the following new warning from configure:
>
> ….
> checking for kaffe... no
> checking for java... java
> checking for uudecode... no
> WARNING: configure: I have to compile Test.class from scratch
> checking for gcj... no
> checking for guavac... no
> checking for jikes… no
> ….
>
> This may have to do with something in our build environment.
I assume you have no uudecode installed. It should be part of sharutils
(http://www.gnu.org/software/sharutils/)
Regards,
Danny
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-01-10 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 21:35 [PATCH] configure.ac: check for org.junit.rules.ExternalResource Danny Al-Gaaf
2013-01-09 21:35 ` Danny Al-Gaaf
2013-01-09 21:54 ` Noah Watkins
2013-01-10 4:32 ` Gary Lowell
2013-01-10 7:55 ` Danny Al-Gaaf [this message]
2013-01-11 5:13 ` Gary Lowell
2013-01-12 16:36 ` Noah Watkins
2013-01-15 9:04 ` James Page
2013-01-15 9:32 ` Danny Al-Gaaf
2013-01-15 14:55 ` Noah Watkins
2013-01-15 17:36 ` Gregory Farnum
2013-01-12 21:59 ` Danny Al-Gaaf
2013-01-14 20:41 ` Gary Lowell
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=50EE73F3.6050705@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=jayhawk@cs.ucsc.edu \
--cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.