Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Malkowski <eric@bvwireless.net>
To: buildroot@busybox.net
Subject: [Buildroot] My tweeks/fixes to get a mostly default system working w/ 2.6.23.1 kernel
Date: Mon, 12 Nov 2007 13:36:39 -0500 (EST)	[thread overview]
Message-ID: <60190.74.94.141.114.1194892599.squirrel@bvwireless.net> (raw)

Where is your tree located?

I checked branches, tags etc. in svn and couldn't see per developer trees
or anything that looked obvious to me...

In looking at the trunk I see this in package/makefile.in:

# XXX: FIXME: We would need to grab MALLOC_GLIBC_COMPAT from the
uClibc.config
# Including it doesn't seem wise, grepping is ugly.. Suggestions?
# Does malloc return live pointer for malloc(0) ?
ifeq ($(MALLOC_GLIBC_COMPAT),y)
BR2_AC_CV_FUNC_MALLOC_0_NONNULL=ac_cv_func_malloc_0_nonnull=yes \
				gl_cv_func_malloc_0_nonnull=yes \
				ac_cv_func_realloc_0_nonnull=yes
else
BR2_AC_CV_FUNC_MALLOC_0_NONNULL=ac_cv_func_malloc_0_nonnull=no \
				gl_cv_func_malloc_0_nonnull=no \
				ac_cv_func_realloc_0_nonnull=no
endif

I have MALLOC_GLIBC_COMPAT=y in my uclibc config yet these options don't
seem to make it into my TARGET_CONFIGURE_OPTS or TARGET_CONFIGURE_ARGS.

perhaps your tree does something better...  if so I'll snag it once I know
where your tree is.  So far only quagga ran into this problem.

Thanks for the reply.

-Eric

             reply	other threads:[~2007-11-12 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 18:36 Eric Malkowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-12 15:29 [Buildroot] My tweeks/fixes to get a mostly default system working w/ 2.6.23.1 kernel Eric Malkowski
2007-11-12 18:02 ` Bernhard Fischer

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=60190.74.94.141.114.1194892599.squirrel@bvwireless.net \
    --to=eric@bvwireless.net \
    --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