[prev in list] [next in list] [prev in thread] [next in thread] 

List:       autoconf-bug
Subject:    Re: Error message for memory.h
From:       Chongke Bi <bichongke () gmail ! com>
Date:       2015-09-10 1:31:29
Message-ID: CACMew60YA=JWp+SFKTbSHtQ2BfQ_Sa5J9-BaBtjr35uca_Sqjg () mail ! gmail ! com
[Download RAW message or body]

Dear Eric,

Thank you very much.

I have deleted memory.h from /usr/local/include.
It perfectly resolved my problem.

Thanks again.

Best regards,
Chongke



On Wed, Sep 9, 2015 at 11:25 PM, Eric Blake <eblake@redhat.com> wrote:

> On 09/09/2015 03:02 AM, Chongke Bi wrote:
> > Dear all,
> >
> > I got the following message,
> > could you please kindly help me?
> >
> >
> > Thank you very much in advance.
> >
> > Best regards,
> > Chongke
> >
> >
> -------------------------------------------------------------------------------------------------------
> > configure:5464: checking for memory.h
> > configure:5464: mpicc -c -g -O2  conftest.c >&5
> > In file included from conftest.c:50:0:
> > /usr/local/include/memory.h:4:19: fatal error: cstdlib: No such file or
> > directory
> >  #include <cstdlib>
> >                    ^
>
> Looks like you have installed some C++ package that pollutes the global
> include namespace into /usr/local/include. Figure out what package
> mistakenly dropped a memory.h there, and get rid of it.
>
> That said, <memory.h> is an obsolete header these days (you should be
> using <string.h> instead), so the fact that configure can't find a
> working <memory.h> shouldn't prevent your package from still compiling,
> if your package isn't relying on obsolete headers.
>
> --
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
>


-- 
Chongke BI<bichongke@gmail.com>

[prev in list] [next in list] [prev in thread] [next in thread]