All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <robert@schwebel.de>
To: linux-mtd@lists.infradead.org
Subject: Re: 2.4.18-howto?
Date: Sat, 4 May 2002 15:11:48 +0200	[thread overview]
Message-ID: <20020504151148.Y13984@schwebel.de> (raw)
In-Reply-To: <20020503214738.U13984@schwebel.de>; from robert@schwebel.de on Fri, May 03, 2002 at 09:47:38PM +0200

On Fri, May 03, 2002 at 09:47:38PM +0200, Robert Schwebel wrote:
> can somebody give me a short pointer what has to be done to patch 2.4.18
> with the mtd stuff from cvs? I tried to checkout the main branch and the
> jffs2-2_4-branch and run patches/patchin.sh, but the kernel breaks. Is
> there some kind of a howto? I searched in the repository and the mailing
> list but didn't find anything. 

Somehow today the main branch seems to work (yesterday I got lots of
warnings and the kernel compilation broke...), so I could compile a kernel
with the latest CVS stuff. 

Now, I want to compile the utilities. Is it really necessary to copy the
utils to the kernel directory? I tried it with the below patch against
util/Makefile and 'make KERNELDIR=/path/to/my/kernel', but it breaks here: 

----------8<----------
ln -sf
/home/robert/embedded/ptxdist-0.1.1/build/linux-2.4.18-rthal5-jffs2/fs/jffs2/compr.c
compr.c
cc
-I/home/robert/embedded/ptxdist-0.1.1/build/linux-2.4.18-rthal5-jffs2/include
-O2 -Wall -Dprintk=printf -DKERN_NOTICE= -c -o compr.o compr.c
compr.c: In function `jffs2_decompress':
compr.c:135: warning: implicit declaration of function `printf'
compr.c:135: `KERN_WARNING' undeclared (first use in this function)
compr.c:135: (Each undeclared identifier is reported only once
compr.c:135: for each function it appears in.)
compr.c:135: parse error before string constant
make: *** [compr.o] Error 1 
----------8<----------

... which comes because in compr.c there is no #include <stdio.h> in case
of non-kernel code. The whole thing with -Dprintk=printf looks a little bit
like a hack, so is there a better way to compile the utilities? 

Robert

----------8<----------
--- Makefile-orig       Sat May  4 15:06:34 2002
+++ Makefile    Sat May  4 14:42:12 2002
@@ -3,7 +3,7 @@
 
 # $Id: Makefile,v 1.23 2002/03/03 16:14:24 dwmw2 Exp $
 
-CFLAGS += -I../include -O2 -Wall
+CFLAGS += -I$(KERNELDIR)/include -O2 -Wall
 
 TARGETS = ftl_format erase eraseall nftldump nanddump doc_loadbios \
 nftl_format mkfs.jffs ftl_check nandtest nandwrite mkfs.jffs2 lock unlock
\
@@ -20,7 +20,7 @@
 compr_rubin.o: pushpull.h histo_mips.h compr_rubin.h
 
 $(SYMLINKS):
-       ln -sf ../fs/jffs2/$@ $@
+       ln -sf $(KERNELDIR)/fs/jffs2/$@ $@
 
 mkfs.jffs2: crc32.o compr_rtime.o compr_rubin.o compr.o mkfs.jffs2.o
compr_zlib.o
        $(CC) -o $@ $^ -lz
----------8<----------
-- 
 +--------------------------------------------------------+
 | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de |
 | Pengutronix - Linux Solutions for Science and Industry |
 |   Braunschweiger Str. 79,  31134 Hildesheim, Germany   |
 |    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4    |
 +--------------------------------------------------------+

  reply	other threads:[~2002-05-04 13:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 19:47 2.4.18-howto? Robert Schwebel
2002-05-04 13:11 ` Robert Schwebel [this message]
2002-05-04 19:32   ` 2.4.18-howto? Robert Schwebel
2002-05-07  5:42 ` 2.4.18-howto? Robert Schwebel
2002-05-07 11:19   ` 2.4.18-howto? Thomas Gleixner
     [not found] <81D0D3538E3CD411AE3C00D0B7474C31C8EE37@jadran.hermes.si>
2002-05-07 13:00 ` 2.4.18-howto? Robert Schwebel
2002-05-07 16:16   ` 2.4.18-howto? Robert Kaiser
2002-05-07 17:34     ` 2.4.18-howto? Robert Schwebel
2002-05-08 10:33       ` 2.4.18-howto? Robert Kaiser

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=20020504151148.Y13984@schwebel.de \
    --to=robert@schwebel.de \
    --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 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.