From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Implicit declaration of mblen
Date: Mon, 23 Oct 2017 20:33:10 +0200 [thread overview]
Message-ID: <20171023203310.7ea017d0@gmx.net> (raw)
In-Reply-To: <1508775095198-0.post@n4.nabble.com>
Hello Kees,
On Mon, 23 Oct 2017 09:11:35 -0700 (MST), Kees van Unen <Keesvanunen@hotmail.com> wrote:
> > Copy the the make command line from the xlib_libX11, append V=1 to it, and
> > you'll see the compilation commands. Copy the compilation command for the
> > failing file, replace the -c with -E and the -o with some filename, so you
> > get
> > the preprocessed file. Then in that preprocessed file check which stdlib.h
> > it
> > includes. stdlib.h should be included from include/X11/Xlibint.h.
>
> Hi, I managed to get the preprocessor file (see uploaded file). It includes
> the next stdlib.h:
>
> output/host/arm-buildroot-linux-uclibc/gnueabihf/sysroot/usr/include/stdlib.h
>
> In this version of stdlib.h there is no reference to mblen (see uploaded
> file).
>
> Regards,
> Kees
>
> imCallbk.o
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2263/imCallbk.o>
> stdlib.h
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2263/stdlib.h>
>
Compared against local build (git master):
seiderer at localhost:~/Work/Buildroot/build-rpi0-xlib_libX11-1.6.5-mblen-error-001> wget http://buildroot-busybox.2317881.n4.nabble.com/file/t2263/stdlib.h
seiderer at localhost:~/Work/Buildroot/build-rpi0-xlib_libX11-1.6.5-mblen-error-001> diff -u stdlib.h ./host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/stdlib.h
--- stdlib.h 2017-10-23 20:17:01.351394515 +0200
+++ ./host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/stdlib.h 2017-10-21 23:29:09.028752219 +0200
@@ -26,6 +26,7 @@
/* Get size_t, wchar_t and NULL from <stddef.h>. */
#define __need_size_t
#ifndef __need_malloc_and_calloc
+# define __need_wchar_t
# define __need_NULL
#endif
#include <stddef.h>
@@ -138,7 +139,8 @@
#define MB_CUR_MAX (__ctype_get_mb_cur_max ())
extern size_t __ctype_get_mb_cur_max (void) __THROW __wur;
#else
-# define MB_CUR_MAX 1
+# define MB_CUR_MAX (_stdlib_mb_cur_max ())
+extern size_t _stdlib_mb_cur_max (void) __THROW __wur;
#endif
@@ -825,6 +827,29 @@
#endif /* use MISC || use X/Open Unix */
+__BEGIN_NAMESPACE_STD
+/* Return the length of the multibyte character
+ in S, which is no longer than N. */
+extern int mblen (const char *__s, size_t __n) __THROW __wur;
+/* Return the length of the given multibyte character,
+ putting its `wchar_t' representation in *PWC. */
+extern int mbtowc (wchar_t *__restrict __pwc,
+ const char *__restrict __s, size_t __n) __THROW __wur;
+/* Put the multibyte character represented
+ by WCHAR in S, returning its length. */
+extern int wctomb (char *__s, wchar_t __wchar) __THROW __wur;
+
+
+/* Convert a multibyte string to a wide char string. */
+extern size_t mbstowcs (wchar_t *__restrict __pwcs,
+ const char *__restrict __s, size_t __n) __THROW;
+/* Convert a wide char string to multibyte string. */
+extern size_t wcstombs (char *__restrict __s,
+ const wchar_t *__restrict __pwcs, size_t __n)
+ __THROW;
+__END_NAMESPACE_STD
+
+
#ifdef __USE_SVID
/* Determine whether the string value of RESPONSE matches the affirmation
or negative response expression as specified by the LC_MESSAGES category
Regards,
Peter
>
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2017-10-23 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 11:10 [Buildroot] Implicit declaration of mblen Kees van Unen
2017-10-21 16:26 ` Peter Korsgaard
2017-10-21 20:44 ` Kees van Unen
2017-10-21 20:56 ` Arnout Vandecappelle
2017-10-21 21:07 ` Kees van Unen
2017-10-22 10:02 ` Arnout Vandecappelle
2017-10-22 13:34 ` Kees van Unen
2017-10-23 16:11 ` Kees van Unen
2017-10-23 18:33 ` Peter Seiderer [this message]
2017-10-23 19:08 ` Arnout Vandecappelle
2017-10-24 5:34 ` Kees van Unen
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=20171023203310.7ea017d0@gmx.net \
--to=ps.report@gmx.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