From: Sam Ravnborg <sam@ravnborg.org>
To: Shaz <shazalive@gmail.com>
Cc: linux-embedded <linux-embedded@vger.kernel.org>,
ray.sunjae.lee@gmail.com, tpm-emulator-user@lists.berlios.de,
tpm-emulator-devel@lists.berlios.de,
Security Engineering Archive <groupsecurityengineering@gmail.com>
Subject: Re: Incompatible CFLAGS for kernel module
Date: Sun, 6 Jul 2008 22:00:56 +0200 [thread overview]
Message-ID: <20080706200056.GA27406@uranus.ravnborg.org> (raw)
In-Reply-To: <7b740b700807060035y66bdc54byc8a5ad87b6e3d50d@mail.gmail.com>
> >>> >> this case. Following is the error:
> >>> >>
> >>> >> [root@develbox tpm_emulator-0.5]# make
> >>> >> Making all in tpmd
> >>> >> make[1]: Entering directory `/embedded/tpm_emulator-0.5/tpmd'
> >>> >> make[1]: Nothing to be done for `all'.
> >>> >> make[1]: Leaving directory `/embedded/tpm_emulator-0.5/tpmd'
> >>> >> Making all in tpmd_dev
> >>> >> make[1]: Entering directory `/embedded/tpm_emulator-0.5/tpmd_dev'
> >>> >> CC [M] /embedded/tpm_emulator-0.5/tpmd_dev/tpmd_dev.o
> >>> >> cc1: error: unrecognized command line option "-mlittle-endian"
> >>> >> cc1: error: unrecognized command line option "-mapcs"
> >>> >> cc1: error: unrecognized command line option "-mno-sched-prolog"
> >>> >> cc1: error: unrecognized command line option "-mabi=aapcs-linux"
> >>> >> cc1: error: unrecognized command line option "-mno-thumb-interwork"
This all looks like you are using the wrong gcc.
And the "make V=1" option should tell you that.
> I've noticed some issues in my rootfs and on to it but plz do look at
> the Makefile. i might be missing something there instead.
The Makefile looks ok.
Sam
prev parent reply other threads:[~2008-07-06 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 17:34 Incompatible CFLAGS for kernel module Shaz
2008-07-04 20:32 ` Sam Ravnborg
2008-07-05 5:33 ` Shaz
2008-07-05 6:33 ` Sam Ravnborg
[not found] ` <7b740b700807052234p49a50c22g290d9a76e04d373f@mail.gmail.com>
2008-07-06 7:35 ` Shaz
2008-07-06 20:00 ` Sam Ravnborg [this message]
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=20080706200056.GA27406@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=groupsecurityengineering@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=ray.sunjae.lee@gmail.com \
--cc=shazalive@gmail.com \
--cc=tpm-emulator-devel@lists.berlios.de \
--cc=tpm-emulator-user@lists.berlios.de \
/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;
as well as URLs for NNTP newsgroup(s).