From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libpng
Date: Wed, 29 Oct 2008 16:58:43 +0100 [thread overview]
Message-ID: <87ljw71jgs.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <C13DBBE85AD6974B85C118C35890CA5F13B20D9A20@EU1RDCRDC1WX029.exi.nxp.com> (Daniel J. Laird's message of "Wed\, 29 Oct 2008 16\:33\:18 +0100")
>>>>> "Daniel" == Daniel J Laird <daniel.j.laird@nxp.com> writes:
Daniel> The BR2_AC_CV_FUNC_MALLOC_0_NONNULL value seems to depend up a value called MALLOC_GLIBC_COMPAT. This is only set in the uClibC config files. This means GLIBC based external toolchains cant use this BR2_AC_CV_FUNC_MALLOC_0_NONNULL if they want it set to yes like libpng does.
Daniel> 1. We could add the calloc stuff
Daniel> 2. We could have
Daniel> ac_cv_have_decl_malloc=yes \
Daniel> gl_cv_func_malloc_0_nonnull=yes \
Daniel> ac_cv_func_malloc_0_nonnull=yes \
Daniel> ac_cv_func_calloc_0_nonnull=yes \
Daniel> ac_cv_func_realloc_0_nonnull=yes
Daniel> When using an external toolchain as well
Or provide an option to let the user set it to whatever their
toolchain does. I'm not familiar with the external toolchain stuff,
how's the other toolchain settins handled (largefile, locales, wchar,
..)?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-10-29 15:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 12:49 [Buildroot] svn commit: trunk/buildroot/package/libpng laird at uclibc.org
2008-10-29 13:53 ` Peter Korsgaard
2008-10-29 14:15 ` Daniel J Laird
2008-10-29 15:33 ` Daniel J Laird
2008-10-29 15:58 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 14:59 jacmet at uclibc.org
2009-02-12 12:17 jacmet at uclibc.org
2009-01-12 12:45 laird at uclibc.org
2008-10-06 15:11 jacmet at uclibc.org
2008-03-05 13:35 sjhill at uclibc.org
2008-03-05 14:02 ` Peter Korsgaard
2008-03-05 14:06 ` sjhill at realitydiluted.com
2008-03-05 14:52 ` Peter Korsgaard
2008-03-04 11:36 jacmet at uclibc.org
2008-03-04 11:36 jacmet at uclibc.org
2008-02-28 13:46 sjhill at uclibc.org
2008-02-28 21:43 ` Ulf Samuelsson
2007-08-05 14:00 aldot at uclibc.org
2007-08-01 8:36 ulf at uclibc.org
2007-08-01 9:47 ` Hebbar
2007-07-29 7:14 ulf at uclibc.org
2007-02-03 18:47 andersen at uclibc.org
2007-01-11 7:26 andersen at uclibc.org
2007-01-10 10:29 andersen at uclibc.org
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=87ljw71jgs.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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