I'm no 'configure' expert but how about looking for 'sockaddr_in6', in6_addr, or
'sin6_port' being defined in the header files, either with grep or by creating a
compile file with the appropriate include and code that uses them and see if it
compiles?
- Justus
[EMAIL PROTECTED] on 09/22/2000 02:04:43 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Justus J. Addiss/HI-Healthinfo/3M/US)
Subject: Re: LPRng: LPRng-3.6.24 and ifhp 3.3.21 fail to compile onTru64 4.0E
w/GCC 2.8.1
> From [EMAIL PROTECTED] Tue Sep 19 10:27:35 2000
> Date: Tue, 19 Sep 2000 11:44:18 -0400
> From: "Damian, G. C. (Gerald)" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: LPRng-3.6.24 and ifhp 3.3.21 fail to compile onTru64
> 4.0E w/GCC 2.8.1
>
> [EMAIL PROTECTED] wrote:
> >
> > As far as I can tell the AF_INET6 #define is the ONLY part of IPV6 that is
> > defined/works in Tru64 V4.0E or 4.0F. I can find no other references to IPV6
> > anywhere in any header file, documentation file, or spec sheet. And the man
> > pages for inet(7) and ip(7) both clearly talk about 4 bytes addresses etc.
No
> > mention of anything IPV6 related.
> >
> > So I conclude that you need to pick some other variable to test, add IPV6 as
a
> > configuration variable (so it can be turned off), or implement IP V6 for
Tru64
> > V4.0E :-)
> >
>
> Patrick,
>
> I hate to tell ya. But I get the identical compile errors as Justus trying to
> compile LPRng-3.6.24 on an SGI running IRIX 6.5. It looks like AF_INET6 is
> defined in /usr/include/sys/socket.h, but I don't see anything else that
> references it. If you're going to give Justus a switch, count me in too.
> For now I'm going back to 3.6.19 on my SGIs.
>
> --
> Jerry Damian | Ford Email: [EMAIL PROTECTED]
> Ford Motor Co./RCS Dept. | Internet Email: [EMAIL PROTECTED]
> SRL MD 1074 RM 1116 | ph: (313)32-38347 fax: (313)39-04865
> Dearborn, MI 48121-2053 | my opinions != Ford's opinions or policy
OK, can you come up with something that is defined ONLY for systems
with IPV6 support in them OR a configure entry to detect it?
Patrick
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
