public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Earl Manning <EManning@PRISMIQ.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Problems making jffs2 utils
Date: Mon, 7 Apr 2003 14:18:57 -0500	[thread overview]
Message-ID: <20030407141857.3a11609c.EManning@PRISMIQ.com> (raw)
In-Reply-To: <001f01c2fd36$9c006c90$1200a8c0@JOHNB>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

Hi John,

I have a similar system, embedded mips based, and here is the changed Makefile for the util directory that I used.  I hope this helps.

Earl Manning

On Mon, 7 Apr 2003 14:50:49 -0400
"John Burch" <jburch@vincisystems.com> wrote:

> I'm running into compiler errors when trying to build the jffs2
> utilities for a 2.4.17/mips target.  I've checked out the latest mtd
> code according to www.linux-mtd.infradead.org, then have followed the
> instructions in the mtd/util/README file (copied mtd/util contents to
> directory under linux root and changed $CROSS as necessary since I'm
> cross-compiling to mips).  I cd to <mips-kernel-path>/linux/utils and do
> a make, but get errors immediately, which typically include the
> following (depending on which util I'm trying to make)...
> 
> .../libc.so.6: undefined reference to 'no symbol'
> .../mips-linux-ld: cannot find -lz
> 
> I'm really only after 'erase' and maybe 'jffs2reader' for use on my mips
> embedded target; I already have mkfs.jffs2 as an x86 binary for my x86
> development platform.  Any ideas, or better place for me to post this
> question?
> 
> John
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

[-- Attachment #2: Makefile --]
[-- Type: application/octet-stream, Size: 1072 bytes --]


# -*- sh -*-

# $Id: Makefile,v 1.1.1.1 2003/03/26 20:58:27 earl Exp $

HOSTCC := gcc
CROSS=mipsel-linux-
CC := $(CROSS)gcc
HOSTCFLAGS += -I../include -O2 -Wall -Wstrict-prototypes -Wshadow
CFLAGS += -I../include -Wall -Wstrict-prototypes -Wshadow -Wl,-Bstatic

TARGETS = ftl_format erase eraseall nftldump nanddump doc_loadbios \
nftl_format mkfs.jffs ftl_check mkfs.jffs2 lock unlock \
einfo mtd_debug fcp nandwrite jffs2dump #jffs2reader

SYMLINKS = crc32.h crc32.c compr_rtime.c

all: $(TARGETS)

clean:
	rm -f *.o $(TARGETS) $(SYMLINKS)

mkfs.jffs2.o eraseall.o crc32.o: crc32.h

$(SYMLINKS):
	ln -sf ../fs/jffs2/$@ $@

# mkfs.jffs2: crc32.o compr_rtime.o mkfs.jffs2.o compr_zlib.o
# 	$(CC) $(LDFLAGS) -o $@ $^ -lz

# eraseall: crc32.o eraseall.o
# 	$(CC) $(LDLAGS) -o $@ $^ -lz

# jffs2reader: jffs2reader.o
# 	$(CC) $(LDFLAGS) -o $@ $^ -lz 

mkfs.jffs2: crc32.c compr_rtime.c mkfs.jffs2.c compr_zlib.c
	$(HOSTCC) $(HOSTCFLAGS) $(LDFLAGS) -o $@ $^ -lz

eraseall: crc32.o eraseall.o
	$(CC) $(LDLAGS) -o $@ $^

jffs2reader: jffs2reader.o
	$(CC) $(LDFLAGS) -o $@ $^



  reply	other threads:[~2003-04-07 19:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 18:50 Problems making jffs2 utils John Burch
2003-04-07 19:18 ` Earl Manning [this message]
2003-04-09 17:19   ` John Burch
2003-04-10  6:23     ` Holger Schurig
2003-04-07 19:53 ` Jörn Engel
2003-04-07 22:54   ` mtd irc Charles Manning
2003-04-07 23:35     ` Conn Clark
2003-04-09 13:09   ` Problems making jffs2 utils John Burch
2003-04-09 13:21     ` Jörn Engel
2003-04-08  8:10 ` David Woodhouse

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=20030407141857.3a11609c.EManning@PRISMIQ.com \
    --to=emanning@prismiq.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