<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] openssl regression
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20openssl%20regression&In-Reply-To=%3CCACB12RFyVN-Du7UsuACqw0LJZ2FMuGFQFLyf9yxjmaASJuk_-Q%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016367.html">
<LINK REL="Next" HREF="016369.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] openssl regression</H1>
<B>Sander Lepik</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20openssl%20regression&In-Reply-To=%3CCACB12RFyVN-Du7UsuACqw0LJZ2FMuGFQFLyf9yxjmaASJuk_-Q%40mail.gmail.com%3E"
TITLE="[Mageia-dev] openssl regression">sander.lepik at eesti.ee
</A><BR>
<I>Mon Jun 11 12:44:36 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016367.html">[Mageia-dev] openssl regression
</A></li>
<LI>Next message: <A HREF="016369.html">[Mageia-dev] openssl regression
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16368">[ date ]</a>
<a href="thread.html#16368">[ thread ]</a>
<a href="subject.html#16368">[ subject ]</a>
<a href="author.html#16368">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Jun 11, 2012 1:14 PM, "Colin Guthrie" <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
><i>
</I>><i> 'Twas brillig, and Guillaume Rousse at 11/06/12 10:19 did gyre and gimble:
</I>><i> > Le 11/06/2012 09:56, Colin Guthrie a écrit :
</I>><i> >> Well it the .so name does not change then it *should* be ABI
</I>compatible.
><i> >> It seems in this case it's only API compatible but that doesn't rule
</I>out
><i> >> certain values, macros or flags changing such that everything needs a
</I>><i> >> recompile.
</I>><i> > Just rebuilding openssl with different build options already triggered
</I>><i> > such kind of issues. I remember adding SNI support broke ntp in the
</I>><i> > past, until this last package was rebuilt. The safe way should be to
</I>><i> > rebuild everything right now, but given than almost everything in the
</I>><i> > distribution uses this library, I think just letting normal update flow
</I>><i> > should be enough, unless actual problems are found.
</I>><i>
</I>><i> Probably true and I think we should ensure that a full rebuild is done
</I>><i> before the beta cycle anwyay. We did moot this for mga2 but it was
</I>><i> deemed (correctly IMO) too late to start messing with that.
</I>><i>
</I>><i> But until then a full rebuild is likely overkill.
</I>What about gcc 4.7? I think we should switch to that one as well. And then
rebuild is needed anyway. So full rebuild at the moment is probably not the
best idea.
--
Sander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20120611/2ee669f4/attachment.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016367.html">[Mageia-dev] openssl regression
</A></li>
<LI>Next message: <A HREF="016369.html">[Mageia-dev] openssl regression
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16368">[ date ]</a>
<a href="thread.html#16368">[ thread ]</a>
<a href="subject.html#16368">[ subject ]</a>
<a href="author.html#16368">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>