From: Alpt <alpt@freaknet.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14 assembler compilation error
Date: Mon, 26 Dec 2005 06:04:01 +0100 [thread overview]
Message-ID: <20051226050400.GA20686@nihil> (raw)
In-Reply-To: <20051224134753.GA19710@nihil>
On Sat, Dec 24, 2005 at 02:47:53PM +0100, <Alpt>:
~> AS arch/i386/kernel/head.o
~> include/asm-generic/pgtable.h: Assembler messages:
~> include/asm-generic/pgtable.h:114: Error: no such instruction: `static inline void ptep_mkdirty(pte_t *ptep)'
~> include/asm-generic/pgtable.h:115: Error: junk at end of line, first unrecognized character is `{'
~> include/asm-generic/pgtable.h:116: Error: invalid character '_' in mnemonic
~> include/asm-generic/pgtable.h:117: Error: invalid character '_' in mnemonic
~> include/asm-generic/pgtable.h:118: Error: junk at end of line, first unrecognized character is `}'
~> make[1]: *** [arch/i386/kernel/head.o] Error 1
~> make: *** [arch/i386/kernel] Error 2
It is compiling \o/
The function ptep_mkdirty doesn't exist at all!
A quick grep -r verifies that.
I re-downloaded the kernel tarball and now it is working.
For some reasons the tarball I was using (dwloaded from kernel.org) got
corrupted, but since I was getting an error on ptep_mkdirty(), I didn't notice
it. I thought of ptep_mkdirty as ptep_make_dirty. Damn, the tarball was dirty!
This is one more reason to begin to learn all the kernel source code.
Well, time to reboot.
--
:wq!
"I don't know nothing" The One Who reached the Thinking Matter '.'
[ Alpt --- Freaknet Medialab ]
[ GPG Key ID 441CF0EE ]
[ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ]
prev parent reply other threads:[~2005-12-26 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 13:47 2.6.14 assembler compilation error Alpt
2005-12-26 5:04 ` Alpt [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=20051226050400.GA20686@nihil \
--to=alpt@freaknet.org \
--cc=linux-kernel@vger.kernel.org \
/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.