Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Sep 2013 05:35:15 -0500
From:      Bryan Drewery <bryan@shatow.net>
To:        Big Lebowski <spankthespam@gmail.com>
Cc:        freebsd-ports <freebsd-ports@freebsd.org>
Subject:   Re: Help in testing Basho Riak port
Message-ID:  <1BF2EE0F-FB81-48C4-8043-E5B5C8B1566C@shatow.net>
In-Reply-To: <CAHcXP%2BdNahiHjdKkwYOHhF1O4R6g=2ssEq-=eazvBnUHxfwnrg@mail.gmail.com>
References:  <CAHcXP%2Be15099FK7ch3NhktHXJKcSL%2BstANhSSZ-zwfOtB6%2BLfA@mail.gmail.com> <20130920203737.GE74496@admin.xzibition.com> <CAHcXP%2BdjP3gTxDSQ4DddingT8YbDaVLSp3HGL1sQahBxU1cG9w@mail.gmail.com> <CAHcXP%2Beqn4izzfH9SCL_Qvs4Zv9jARKsa=nTRHsX8r_RunxrFQ@mail.gmail.com> <523E1D31.5060302@shatow.net> <CAHcXP%2BdNahiHjdKkwYOHhF1O4R6g=2ssEq-=eazvBnUHxfwnrg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Yes, to commit it, it needs to build.

Sent from my iPhone

> On Sep 22, 2013, at 4:43, Big Lebowski <spankthespam@gmail.com> wrote:
>=20
>> On Sat, Sep 21, 2013 at 11:26 PM, Bryan Drewery <bryan@shatow.net> 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 <bryan@shatow.net> 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::<unnamed>::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"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1BF2EE0F-FB81-48C4-8043-E5B5C8B1566C>