On Jun 10, 2013, at 9:05 PM, Jeff Squyres wrote:
> That being said, that release note was for glibc 2.14. I just downloaded and
> built 2.17; it looks like a) the hooks are still there, and b) they're still
> installed by default.
Ah -- I see what happened. glibc marked the hook interfaces w
yes
On Tue, Jun 11, 2013 at 5:10 PM, Jeff Squyres (jsquyres) wrote:
> On Jun 11, 2013, at 9:37 AM, Mike Dubman wrote:
>
> > ubuntu12
> > fedora16
> >
> > the hooks are there, but marked as "deprecated"
>
> Does that mean they come up with a compiler warning?
>
>
> >
> > On Tue, Jun 11, 2013 at
On Jun 11, 2013, at 9:37 AM, Mike Dubman wrote:
> ubuntu12
> fedora16
>
> the hooks are there, but marked as "deprecated"
Does that mean they come up with a compiler warning?
>
> On Tue, Jun 11, 2013 at 4:05 AM, Jeff Squyres (jsquyres)
> wrote:
> On Jun 10, 2013, at 10:29 AM, "Barrett, Bri
ubuntu12
fedora16
the hooks are there, but marked as "deprecated"
On Tue, Jun 11, 2013 at 4:05 AM, Jeff Squyres (jsquyres) wrote:
> On Jun 10, 2013, at 10:29 AM, "Barrett, Brian W"
> wrote:
>
> > At least they've finally come to that conclusion. I look forward to not
> > shipping a memory al
On Jun 10, 2013, at 10:29 AM, "Barrett, Brian W" wrote:
> At least they've finally come to that conclusion. I look forward to not
> shipping a memory allocator with our communication library ;).
+1 on that.
That being said, that release note was for glibc 2.14. I just downloaded and
built 2
On 6/10/13 8:23 AM, "Jeff Squyres (jsquyres)" wrote:
>If you saw Mellanox's commit this morning, you noticed a comment about
>how the glibc malloc hooks are deprecated. I pinged Mike D. about this
>off-list, and he sent me the following reference from the glibc 2.14
>release notes at
>http://so
