We are talking "ifhp" not "lprng" so the liblpr.a is not available and your
inet_ntop is not available from it. Maybe you need to include an inet_ntop for
ifhp as well as LPRng :-)

- Justus





[EMAIL PROTECTED] on 01/07/2001 12:50:23

Please respond to [EMAIL PROTECTED]


To:   [EMAIL PROTECTED]
cc:    (bcc: Justus J. Addiss/HI-Healthinfo/3M/US)
Subject:  Re: LPRng: ifhp-3.4.4 fails to compile due to IPV6 code



> From [EMAIL PROTECTED] Thu Jan  4 14:25:16 2001
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: ifhp-3.4.4 fails to compile due to IPV6 code
> Date: Thu, 04 Jan 2001 15:26:21 -0600
> From: John Perkins <[EMAIL PROTECTED]>
>
> > On Tru64 V4.0E ifhp fails to link because inet_ntop is not found. This is a
> > routine called in open_device.c. The configure script correctly decided that
> > inet_ntop did NOT exist but there are no #if defined in open_device.c to
test
> > for this and not compile the offending code. It looks like the entire
> > inet_ntop_sockaddr() function is new. Maybe all of this should be commented
out
> > if there is no IPV6?
>
> > Also, I still have the problem that GCC V2.95.2 on Tru64 believes that
SETENV
> > and UNSETENV exist, but fails to define AES_SOURCE that is required for
these
> > function calls to be defined in the system header files. So trying to
compile
> > with GCC on Tru64 fails because of the implicit definition of setenv() and
> > unsetenv().
>
> We run Tru64 V4.0F here.
>
> There were a couple of tweaks I found necessary to get ifhp to compile on the
> alpha platform:
>
> 1.  Disable the -Werror flag in src/Makefile.  It will bitch about setenv()
> and unsetenv() declarations as well as va_list definitions throughout the
> build.

Now THIS I want to see.  Could you please send me a sample of output
with the -Werror enabled and also -Werror disable (removed).

>
> 2.  Go build the libraries in bind-8.2.2 first.  There's an __inet_ntop()
> function in there that will make ifhp happy.  Solaris and Linux have these
> definitions in libresolv, which makes them easier to deal with.

But I have one also:

LPRng/src/common/linksupport.c:inet_ntop()

I am wondering if we have a problem with the order of the calls
in the liblpr library.

Try using:
  nm liblpr.a |grep inet_ntop

this will tell you if it is present.  If it is,  and is not
being found by the linker,  then you have linker problems.  I
suspect you may need to use the 'ar' facility to build a
library file index.


>
> 3.  Apply the following patch to open_device.c:
>
> *** open_device.c.orig  Wed Dec 27 09:07:52 2000
> --- open_device.c       Wed Dec 27 13:48:52 2000
> ***************
> *** 168,172 ****
> --- 168,176 ----
>           FATAL("inet_ntop_sockaddr: bad family '%d'",
>               addr->sa_family );
>       }
> + #ifdef __alpha__
> +     return( __inet_ntop( addr->sa_family, a, str, len ) );
> + #else
>       return( inet_ntop( addr->sa_family, a, str, len ) );
> + #endif
>   }
>
> Now, if Patrick could ship an inet_ntop() function with LPRng-3.4.X for those
> bizarro machines that don't have one of their own, that would be helpful.
>
> --
> ============================================================================
>    John Perkins               |   University of Wisconsin-Madison
>    Associate Researcher            |   Department of Computer Science
>    [EMAIL PROTECTED]           |   1210 W. Dayton St.
>    608-262-0438/608-262-9997 FAX  |   Madison, WI  53706-1685
> ============================================================================

Patrick Powell                 Astart Technologies,
[EMAIL PROTECTED]            9475 Chesapeake Drive, Suite D,
Network and System             San Diego, CA 92123
  Consulting                   858-874-6543 FAX 858-279-8424
LPRng - Print Spooler (http://www.lprng.com)

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------







-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to