From: Steve Dickson <SteveD@redhat.com>
To: Giulio Troccoli
<Giulio.Troccoli-xnMMdYoS6WpEKMMhf/gKZA@public.gmane.org>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Compileing nfs-utils 1.1.5 on RHEL4 fails in tcpwrapper.c
Date: Fri, 27 Mar 2009 09:59:46 -0400 [thread overview]
Message-ID: <49CCDBD2.2000709@RedHat.com> (raw)
In-Reply-To: <6680A70380E6BA44A2D94ED7085718EE066A08079D@ln1exc03>
Giulio Troccoli wrote:
> Hi,
>
> I want to upgrade nfs-utils from 1.0.6 to 1.1.5, so I have downloaded the source code form sourceforge.net and issue the following ./configure command
>
> ./configure --disable-nfsv4 --disable-static --with-statduser=rpcuser --disable-gss
>
> Which finishes without errors. But then when I make I get the following
>
> make[2]: Entering directory `/usr/local/src/nfs-utils-1.1.5/support/misc'
> gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include -D_GNU_SOURCE -Wall -Wstrict-prototypes -pipe -g -O2 -MT tcpwrapper.o -MD -MP -MF .deps/tcpwrapper.Tpo -c -o tcpwrapper.o tcpwrapper.c
> tcpwrapper.c: In function `haccess_add':
> tcpwrapper.c:117: warning: implicit declaration of function `TAILQ_EMPTY'
> tcpwrapper.c:119: error: syntax error before "else"
> tcpwrapper.c: At top level:
> tcpwrapper.c:121: error: syntax error before '}' token
> tcpwrapper.c: In function `haccess_lookup':
> tcpwrapper.c:131: warning: implicit declaration of function `TAILQ_FOREACH'
> tcpwrapper.c:131: error: `list' undeclared (first use in this function)
> tcpwrapper.c:131: error: (Each undeclared identifier is reported only once
> tcpwrapper.c:131: error: for each function it appears in.)
> tcpwrapper.c:131: error: syntax error before '{' token
> make[2]: *** [tcpwrapper.o] Error 1
> make[2]: Leaving directory `/usr/local/src/nfs-utils-1.1.5/support/misc'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/local/src/nfs-utils-1.1.5/support'
> make: *** [all-recursive] Error 1
>
> I have found the TAILQ_ definitions in utils/idmapd/queue.h but most importantly in /usr/include/sys/queue.h which tcpwrapper.c should have picked up.
>
> Can anubody help? I'm not subscribed to the list so please make sure to CC me.
This is a bit strange... What environment are you compiling this in?
You can also try the "--without-tcp-wrappers" config flag
steved.
------------------------------------------------------------------------------
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2009-03-27 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 16:37 [NFS] Compileing nfs-utils 1.1.5 on RHEL4 fails in tcpwrapper.c Giulio Troccoli
2009-03-27 13:59 ` Steve Dickson [this message]
[not found] ` <49CCDBD2.2000709-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-27 14:15 ` Giulio Troccoli
[not found] ` <49CD07F5.1070005@RedHat.com>
[not found] ` <49CD07F5.1070005-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-30 9:06 ` Giulio Troccoli
2009-03-31 19:50 ` Steve Dickson
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=49CCDBD2.2000709@RedHat.com \
--to=steved@redhat.com \
--cc=Giulio.Troccoli-xnMMdYoS6WpEKMMhf/gKZA@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.