Problem building firmware-mod-kit on Centos version 2.6.18-128.el5

[GoogleCodeExporter]

What steps will reproduce the problem?
1. /trunk/src/make or /trunk/src/make all
2.
3.

What is the expected output? What do you see instead?
the expected output is successful build of firmware-mod-kit. 
instead:
make[3]: Entering directory 
`/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma/squashfs3.2-r
2/squashfs-tools'
cc   mksquashfs.o read_fs.o sort.o  -lz -lm 
-L/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma//CPP/7zip/Co
mpress/LZMA_Alone 
-L/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma//C/Compress/
Lzma -lpthread -lunlzma_r -llzma_r -lstdc++ -o mksquashfs
/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma//C/Compress/Lz
ma/libunlzma_r.a(uncomp_r.o): In function `sqlzma_init':
uncomp_r.c:(.text+0xda): undefined reference to `inflateInit_'
/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma//C/Compress/Lz
ma/libunlzma_r.a(uncomp_r.o): In function `sqlzma_un':
uncomp_r.c:(.text+0x134): undefined reference to `inflateReset'
uncomp_r.c:(.text+0x174): undefined reference to `inflate'
collect2: ld returned 1 exit status
make[3]: *** [mksquashfs] Error 1
make[3]: Leaving directory 
`/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma/squashfs3.2-r
2/squashfs-tools'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/usr/local/firmware-mod-kit/trunk/src/others/squashfs-3.2-r2-lzma'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/local/firmware-mod-kit/trunk/src/others'
make: *** [all] Error 2

What version of the product are you using? On what operating system?
svn checkout http://firmware-mod-kit.googlecode.com/svn/trunk/ 
firmware-mod-kit-read-only

Please provide any additional information below.
building firmware-mod-kit on Linux version 2.6.18-128.el5
after executing ./configure

Original issue reported on code.google.com by zohair2...@gmail.com on 16 Feb 2012 at 2:18

Attachments:

• Makefile

[GoogleCodeExporter]

Do you have the zlib development package installed?

Original comment by heffne...@gmail.com on 16 Feb 2012 at 8:51

[GoogleCodeExporter]

Yes. I checked that the zlib development library is installed before reporting 
this issue. 

Original comment by zohair2...@gmail.com on 16 Feb 2012 at 9:33

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[root@localhost src]# yum install zlib-devel
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.prometeus.net
 * updates: mirrors.prometeus.net
 * extras: mirrors.prometeus.net
Setting up Install Process
Parsing package install arguments
Package zlib-devel-1.2.3-4.el5.i386 already installed and latest version
Nothing to do
[root@localhost src]# yum update zlib-devel
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.prometeus.net
 * updates: mirrors.prometeus.net
 * extras: mirrors.prometeus.net
Setting up Update Process
No Packages marked for Update
[root@localhost src]#

I also downloaded zlib-1.2.6 source and make, make test, make install all went 
well with no problems. The path for lib directory is add to /etc/ld.so.conf as 
/usr/local/lib. I also tried  trunk/src/./configure --libdir=/usr/local/lib but 
didn't work.

Original comment by zohair2...@gmail.com on 16 Feb 2012 at 11:33

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Yes, that *particular* variation of squashfs-lzma-r2 has its own LZMA drop-in 
replacement library included within its subdirectory. The error is there. I'd 
comment it out in src/others/Makefile and go on, as you probably aren't using 
that variant.

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 1:07

[GoogleCodeExporter]

I deleted all my speculative comments. When I'm talking to myself, I should 
really do so quieter ;p. Anyway, I am looking into possible build errors and 
will test it on a similar machine soon. I don't want to commit a change I don't 
know will work for sure.

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 1:09

[GoogleCodeExporter]

I have a CentOS box ready for it, so we'll find out soon. I should see the same 
issue there.

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 1:10

[GoogleCodeExporter]

Funny thing, it built *fine* on a fresh CentOS 6.0 install .. So... Hmm...

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 1:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Too bad that's the one you need then (presumably). I can double check, but 
identifying why your build failed would be ideal. I don't know, my CentOS test 
went perfectly. Make sure everything is up to date, all packages. Make sure gcc 
and g++ are, and other build tools. That's all I can think of.

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 1:37

[GoogleCodeExporter]

Thanks for your help again.. I will try to figure this out on my own...!

Original comment by zohair2...@gmail.com on 17 Feb 2012 at 1:57

[GoogleCodeExporter]

If I had any other clue, I'd help. But, I don't know where to go. I am hardly a 
linux expert myself. I mostly do Windows development, I got into linux only due 
to my embedded work, and now web server setup and management. 

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 9:48

[GoogleCodeExporter]

Marked as 'invalid' for now, until we get another report, since it build for me 
under CentOS 6.

Original comment by jeremy.collake@gmail.com on 17 Feb 2012 at 9:49

• Changed state: Invalid