From: Robert Schwebel <robert@schwebel.de>
To: linux-mtd@lists.infradead.org
Subject: Re: 2.4.18-howto?
Date: Sat, 4 May 2002 21:32:42 +0200 [thread overview]
Message-ID: <20020504213242.A29364@schwebel.de> (raw)
In-Reply-To: <20020504151148.Y13984@schwebel.de>; from robert@schwebel.de on Sat, May 04, 2002 at 03:11:48PM +0200
On Sat, May 04, 2002 at 03:11:48PM +0200, Robert Schwebel wrote:
> ... 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?
... meaning that at the moment they do not compile at all. At the moment
I seem to have resolved some of the problem, but I'm stuck here:
----------8<----------
robert@callisto:~/embedded/cvs/mtd/util ! make
KERNELDIR=~/embedded/ptxdist-0.1.1/build/linux-2.4.18-rthal5-jffs2
cc -o mkfs.jffs2 crc32.o compr_rtime.o compr_rubin.o compr.o mkfs.jffs2.o
compr_zlib.o -lz
compr_rubin.o: In function `encode':
compr_rubin.o(.text+0x88): undefined reference to `pushbit'
compr_rubin.o: In function `end_rubin':
compr_rubin.o(.text+0x124): undefined reference to `pushbit'
compr_rubin.o: In function `rubin_do_compress':
compr_rubin.o(.text+0x3ee): undefined reference to `init_pushpull'
compr_rubin.o(.text+0x447): undefined reference to `pushedbits'
compr_rubin.o: In function `rubin_do_decompress':
compr_rubin.o(.text+0x695): undefined reference to `init_pushpull'
compr.o: In function `jffs2_compress':
compr.o(.text+0x1a): undefined reference to `zlib_compress'
compr.o: In function `jffs2_decompress':
compr.o(.text+0xa8): undefined reference to `zlib_decompress'
collect2: ld returned 1 exit status
make: *** [mkfs.jffs2] Error 1
---------->8----------
Where comes pushbit() from? I cannot avoid the impression that I'm doing
something significantly wrong...
Robert
--
+--------------------------------------------------------+
| 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 |
+--------------------------------------------------------+
next prev parent reply other threads:[~2002-05-04 19:33 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 ` 2.4.18-howto? Robert Schwebel
2002-05-04 19:32 ` Robert Schwebel [this message]
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=20020504213242.A29364@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox