[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] compile error location of malloc.h

From: Juergen Sauermann
Subject: Re: [Bug-apl] compile error location of malloc.h
Date: Mon, 29 Aug 2016 11:43:38 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0


thanks, fixed in SVN 794.

I went for <stdlib.h> because that is what the malloc manpage says.

Currently <stdlib.h> is aleady #included by Common.hh but that may change.
Therefore I believe that it is cleaner to #include it again.

/// Jürgen

On 08/29/2016 07:21 AM, Elias Mårtenson wrote:
They are, but if they are not found in the local directory, they are also searched for in the system directories.

That said, in this case using the angle brackets is the correct thing to use.

On 29 August 2016 at 13:08, Christian Robert <address@hidden> wrote:
that should read:

#include <malloc.h>

or better

#include <stdlib.h>

things in double quotes are searched in local directory by default and not in system.


On 2016-08-28 23:42, Xiao-Yong Jin wrote:
    LApack.cc:21:20: fatal error: malloc.h: No such file or directory
     #include "malloc.h"
    compilation terminated.

Under OS X, it’s in /usr/include/malloc/malloc.h

Is it actually needed?  The code compiles fine without the #include.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]