#4 Compile errors using gcc 3.2, 3.3, 4.0

[Brad Alexander]

I have tried compiling LavaRnd, with three different
versions of gcc, and all of them fail. System specs are
as follows:

LavaRnd version: 0.1.3
System: Debian/sid (unstable)
Kernel: 2.6.11
gcc versions: 3.2, 3.3, 4.0

I get the following errors:

gcc-3.2:
(this one has already been reported...)

rm -f blib/arch/auto/LavaRnd/Exit/Exit.so
LD_RUN_PATH="" cc -shared -L/usr/local/lib Exit.o -o
blib/arch/auto/LavaRnd/Exit/Exit.so
chmod 755 blib/arch/auto/LavaRnd/Exit/Exit.so
cp Exit.bs blib/arch/auto/LavaRnd/Exit/Exit.bs
chmod 644 blib/arch/auto/LavaRnd/Exit/Exit.bs
Unknown option: perm_rw
make[2]: *** [manifypods] Error 1
make[2]: Leaving directory
`/usr/local/src/LavaRnd-0.1.3/perllib/LavaRnd/Exit'
make[1]: *** [Exit] Error 2
make[1]: Leaving directory
`/usr/local/src/LavaRnd-0.1.3/perllib'
make all for perllib failed
make: *** [all] Error 2

gcc-3.3:

=+=+= starting tool subdir =+=+=
(cd tool; make all)
make[1]: Entering directory
`/usr/local/src/LavaRnd-0.1.3/tool'
/usr/bin/gcc-3.3 -DLAVA_DEBUG -Wall -Werror -g3 -O3
-I../lib tryrnd.c -c
tryrnd.c: In function `main':
tryrnd.c:212: warning: null argument where non-null
required (arg 2)
tryrnd.c:215: warning: null argument where non-null
required (arg 1)
make[1]: *** [tryrnd.o] Error 1
make[1]: Leaving directory
`/usr/local/src/LavaRnd-0.1.3/tool'
make all for tool failed
make: *** [all] Error 2

gcc-4.0:

=+=+= starting lib subdir =+=+=
(cd lib; make all)
make[1]: Entering directory
`/usr/local/src/LavaRnd-0.1.3/lib'
/usr/bin/gcc-4.0 -DLAVA_DEBUG -Wall -Werror -g3 -O3
-I. -c -o fetchlava.o fetchlava.c
cc1: warnings being treated as errors
fetchlava.c: In function 'lava_preload':
fetchlava.c:2021: warning: pointer targets in
assignment differ in signedness
fetchlava.c:2036: warning: pointer targets in
assignment differ in signedness
make[1]: *** [fetchlava.o] Error 1
make[1]: Leaving directory
`/usr/local/src/LavaRnd-0.1.3/lib'
make all for lib failed
make: *** [all] Error 2

[Nobody/Anonymous]

Logged In: NO

I have had similar problems and fixed it only by going to
redhat 9 or redhat Enterprise 3

[Nobody/Anonymous]

The problem stems from trying to manify the perl modules using an depricated option to pod2man.

I was able to get around it by editting /usr/bin/pod2man and adding "'perm_rw=s'" to the list of GetOptions it accepts just to make it STFU and let the rest of the make finish.

From what I can tell it just dictates the permissions of the eventually installed man files for the perl modules. LavaRnd seems to work fine without that option being honored.