public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Fix a building error.
Date: Fri, 14 Jan 2011 16:46:08 -0500	[thread overview]
Message-ID: <201101141646.09224.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTik8_=dyDFacvbJs8t6E1iaCmAgUEKOSRtv9fepZ@mail.gmail.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 1504 bytes --]

On Friday, January 14, 2011 16:33:38 Garrett Cooper wrote:
> On Fri, Jan 14, 2011 at 1:24 PM, Mike Frysinger wrote:
> > On Friday, January 14, 2011 04:48:33 Peng Haitao wrote:
> >>  testcases/kernel/syscalls/mallopt/mallopt01.c |    1 +
> > 
> > please use descriptive subjects in your patches.  this really should be
> > something like:
> >        mallopt01: fix build error due to xxxx
> > 
> >> --- a/testcases/kernel/syscalls/mallopt/mallopt01.c
> >> +++ b/testcases/kernel/syscalls/mallopt/mallopt01.c
> >> @@ -37,6 +37,7 @@
> >>  #ifdef CONFIG_COLDFIRE
> >>  #define __MALLOC_STANDARD__
> >>  #endif
> >> +#include <malloc.h>
> > 
> > umm, no.  malloc.h is a dead header file and nothing should be including
> > it.
> 
>     It is exposing extra junk in this case that isn't available from
> stdlib.h, which unfortunately the test uses. I fixed the build error
> for now, but maybe someone upstream should be informed that this
> header needs to die a painful death, because all contemporary
> documentation says that you need to include stdlib.h, not malloc.h
> when working with malloc(3). I was reminded of this recently because I
> built some stuff on FreeBSD and FreeBSD has a nice #warning about this
> deprecation.

err, right.  we're using mallopt() here and not malloc().  the former is not 
part of POSIX which means it should not be in stdlib.h.  i dont believe it is 
being deprecated on the GNU side, so we dont want to go killing off the tests.
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 372 bytes --]

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-01-14 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  9:48 [LTP] [PATCH] Fix a building error Peng Haitao
2011-01-14 12:58 ` Cyril Hrubis
2011-01-14 21:24 ` Mike Frysinger
2011-01-14 21:33   ` Garrett Cooper
2011-01-14 21:46     ` Mike Frysinger [this message]
2011-01-14 21:52       ` Garrett Cooper
2011-01-14 22:12         ` Mike Frysinger
  -- strict thread matches above, loose matches on Subject: below --
2011-01-14  9:31 Peng Haitao
2011-01-28  8:24 ` Peng Haitao
2011-02-14  9:45   ` Peng Haitao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201101141646.09224.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox