Re: Compiling for FreeBSD

From: Sage Weil <sage@newdream.net>
To: Willem Jan Withagen <wjw@digiware.nl>
Cc: Mykola Golub <mgolub@mirantis.com>,
	"Yan, Zheng" <ukernel@gmail.com>, Haomai Wang <haomai@xsky.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Compiling for FreeBSD
Date: Tue, 1 Dec 2015 05:30:01 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1512010529280.19170@cobra.newdream.net> (raw)
In-Reply-To: <565D7FA8.3010301@digiware.nl>

On Tue, 1 Dec 2015, Willem Jan Withagen wrote:
> On 30-11-2015 14:21, Sage Weil wrote:
> > The problem with all of the porting code in general is that it is doomed
> > to break later on if we don't have (at least) ongoing build tests.  In
> > order for a FreeBSD or OSX port to continue working we need VMs that run
> > either gitbuilder or a jenkins job or similar so that we can tell when it
> > breaks.
> > 
> > If someone is willing to run a VM somewhere to do this we can pretty
> > easily stick it on the gitbuilder page at
> > 
> > 	http://ceph.com/gitbuilder.cgi
> 
> 
> Hi Sage,
> 
> Could you give some pointers as to where to start running the tests.
> I see a lot of "basic" tests to see if the platform is actually conformant.
> 
> So before plunging into running ceph-mon and stuff, it would perhaps be
> better to actually run (parts of) the basic required tests..

I would start with 'make check' from src/... that's what we'd actually 
want the gitbuilder to do.

sage