Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 7 Aug 2003 03:28:57 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: inet.h error?

Hi,

On Wed, Aug 06, 2003 at 03:55:09PM -0500, Asenchi wrote:
> I am using OpenBSD 3.3 with a GENERIC kernel.  Today I decided to try 
> popa3d as a POP3 solution.

OK.

You know that OpenBSD includes popa3d, right?  Did that version or the
way it's built not satisfy you and why?

> After I tar -zxvf the latest stable release (0.6.3) I make my changes 
> to params.h and the Makefile.  I then try to do a 'make' and get this 
> error:
> 
> $ make
> gcc -c -Wall -02 -fomit-frame-pointer virtual.c
> In file included from virtual.c:25:
> /usr/include/arpa/inet.h:89: syntax error before 'inet_nsap_addr'
> /usr/include/arpa/inet.h:89: syntax error before 'u_char'
> /usr/include/arpa/inet.h:89: warning: data definition has no type or 
> storage class
> /usr/include/arpa/inet.h:90: syntax error before '*'
> *** Error code 1
> 
> Stop in /home/asenchi/popa3d/popa3d-0.6.3.
> $
> 
> I have looked at the code, but I am not very good at C so I didn't want 
> to touch it.  Do any of you have an idea what could be the problem?

1. You have enabled POP_VIRTUAL.  Do you really need it?  If not,
disable it and you'll avoid this problem.

2. There really appears to be a bug either in that header file or in
the way I'm using it with the #define's (_XOPEN_SOURCE and so on).
Camiel, -- if you're reading this, could you handle this report within
the OpenBSD team as appropriate?  I'd appreciate being CC'd on any
discussions, especially if there's anything to correct on my part.

> I have tried this both as user and root.

You shouldn't be building source code as root.  But this is not
related to the problem you're seeing.

-- 
/sd

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.