:ffilz...@mindspring.com> >
> *Cc:* nfs-ganesha-devel@lists.sourceforge.net
> <mailto:nfs-ganesha-devel@lists.sourceforge.net>
> *Subject:* Re: [Nfs-ganesha-devel] Conditional compile failures
>
>
>
> If we make those as some kind of cmake build configs, then deve
ts issuing Verify-1. If there’s a build option set someone thinks
> > might be relevant that we don’t succeed in compiling for, we need to fix
> > it immediately.
> >
> >
> >
> > Frank
> >
> >
> >
> > *From:*Malahal Naineni [mailto:mala...@gmail.co
Sent:* Monday, May 8, 2017 9:01 AM
> *To:* Frank Filz
> *Cc:* nfs-ganesha-devel@lists.sourceforge.net
> *Subject:* Re: [Nfs-ganesha-devel] Conditional compile failures
>
>
>
> If we make those as some kind of cmake build configs, then developers
> can also build those combinati
Filz
Cc: nfs-ganesha-devel@lists.sourceforge.net
Subject: Re: [Nfs-ganesha-devel] Conditional compile failures
If we make those as some kind of cmake build configs, then developers can also
build those combinations before we push our code for review. Maybe, have
randconfig as well for
If we make those as some kind of cmake build configs, then developers can
also build those combinations before we push our code for review. Maybe,
have randconfig as well for developers to use but don't enforce in CI for
the time being (until it has some run time!)
Regards, malahal.
On Mon, May 8
