Re: Supported GnuTLS/glib/libgcrypt versions?

[Anders Broman <a.broman58 () gmail com>]

Den 15 okt 2015 19:43 skrev "Jeff Morriss" <jeff.morriss.ws () gmail com>:
> On 10/14/15 14:25, Peter Wu wrote:
> > On Mon, Oct 12, 2015 at 02:02:18PM -0400, Jeff Morriss wrote:
> > > But you do raise a good point: I should start doing test compiles of
the 2.0
> > > rc on RHEL 6.  I hadn't realized my users would have to continue using
the
> > > Gtk+ GUI.  Too bad...
> >
> >
> > I have started testing with cmake + CentOS 6, it is not doing bad. At
> > least these fixes are needed to fix the build:
> > https://code.wireshark.org/review/10916
> > https://code.wireshark.org/review/11041
>
>
> Funny, I actually didn't have any problems (once I updated my
(customized) RPM spec file with some of the changes from master).  But
rpmbuild is using autotools and building from the source tarball.
> > > > Speaking of bumping library versions, can we also bump the glib and
> > > > libgcrypt versions? Current versions are glib 2.14 and libgcrypt
> > > > 1.1.92. If we could go to glib 2.28 (Feb 2011) and gcrypt 1.5.0 (Jun
> > > > 2011), it would enable us to use newer functions such as
> > > > g_list_free_full.
> > >
> > >
> > > The glib change is OK for me (for RHEL 6) but it does appear to mean
we'd
> > > lose support for all SLES versions; I'd tend to think that would be a
bad
> > > thing.
> >
> >
> > I made a mistake, SLES 12 includes glib2 2.38.2, the wiki is now updated
> > to reflect that. For now the minimum gcrypt version is 1.4.2
> > (https://code.wireshark.org/review/11043).
>
>
> So bumping the glib version means we'd lose SLES 11.  Given how recent
(for an enterprise version) SLES 12 is I'd guess there are still a lot of
SLES 11 users out there.
>
I'm need to build on SLES11 so please don't break that.

>
___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe