Hi Greg

Found the problem don't have the patch! But I have a good explanation and 
a work around.

I Compiled in ~/projects/uClinux-cdl/  not ~/projects/uClinux-dist/

> It should be generated as part of your snapgear/uClinux-dist build.
> If everything worked as it should (:-) then there would be a
> libz.a in your build tree at ~/lib/libz.a. Can you check that?

~/lib/libz.a is a symlink pointing to in this case 
~/projects/uClinux-dist/lib/zlib/libz.a (the rest of the symlinks appear 
to build correctly) since I am building in ~/projects/uClinux-cdl/~ ( I 
did "make xconfig", "make dep", "make" in "~/uClinux-cdl/")  This is a bad 
thing. ;-)

So if I rename my top level directory to uClinux-dist then do the make 
trinity again, it works! (:-)

It appears that this symlink happens at untarring?????

Looking at the achieves this has happened to a number of people.  One of 
your pieces of advise was always to untar a fresh distribution and that 
always worked in the past for this reason.

My question now is what are the cleaning steps to prepare a distribution 
that you follow from your /uClinux-dist/ --> "uClinux-20070717.tar.bz2" so 
I may complete the patch.

Cheers John

> 
> Can you check when you build that it is actually even trying
> to build the code in lib/zlib?

It does see below:

> > The uClinux build 2.4.32-uC0 failed at the ever popular place of 
MTD-Utils 
> > for jffs2.
So I have.
> > 
> > All of Patrice's MTD patches in.  Forced zlib config (not needed)
> > 
> > This is Snapgear uClinux 20070130

ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -Wl,--fatal-warnings 
-Wl,-elf2flt -Wl,-move-rodata -msep-data -Wl,--fatal-warnings -Wl,-elf2flt 

-Wl,-move-rodata -msep-data -Os -g -fomit-frame-pointer -pipe -fno-common 
-fno-builtin -Wall   -DEMBED -msep-data -Dlinux -D__linux__ -Dunix 
-D__uClinux__ -D__USE_BSD -I. -o mkfs.jffs2 crc32.o mkfs.jffs2.o 
 compr_zlib.o compr_rtime.o  -lz
> 
> JFFS2 stores files compressed by default, and it uses the zlib code
> to do it...
> 
Absolutely.
> 

The ld tool finds the symlink at ~/lib/zilb.a and most people typically 
still have the uClinux-dist available so the build works.

The build always makes the correct "~/lib/zlib/zlib.a" but the symlink 
hides it from "ld"
> > 
m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g -fomit-frame-pointer -pipe 
-fno-common -fno-builtin -Wall   -DEMBED -msep-data -Dlinux -D__linux__ 
-Dunix -D__uClinux__   -c -o zutil.o zutil.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o inflate.o 
inflate.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o infblock.o 
infblock.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o inftrees.o 
inftrees.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o infcodes.o 
infcodes.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o infutil.o 
infutil.c
ucfront-gcc m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -O2 -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o inffast.o 
inffast.c
m68k-elf-ar rc libz.a adler32.o compress.o crc32.o gzio.o uncompr.o 
deflate.o trees.o zutil.o inflate.o infblock.o inftrees.o infcodes.o 
infutil.o inffast.o 
make[3]: Leaving directory `/home/jjeffers/projects/uClinux-cdl/lib/zlib'
make[2]: Leaving directory `/home/jjeffers/projects/uClinux-cdl/lib'
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Reply via email to