From: "Tim Drury" <tdrury@siliconmotorsports.com>
To: <linux-mtd@lists.infradead.org>
Subject: RE: compiling latest CVS
Date: Fri, 1 Aug 2003 18:17:10 -0400 [thread overview]
Message-ID: <000701c3587a$aa6e5e00$f546a8c0@SIMOTORSPORTS> (raw)
In-Reply-To: <000601c35879$6af19450$f546a8c0@SIMOTORSPORTS>
oops - that path to 'zlib-1.4.1' should read 'zlib-1.1.4' - hopefully
you got the point.
-tim
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org
> [mailto:linux-mtd-bounces@lists.infradead.org] On Behalf Of Tim Drury
> Sent: Friday, August 01, 2003 6:08 PM
> To: linux-mtd@lists.infradead.org
> Subject: compiling latest CVS
>
>
>
> I got the latest CVS to build, but with a few issues.
>
> patches/patchin.sh ran successfully. Upon building my kernel
> modules I got an error in nand.c that 'i' was undeclared. So
> in mtd/drivers/nand/nand.c, line 936 add 'i' to the int declaration.
>
> Now cross-compiling the kernel and modules worked fine.
>
> I sym-linked mtd/util into the kernel source base as
> instructed in the README. Building failed complaining about
> something in crc32.h and I realized that it wasn't finding
> linux/types.h. I needed to include the linux kernel include
> directory to get past this. Then it failed trying to find
> zlib.h. Added that then it failed to find libz.so.
>
> The above can all be done without modifying files:
>
> make CROSS=i386-linux- CFLAGS='-I/path/to/kernel/linux-2.4.21/include
> -I/path/to/zlib-1.4.1' \
> LDFLAGS=-L/path/to/zlib/lib
>
> and everything cross-compiled to my target system. Was
> pointing to the kernel/include directory bad?
>
> -tim
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/li> nux-mtd/
>
prev parent reply other threads:[~2003-08-01 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:08 compiling latest CVS Tim Drury
2003-08-01 22:17 ` Tim Drury [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='000701c3587a$aa6e5e00$f546a8c0@SIMOTORSPORTS' \
--to=tdrury@siliconmotorsports.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox