From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Added package v86d which provides a real-mode helper for uvesafb driver.
Date: Tue, 17 Jul 2012 10:01:51 +0200 [thread overview]
Message-ID: <20120717100151.3948f42e@skate> (raw)
In-Reply-To: <1342495023-17145-1-git-send-email-golubovsky@gmail.com>
Le Mon, 16 Jul 2012 23:17:03 -0400,
Dmitry <golubovsky@gmail.com> a ?crit :
> +define V86D_BUILD_CMDS
> + $(MAKE) CC="$(TARGET_CC) -D__i386__" LD="$(TARGET_LD)" -C $(@D) all
> +endef
Can you try using $(TARGET_CONFIGURE_OPTS) instead, so that CFLAGS and
al. are also passed?
Something like:
$(MAKE) $(TARGET_CONFIGURE_OPTS) CFLAGS="$(TARGET_CFLAGS) -D__i386__" -C $(@D) all
I'm a bit surprised by the -D__i386__, because this is normally defined
by the compiler. Why is it needed?
See:
thomas at skate:/tmp$ cat toto.c
#ifdef __i386__
#error "You are on x86"
#elif defined(__x86_64__)
#error "You are on x86-64"
#elif defined(__arm__)
#error "You are on ARM"
#endif
thomas at skate:/tmp$ ~/x-tools/ia32-2012.03/bin/i686-pc-linux-gnu-gcc -c toto.c
toto.c:3:2: error: #error "You are on x86"
thomas at skate:/tmp$ ~/x-tools/ia32-2012.03/bin/i686-pc-linux-gnu-gcc -m64 -c toto.c
toto.c:5:2: error: #error "You are on x86-64"
thomas at skate:/tmp$ ~/x-tools/arm-2011.03/bin/arm-none-linux-gnueabi-gcc -c toto.c
toto.c:7:2: error: #error "You are on ARM"
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-17 8:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 3:17 [Buildroot] [PATCH] Added package v86d which provides a real-mode helper for uvesafb driver Dmitry
2012-07-17 8:01 ` Thomas Petazzoni [this message]
2012-07-17 9:38 ` Dmitry Golubovsky
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 21:17 Dmitry
2012-05-14 3:50 Dmitry
2012-05-09 10:41 Dmitry
2012-05-11 22:39 ` Arnout Vandecappelle
2012-05-12 5:01 ` Dmitry Golubovsky
2012-05-12 14:30 ` Arnout Vandecappelle
2012-05-09 10:32 Dmitry
2012-05-09 10:35 ` Baruch Siach
2012-05-09 1:19 Dmitry
2012-05-09 3:45 ` Baruch Siach
2012-05-09 3:47 ` Dmitry Golubovsky
2012-05-09 4:32 ` Baruch Siach
2012-05-07 3:29 Dmitry
2012-05-07 3:58 ` Baruch Siach
2012-05-07 10:31 ` Dimitry Golubovsky
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=20120717100151.3948f42e@skate \
--to=thomas.petazzoni@free-electrons.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