Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <1734020187.429001269332907329.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Mar 2010 08:28:27 +0000 (UTC)
From: "Mark Hindess (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-6480) FreeBSD comparability: Location of
 malloc
In-Reply-To: <1916013441.426411269324627221.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848612#action_12848612 ] 

Mark Hindess commented on HARMONY-6480:
---------------------------------------

According to the malloc(3) man page, <stdlib.h> is correct on linux too.  I have a vague memory of breaking the windows build fixing some of these in classlib in the past so I think the correct fix is to do:

#ifdef _WIN32
#include <malloc.h>
#endif


> FreeBSD comparability: Location of malloc
> -----------------------------------------
>
>                 Key: HARMONY-6480
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6480
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: operating system :  FreeBSD [8.0p2]
> CPU architecture :  x86
> ant os name/arch :  FreeBSD/i386
> hosting Java     :  1.6.0_07 (The FreeBSD Foundation)
>            Reporter: Mark Eschbach
>            Priority: Minor
>         Attachments: fbsd-malloc-stdlib-patch.diff
>
>
> While attempting to run the included unit tests (attempting to track down another issue), I got an error from a test header file.  Apparently the standard library declaration for malloc(size_t) and friends are now in <stdlib.h>, or where they should be.  On FreeBSD including <malloc.h> will generate a compiler error (via preprocessor), and directs you to include <stdlib.h>.  Those governing the header files are adamant about the modifications.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.