From: JS <js@hipro.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] Reg. CC_FOR_BUILD in xlib_libX11
Date: Sun, 02 Mar 2008 01:05:40 +0530 [thread overview]
Message-ID: <1204400140.23564.9.camel@localhost> (raw)
Hello,
In package/x11r7/xlib_libX11/xlib_libX11.mk, the variable
'XLIB_LIBX11_CONF_ENV' confuses me. CC_FOR_BUILD is set to
use /usr/bin/gcc (native gcc) to use the headers from cross-compiler's
toolchain. Is this right?
Building x11r7 for mipsel fails with failures starting as,
> make[3]: Entering directory `/home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/xlib_libX11-1.1.1/src/util'
> Makefile:510: warning: overriding commands for target `makekeys-makekeys.o'
> Makefile:313: warning: ignoring old commands for target `makekeys-makekeys.o'
> Makefile:513: warning: overriding commands for target `makekeys'
> Makefile:280: warning: ignoring old commands for target `makekeys'
> /usr/bin/gcc -I/home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include -DHAVE_CONFIG_H -I. -I../../src -I../../include/X11 -c makekeys.c -o makekeys-makekeys.o
> In file included from /home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include/sys/types.h:31,
> from /home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include/X11/Xos.h:60,
> from makekeys.c:35:
> /home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include/bits/types.h:133:3: error: #error
> In file included from /home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include/sys/types.h:31,
> from /home/joe/work/inventsoln/tornado/tornado-gnu/buildroot/build_mipsel/staging_dir/usr/include/X11/Xos.h:60,
> from makekeys.c:35:
After a bit of digging into the failure, I saw that __WORDSIZE is
defined to _MIPS_SZPTR in include/bits/wordsize.h . And, since the
compiler used is a native compiler (i686), I did not define that macro.
--
HiPro Solutions
http://hipro.co.in/
reply other threads:[~2008-03-01 19:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1204400140.23564.9.camel@localhost \
--to=js@hipro.co.in \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.