From owner-freebsd-ports@FreeBSD.ORG Sun Sep 22 10:35:26 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A420718 for ; Sun, 22 Sep 2013 10:35:26 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DC80E2749 for ; Sun, 22 Sep 2013 10:35:25 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=references :mime-version:in-reply-to:content-type:content-transfer-encoding :message-id:cc:from:subject:date:to; q=dns; s=sweb; b=2eU/F71X13 x6qOoexjKcJjDT5wH1dFTpN01JTb2+U8MEh2WVDIEktLTPBos+QmEj4G9GlUk9gU AoTt8XSj8q8hWP4jG2MY+ini1Zsdvmf4IawXVGvbTR9NRgIku0Qtx+7hAOejrl3C 6aZTE1tiY3sV2dhkSnj4pGGU/TvLTGufw= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=references :mime-version:in-reply-to:content-type:content-transfer-encoding :message-id:cc:from:subject:date:to; s=sweb; bh=sH8B/oiUjnAe8lFS bwDPF5fjAt+7e/IHKLji4SSSaik=; b=rBgQCUbFcXLA3ZEjDjWfB4RhBHRbVl5J D7UBohUBD889arfaEDINGiV+yA54LYlyTuwr2tNMqoxyuZ6vT446ijWbUxjaKHTp PBOowOEErI/0XjRkVS45ENfpdgDaVWj7aPCslaG6ybizBXJlQqVhIK1rOuy4gM9P /O3XhjOtlP0= Received: (qmail 60758 invoked from network); 22 Sep 2013 05:35:22 -0500 Received: from unknown (HELO ?10.10.1.203?) (bryan@shatow.net@10.10.1.203) by sweb.xzibition.com with ESMTPA; 22 Sep 2013 05:35:22 -0500 References: <20130920203737.GE74496@admin.xzibition.com> <523E1D31.5060302@shatow.net> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <1BF2EE0F-FB81-48C4-8043-E5B5C8B1566C@shatow.net> X-Mailer: iPhone Mail (11A465) From: Bryan Drewery Subject: Re: Help in testing Basho Riak port Date: Sun, 22 Sep 2013 05:35:15 -0500 To: Big Lebowski Cc: freebsd-ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 10:35:26 -0000 Yes, to commit it, it needs to build. Sent from my iPhone > On Sep 22, 2013, at 4:43, Big Lebowski wrote: >=20 >> On Sat, Sep 21, 2013 at 11:26 PM, Bryan Drewery wrote:= >>=20 >>> On 9/21/2013 5:08 PM, Big Lebowski wrote: >>> Hi, >>>=20 >>> Thanks for your comments, see mine below. >>>=20 >>>=20 >>>> On Fri, Sep 20, 2013 at 9:37 PM, Bryan Drewery wrote= : >>>>=20 >>>>> On Fri, Sep 20, 2013 at 06:57:52PM +0100, Big Lebowski wrote: >>>>> Hi list! >>>>>=20 >>>>> I've been working for couple last days on porting Basho Riak database >>>>> (latest version 1.4.2) and finally I think it is ready to be presented= : >>>>> https://www.dropbox.com/s/2ztu2bdiip1u2un/riak.tgz >>>>=20 >>>> MASTER_SITES=3D >>>> http://s3.amazonaws.com/downloads.basho.com/riak/1.4/1.4.2/ \ >>>>=20 >>>> http://downloads.basho.com.s3.amazonaws.com/riak/1.4/1.4.2/ >>>>=20 >>>> Use ${PORTVERSION} instead of 1.4.2 >>>=20 >>> Fixed. >>>=20 >>>=20 >>>>=20 >>>> USES=3D ${GMAKE} >>>>=20 >>>> Use 'gmake', not ${GMAKE} here. >>>=20 >>> Fixed. >>>=20 >>>=20 >>>>=20 >>>> Fails to build on 8.3 i386: >>>>=20 >>>> db/version_set.cc:59: warning: this decimal constant is unsigned only >> in >>>> ISO C90 >>>> db/version_set.cc:59: warning: this decimal constant is unsigned only >> in >>>> ISO C90 >>>> db/version_set.cc:60: error: integer constant is too large for 'long' >>>> type >>>> db/version_set.cc:60: error: integer constant is too large for 'long' >>>> type >>>> db/version_set.cc:61: error: integer constant is too large for 'long' >>>> type >>>> db/version_set.cc:61: error: integer constant is too large for 'long' >>>> type >>>> db/version_set.cc:62: error: integer constant is too large for 'long' >>>> type >>>> db/version_set.cc:62: error: integer constant is too large for 'long' >>>> type >>>> table/filter_block.cc: In member function 'bool >>>> leveldb::FilterBlockReader::KeyMayMatch(uint64_t, const >> leveldb::Slice&)': >>>> table/filter_block.cc:112: warning: comparison between signed and >>>> unsigned integer expressions >>>> util/env_posix.cc: In constructor >>>> 'leveldb::::PosixEnv::PosixEnv()': >>>> util/env_posix.cc:788: warning: unused variable 'ts' >>>>=20 >>>>=20 >>>> gmake[1]: *** [libleveldb.so.1.9] Error 1 >>>> gmake[1]: Leaving directory >> `/wrkdirs/usr/ports/databases/riak/work/riak-1.4.2/deps/eleveldb/c_src/le= veldb' >>>=20 >>> Can you provide any more details on your testing environment, like 32/64= >>> bit, GCC version, any compile optimizations in make.conf and so on? >>> Unfortunately, I dont have any 8.x machine to test it, so I wasnt able t= o >>> see that before. Could you also try to build it on 8.3 using CLANG? >>=20 >> 8.3 i386 (32 bit). GCC 4.2. This error is of too much data for 32bit >> variable. Clang won't help. >>=20 >> Here is the issue upstream as well with a recommended fix and a SO >> explaining more: >>=20 >> https://github.com/basho/leveldb/issues/87 >>=20 >> http://stackoverflow.com/questions/5541560/integer-constant-is-too-large-= for-long-type >=20 >=20 > It seems like its a bug in Riak itself, and I wonder if it should be me, > who's fixing it? Given the fact, the fix have not been accepted for two > months now, that it is (as its author writes) still giving warnings, and > given that I've zero knowledge of C, does it make sense to make this > unaccepted, uncomplete and unknown code a patch for the port? If there > would be Nginx error prohibiting building it on certain enviroments, would= > Nginx port owner be fixing it, or should it rather be a Nginx authors > problem? >=20 > B. >=20 >=20 >>=20 >>=20 >>>=20 >>>=20 >>>>=20 >>>>=20 >>>> Instead of bsd.port.pre.mk ... bsd.port.post.mk, use >> bsd.port.options.mk... >>>> bsd.port.mk. Although, it doesn't look like you even need that. Just >> use >>>> bsd.port.mk at the end, no 2nd include. >>>=20 >>> I dont think I can get away with only using bsd.port.mk - I've tried >> that, >>> and the port fails miserably, somwhere on the level of interpretation of= >>> the Makefile, where it is missing many macros, so I've stayed with two >>> includes. >>>=20 >>>=20 >>>>=20 >>>>=20 >>>> Otherwise, good work. I will pkg-build test any updates you send out. >>>=20 >>> Thanks, great to hear that. Latest version will be posted in response to= >> my >>> original message. >>>=20 >>> B. >>>=20 >>>=20 >>>>=20 >>>>>=20 >>>>> Please, grab the port and test it on anything you can, break it in any= >>>> way >>>>> possible, and comment on anything you see that's been done wrong - I a= m >>>>> open to any suggestion on how to make it worthy candidate for send-pr >>>> with >>>>> port submission. >>>>>=20 >>>>> Any help will be highly appreciated and will motivate me to port more >>>> cool >>>>> software to FreeBSD! ;) >>>>>=20 >>>>> Kind regards, >>>>> S. >>>>> _______________________________________________ >>>>> freebsd-ports@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>>>> To unsubscribe, send any mail to " >> freebsd-ports-unsubscribe@freebsd.org" >>> _______________________________________________ >>> freebsd-ports@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"= > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"