Re: still: preparing SuSE 5.2 for swarm

[Paul E. Johnson]

Dear Lorenz:

I don't have SUSE, so I don't know precisely what is wrong.  Rather than
compile this yourself, you might think about using the rpms for libpng. 
I'm reading the SUSE FAQ right now and it says it is an RPM based
distribution. Not so?

If RPM does run, there is no need to fight with this.  Go to the Redhat
site, where you can find many differnt versions of libpng.  

ftp://ftp.redhat.com/pub/redhat/...

There you see directories of their official releases.  Redhat 5 & 5.1
are glibc based systems, and it is likely  their stuff will not work
with your system.  I see in the faq that SUSE 5.2 is libc5, correct? 
You ought to be able to take RPMs from Redhat 4.2 and install in your
system.  If I was in your situation, I would get the SRPM packages for
the things you want from the newer Redhat distributions, then I would
install them, and then try rebuilding the rpms by going to
/usr/src/redhat/SPEC and typing "rpm -ba xxx.spec".  If it fails, it
will probably tell you what other stuff you are missing.

If you don't find the version of libpng you want to look in the
/pub/contrib directory.  The subdirectory "hurricane" is for the glib-c
based distribution of Redhat 5.0 and after. You can't install their
RPMS, but you can take their SRPMS and recompile them.   The
subdirectory /pub/rawhide has RPMS of the not-yet released Redhat 5.2.
If you want to see what the newest wave is, look in there.

Incidentally, even if you don't use the RPMs or SPRMs to actually make a
package, you usually get good ideas from looking at their SPEC files and
any patches they apply to the source. In the case of libpng, I see the
SPEC file provided with Redhat 5.0 supplies a lot of hints about the
problem you are facing.  It applies a patch that change the references
to zlib in files makefile.elf and makefile, like this.

-ZLIBLIB=../zlib
-ZLIBINC=../zlib
+ZLIBLIB=/usr/lib
+ZLIBINC=/usr/include

It also changes the prefix and fiddles with compiler flags too. It looks
to me from your output below that you do need to fix ZLIB references.
Perhaps if you look at the SPEC file that goes with the version you are
working on, it will be OK!  It  appears this is a difficult one to
configure because it is not a GNU autoconf style package, there's no
./configure or such. That means you have to be extra fussy editing the
makefile so it can find all the stuff in your system. Also, I note the
commands typed after patching makefile and makefile.elf are not the
usuals. The SPEC file has (omitting the RPM optimization flags):


make  -f makefile.elf
rm -f *.o
make  -f makefile
make -f makefile.elf install
make -f makefile install
/sbin/ldconfig

This is bringing back all kinds of bad memories of libpng and what a
strange package it was/is. 

Paul Johnson


Lorenz Gygax wrote:
> 
> Dear all,
> 
> sorry that you didn't hear from me earlier again, but somehow your
> messages did not reach me by e-mail (I actually wondered about the
> quietness), though the command 'which' to majordomo asures me that I am
> still subscribed to the list. I realized this only today when I went
> digging into the list's archive. Well, I will see whether I get your
> responses this time ...
> 
> I could successfully (as far as I see) install BLT 2.4. The only problem
> remaining now (except for SWARM itself ;-) is libpng. I set up the
> directories for it and zlib as proposed in the libpng INSTALL and copied
> the makefile.lnx from the scripts. I did not change anything in there.
> When I try to follow the INSTALL further this is what happens:
> 
> # make test
> gcc -o pngtest -I../zlib -Wall -O3 -funroll-loops -malign-loops=2
> -malign-functions=2  pngtest.o -L. -Wl,-rpath,. -L../zlib
> -Wl,-rpath,../zlib -lpng -lz -lm
> pngtest.o: In function `test_one_file':
> pngtest.o(.text+0x54d): undefined reference to `png_set_write_status_fn'
> pngtest.o(.text+0x56a): undefined reference to `png_set_write_status_fn'
> pngtest.o(.text+0x578): undefined reference to `png_set_read_status_fn'
> pngtest.o(.text+0x596): undefined reference to
> `png_set_write_user_transform_fn'
> make: *** [pngtest] Error 1
> 
> Then I looked at pngconf.h where I found some lines with reference to
> Linux.  When I uncomment them I get:
> 
> # make test
> gcc -I../zlib -Wall -O3 -funroll-loops -malign-loops=2 -malign-functions=2
> -c pngtest.c -o pngtest.o
> In file included from png.h:112,
>                  from pngtest.c:38:
> pngconf.h:104: parse error before `1'
> In file included from pngtest.c:38:
> png.h:529: parse error before `jmp_buf'
> png.h:529: warning: no semicolon at end of struct or union
> png.h:682: parse error before `}'
> pngtest.c: In function `test_one_file':
> pngtest.c:511: warning: implicit declaration of function `setjmp'
> pngtest.c:511: dereferencing pointer to incomplete type
> pngtest.c:527: dereferencing pointer to incomplete type
> make: *** [pngtest.o] Error 1
> 
> So maybe that is the right track if I only uncomment the right lines? But
> which are these?
> 
> Thanks for all further help! Regards
> --
>                         Lorenz Gygax
> 
>         |
>        /|         address@hidden;       room: 36-L-40
>       / |\
>      /  | \       Department of Applied Mathematics
>     /   |  \      University of Zuerich-Irchel
>    /____|   \     Winterthurerstr. 190; CH-8057 Zurich
>   ______|____\    voice: 41-1-635-58-52  fax: 41-1-635-57-05
>  /           /
> ~~~~~~~~~~~~~~~~~ Dachslernstr. 141, 8048 ZH, 41-1-432-51-47
> 
>                   ==================================
>    Swarm-Support is for discussion of the technical details of the day
>    to day usage of Swarm.  For list administration needs (esp.
>    [un]subscribing), please send a message to <address@hidden>
>    with "help" in the body of the message.
>                   ==================================

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================