public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Atkins <derek@ihtfp.com>
To: Kostadin Karaivanov <larry@minfin.bg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ipsec-tools 0.1 + kernel 2.5.64
Date: 05 Mar 2003 13:15:00 -0500	[thread overview]
Message-ID: <sjmof4pvfx7.fsf@kikki.mit.edu> (raw)

Hi,

>   If you mention www.sf.net/projects/ipsec-tools
>   they does not compiles for me I cot following error

Yes, this is what we mean...

> grabmyaddr.c:69:1: warning: "HAVE_GETIFADDRS" redefined
> <command line>:1:1: warning: this is the location of the previous definition
> grabmyaddr.c:88: redefinition of `struct ifaddrs'
> grabmyaddr.c:200: warning: static declaration for `getifaddrs' follows
> non-static
> grabmyaddr.c:254: warning: static declaration for `freeifaddrs' follows
> non-static
> make[3]: *** [grabmyaddr.o] Error 1
> make[3]: Leaving directory `/usr/src/ipsec-tools-0.1/src/racoon'

Hmm...  What version of glibc are you using?  This seems to imply that
getifaddrs() and freeifaddrs() is now in libc, where it wasn't before.
I didn't know it got added -- I wonder when that happened?

>   I can provide additional info if needed (gcc-3.2.2) 

Please.  Feel free to follow up personally rather than to this list
(or at least be sure to CC me on all your replies, as I'm not actually
subscribed directly).

Can you try this patch and see if that fixes the problem?

diff -u -r1.3 grabmyaddr.c
--- src/racoon/grabmyaddr.c	3 Mar 2003 23:56:56 -0000	1.3
+++ src/racoon/grabmyaddr.c	5 Mar 2003 18:12:28 -0000
@@ -65,7 +65,7 @@
 #include "isakmp_var.h"
 #include "gcmalloc.h"
 
-#ifdef __linux__
+#if defined(__linux__) && !defined(HAVE_GETIFADDRS)
 #define HAVE_GETIFADDRS
 #endif
 
@@ -78,7 +78,7 @@
 static int suitable_ifaddr6 __P((const char *, const struct sockaddr *));
 #endif
 
-#ifdef __linux__
+#if defined(__linux__) && !defined(HAVE_GETIFADDRS)
 
 /* We could do this _much_ better. kame racoon in its current form
  * will esentially die at frequent changes of address configuration.

Thanks,

-derek, ipsec-tools maintainer
-- 
       Derek Atkins
       Computer and Internet Security Consultant
       derek@ihtfp.com             www.ihtfp.com

             reply	other threads:[~2003-03-05 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 18:15 Derek Atkins [this message]
2003-03-05 18:27 ` ipsec-tools 0.1 + kernel 2.5.64 Christoph Hellwig
2003-03-05 18:43   ` Derek Atkins
2003-03-05 18:51     ` Christoph Hellwig
2003-03-05 19:00       ` Derek Atkins
2003-03-05 19:55       ` Derek Atkins
  -- strict thread matches above, loose matches on Subject: below --
2003-03-05 11:49 Kostadin Karaivanov
2003-03-05 16:05 ` Kostadin Karaivanov
2003-03-05 11:29 Andreas Jellinghaus
2003-03-05 11:28 ` bert hubert
2003-03-05 14:52   ` Derek Atkins
2003-03-05 12:47 ` James Morris
2003-03-05 19:33   ` Andreas Jellinghaus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sjmof4pvfx7.fsf@kikki.mit.edu \
    --to=derek@ihtfp.com \
    --cc=larry@minfin.bg \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox