[Fink-users] Porting Opennap

[Jeffrey E. <su...@gr...>]

Well, now to what I was really trying to do in the first place. I am trying
to port OpenNap, the open source Napster server -- BTW, this is another good
product brought to you by sourceforge:

http://opennap.sourceforge.net

I installed all available packages as of this morning from Fink. Then I ran
the configure script as described in the Install readme for OpenNap 0.44.
Here's my output:

[dsl-gte-20555:~/desktop/opennap-0.44] root# ./configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) cc
checking whether the C compiler (cc  ) works... yes
checking whether the C compiler (cc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ANSI C... (cached) none needed
checking how to run the C preprocessor... (cached) cc -E -traditional-cpp
checking for ANSI C header files... (cached) yes
checking for unistd.h... (cached) yes
checking for socklen_t... no
checking whether byte ordering is bigendian... (cached) yes
checking size of long... (cached) 4
checking for getopt... (cached) yes
checking for regcomp... (cached) yes
checking for alarm... (cached) yes
checking for syslog... (cached) yes
checking for compress2 in -lz... (cached) yes
checking for gethostbyname in -lxnet... (cached) no
checking for socket in -lnsl... (cached) no
checking for gethostbyname in -lsocket... (cached) no
checking for mlockall... (cached) yes
checking for poll... (cached) no
checking for default config directory... ${pkgdatadir}
checking whether running as a router... no
checking whether to run chrooted... no
creating ./config.status
creating Makefile
creating config.h
config.h is unchanged

The install instructions then says to run make...

[dsl-gte-20555:~/desktop/opennap-0.44] root# make
cc -DHAVE_CONFIG_H -I. -I. -I. -DSHAREDIR=\"/usr/local/share/opennap\"    -W
-Wall -Wmissing-prototypes -Wcast-align -pedantic -g -O2 -c init.c
In file included from init.c:12:
/usr/include/grp.h:79: warning: parameter names (without types) in function
declaration
In file included from /usr/include/machine/types.h:30,
                 from /usr/include/sys/types.h:70,
                 from /usr/include/pwd.h:68,
                 from init.c:13:
/usr/include/ppc/types.h:75: warning: ANSI C does not support `long long'
/usr/include/ppc/types.h:76: warning: ANSI C does not support `long long'
In file included from init.c:26:
/usr/include/stdlib.h:181: warning: ANSI C does not support `long long'
/usr/include/stdlib.h:183: warning: ANSI C does not support `long long'
In file included from opennap.h:20,
                 from init.c:35:
/usr/include/zlib.h:171: warning: ANSI C forbids const or volatile functions
/usr/include/zlib.h:804: warning: ANSI C forbids const or volatile functions
/usr/include/zlib.h:885: warning: ANSI C forbids const or volatile functions
/usr/include/zlib.h:887: warning: ANSI C forbids const or volatile functions
init.c: In function `init_server':
init.c:237: warning: implicit declaration of function `mlockall'
init.c:237: `MCL_CURRENT' undeclared (first use in this function)
init.c:237: (Each undeclared identifier is reported only once
init.c:237: for each function it appears in.)
init.c:237: `MCL_FUTURE' undeclared (first use in this function)
make: *** [init.o] Error 1
[dsl-gte-20555:~/desktop/opennap-0.44] root#

I don't actually see the error anywhere, just all the warnings. However,
this is a vast improvement over my results without Fink!

Here's a reprint of the OpenNap Install instructions:

Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure


Any ideas?

Best Regards,
Jeffrey