Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kees van Unen <Keesvanunen@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Implicit declaration of mblen
Date: Sun, 22 Oct 2017 06:34:41 -0700 (MST)	[thread overview]
Message-ID: <1508679281272-0.post@n4.nabble.com> (raw)
In-Reply-To: <bc9fed74-546a-a9f6-26b5-4698562b051e@mind.be>

> 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. 

Need some more help... When following steps above the following error
appears:

fatal error: cannot specify -o with -c, -S or -E with multiple files.

I noticed that when executing abc_new the options -fPIC -DPIC -o
.libs/imCallbk.o were automatically placed behind the compilation command

abc_old is initial compilation command
abc_new is adjusted compilation command to obtain preprocessed file

abc_old.abc_old
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2263/abc_old.abc_old>  
abc_new.abc_new
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2263/abc_new.abc_new>  



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

  reply	other threads:[~2017-10-22 13:34 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 [this message]
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=1508679281272-0.post@n4.nabble.com \
    --to=keesvanunen@hotmail.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