thx for the support!
by the way same problem also occurs in review
http://review.gluster.org/#/c/14045/
br, vangelis
On Tue, Apr 19, 2016 at 5:01 PM, Michael Scherer wrote:
> Le mardi 19 avril 2016 à 09:58 -0400, Jeff Darcy a écrit :
>> > So can a workable solution be
Le lundi 04 avril 2016 à 08:54 -0400, Jeff Darcy a écrit :
> > Once this was done, I pushed to use the regular upstream change,
> > something that was not done before since the local change broke
> > automation to deploy test suite on Freebsd.
>
> It looks like we have two options here:
>
> (1)
> Once this was done, I pushed to use the regular upstream change,
> something that was not done before since the local change broke
> automation to deploy test suite on Freebsd.
It looks like we have two options here:
(1) Fix configure so that it accurately detects whether the
system can/should
Le samedi 02 avril 2016 à 16:36 +0200, Niels de Vos a écrit :
> On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote:
> > > IIRC, this happens because in the build job use "--enable-bd-xlator"
> > > option while configure
> >
> > I came to the same conclusion, and set --enable-bd-xlator=no
On Sat, Apr 02, 2016 at 11:04:48AM -0400, Jeff Darcy wrote:
> > Please make sure that this change also gets included in the repository:
> >
> > https://github.com/gluster/glusterfs-patch-acceptance-tests
>
> Looks like we're getting a bit of a queue there. Who can merge some of
> these?
I
- Original Message -
> On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote:
> > > IIRC, this happens because in the build job use "--enable-bd-xlator"
> > > option while configure
> >
> > I came to the same conclusion, and set --enable-bd-xlator=no on the
> > slave. I also had
On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote:
> > IIRC, this happens because in the build job use "--enable-bd-xlator"
> > option while configure
>
> I came to the same conclusion, and set --enable-bd-xlator=no on the
> slave. I also had to remove -Werror because that was also