Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Valenzuela <jvalenzuela@dspfl.com>
To: buildroot@busybox.net
Subject: [Buildroot] malloc/rpl_malloc
Date: Wed, 21 May 2008 11:56:55 -0400	[thread overview]
Message-ID: <48344647.4020503@dspfl.com> (raw)
In-Reply-To: <326f33790805201145r785b06hcbec87b888ff8a76@mail.gmail.com>

I'm trying to compile some packages of my own and am coming up with some 
problems at link time with the malloc function. According to the uclibc 
FAQ, MALLOC_GLIBC_COMPAT should be enabled in order for the configure 
script not to define malloc() to rpl_malloc(). I went to the 
toolchain_build_ARCH/uClibc-0.9.29 and did a 'make menuconfig'. This 
option under 'General Library Settings->Malloc returns live pointer for 
malloc(0)' was indeed enabled, causing me to believe that the uclibc in 
my buildroot toolchain is already correctly set.

Now going back to the build_ARCH/MY_PACKAGE directory and checking the 
config.h, HAVE_MALLOC has been defined as 0 and the results in 
config.log shows that the configure script didn't think malloc() was 
compatible with the GNU libc version.



Jason Valenzuela

      parent reply	other threads:[~2008-05-21 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 22:24 [Buildroot] Bootloaders Jason Valenzuela
2008-05-20  0:34 ` Arun Reddy
2008-05-20 17:45   ` Jason Valenzuela
2008-05-20 18:31     ` Arun Reddy
2008-05-20 18:32       ` Arun Reddy
2008-05-20 18:38       ` Jason Valenzuela
2008-05-20 18:45         ` Arun Reddy
2008-05-20 18:51           ` Jason Valenzuela
2008-05-20 20:10           ` Jason Valenzuela
2008-05-20 20:43             ` Arun Reddy
2008-05-20 20:48               ` Jason Valenzuela
2008-05-21 15:56           ` Jason Valenzuela [this message]

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=48344647.4020503@dspfl.com \
    --to=jvalenzuela@dspfl.com \
    --cc=buildroot@busybox.net \
    /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