From: "Dr. Volker Zell" <Dr.Volker.Zell@oracle.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: Recompilation errors of xinetd-2.3.9
Date: Wed, 20 Feb 2008 14:26:00 -0000 [thread overview]
Message-ID: <7zve4jhlra.fsf@vzell-de.de.oracle.com> (raw)
Hi
I'm trying to adopt the xinetd package of Sergey. The original build
script gives:
make[1]: Entering directory `/misc/src/xinetd-2.3.9/xinetd'
i686-pc-cygwin-gcc -O2 -g -O2 -g -I../libs/include -c -o access.o access.c
In file included from util.h:5,
from access.h:16,
from access.c:22:
defs.h:26: error: field `sa_in6' has incomplete type
This is from defs.h:
#include "config.h"
#include <memory.h>
#include <string.h>
#include <stdlib.h>
#include <sys/socket.h>
#include <netinet/in.h>
union xsockaddr {
struct sockaddr sa;
struct sockaddr_in sa_in;
struct sockaddr_in6 sa_in6;
char pad[128];
};
I'm wondering how Sergey compiled this way back than. Any hints ?
Ciao
Volker
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
reply other threads:[~2008-02-20 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7zve4jhlra.fsf@vzell-de.de.oracle.com \
--to=dr.volker.zell@oracle.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).