From users-return-1802-apmail-buildr-users-archive=buildr.apache.org@buildr.apache.org Mon Nov 16 15:22:36 2009 Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 51018 invoked from network); 16 Nov 2009 15:22:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Nov 2009 15:22:35 -0000 Received: (qmail 16744 invoked by uid 500); 16 Nov 2009 15:22:35 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 16709 invoked by uid 500); 16 Nov 2009 15:22:35 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 16670 invoked by uid 99); 16 Nov 2009 15:22:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2009 15:22:35 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of djspiewak@gmail.com designates 209.85.160.58 as permitted sender) Received: from [209.85.160.58] (HELO mail-pw0-f58.google.com) (209.85.160.58) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2009 15:22:33 +0000 Received: by pwi21 with SMTP id 21so4598680pwi.37 for ; Mon, 16 Nov 2009 07:22:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=M+jDuk23B6urXgjoac3Fsi2HVrjK4vPbazLHbQ8fFrs=; b=McUsczERnHuJfN06+3bP1Nh6w02WsPkjgfHOrc7YcrXxFZXGhyqWyxpEbFYs6NTtJX uphocHskfn1k2MKicZDduCrPqdKjHAHkq2hWZuojAQmW8nLbxggnQjrr48b+HJDBUI20 rOUbViKba7iWzSyRT13D3hnD7Ac2abYMlarTw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=QqC3pEImQia+77zN4WgDfpzy+phCNo7XAHJ9q4nk0Z3HuyC5Ft2ekPAlslUUg7ipEb /wvFjH1WQ6Gzd9yqBK+HrGD3wR6GztcZDfu3HA7dKtLTZga685NKAOaad/7lP3jhFAeN PJgoo+HJNUGsWvtsEdfciDOXN5fEVlgZu1e1I= MIME-Version: 1.0 Received: by 10.143.24.41 with SMTP id b41mr853442wfj.238.1258384933062; Mon, 16 Nov 2009 07:22:13 -0800 (PST) In-Reply-To: References: <4dcd15a90911101404w732c2d58t1a9a6c1b1aebbcb2@mail.gmail.com> <4dcd15a90911101442u19ff681ax1c7e7ad0e4446e30@mail.gmail.com> <7614AD53-F71F-4F98-96E7-2EC7623115BC@gmail.com> <4dcd15a90911101459s37de4337n5b28341960f8d142@mail.gmail.com> <4dcd15a90911101616g360befe0o15b1c8997a85cb86@mail.gmail.com> <4c1d6a900911101756u6d1df9c2h7d910de530c96533@mail.gmail.com> From: Daniel Spiewak Date: Mon, 16 Nov 2009 09:21:53 -0600 Message-ID: <5c99d0330911160721k3066a874k6fd150170248db31@mail.gmail.com> Subject: Re: Bundled Buildr + JRuby distribution To: users@buildr.apache.org Cc: dev@buildr.apache.org Content-Type: multipart/alternative; boundary=001636e1f81fed09bc04787e9234 --001636e1f81fed09bc04787e9234 Content-Type: text/plain; charset=UTF-8 I forgot about that. Our JRuby code does require jruby-ffi. Is it possible to bundle the appropriate native libs within a JRuby distribution? Another thing to consider is that JRuby does have a jar-complete distribution which is a little easier to manage. We would have to write a separate buildr script just for that distribution, but it might be an overall win in terms of manageability. Daniel On Mon, Nov 16, 2009 at 9:19 AM, Greg Lucas wrote: > Thanks for putting this together Alex. > > I've been trying it out with our continuous integration system in order to > build on multiple Linux machines. I'm getting: > > /opt/tools/buildr-1.3.5-jruby-1.4.0/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > `require': Could not load FFI Provider: FFI not available: > /tmp/jffi60799.tmp: Can't load AMD 64-bit .so on a AMD 64-bit platform > (LoadError) > > Has anyone seen this? > > -- > Greg Lucas > --001636e1f81fed09bc04787e9234--