Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Implicit declaration of mblen
Date: Sat, 21 Oct 2017 18:26:53 +0200	[thread overview]
Message-ID: <87bml0cvqq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1508584234482-0.post@n4.nabble.com> (Kees van Unen's message of "Sat, 21 Oct 2017 04:10:34 -0700 (MST)")

>>>>> "Kees" == Kees van Unen <Keesvanunen@hotmail.com> writes:

 > Hi,
 > I am using buildroot-2017.08 and I want to use X.org. When compiling
 > xlib_libX11-1.6.5 there is an error in imCallbk.c: implicit declaration of
 > function mblen. By adding a -I reference to CFLAGS in the relevant Makefile
 > to stdlib.h this source compiles. This happens for a number of X11 sources.
 > Does anybody knows how this can be solved with Buildroot?

 > The mblen bug also appears later on in the process when it tries to use
 > xlib_libx.so.

The cross compiler should find stdlib.h without any special -I
flags. Can you post your defconfig file (run make savedefconfig to
generate it) and the exact error message you are seeing?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-10-21 16:26 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 [this message]
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
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=87bml0cvqq.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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