NSD 2.3.4 is a bugfix release.
Please see the README document for configuration and installation
instructions.
You can download NSD from http://www.nlnetlabs.nl/nsd/
sha1: c9e3959ab61fecaa78f64fda9d19abd06309015a
2.3.4
Hello, allow me inform you the failure occured while
building NSD 2.3.4.
NSD 2.3.4 is a bugfix release.
Please see the README document for configuration and installation
instructions.
Summary:
make fails with the message 'Error expanding embedded variable.'
Condition:
OS is FreeBSD 4.11-RELEASE-p16
make is /usr/bin/make on it.
Everything seems good with GNU make. It was okey with
/usr/bin/make on NSD 2.3.3.
I noticed two odd things.
1. configure lefts the message '[: unexpected operator'.
2. @nsdxfer@ is left on Makefile generated by configure.
What's the matter?
The following is the almost everything I experienced.
Script started on Mon May 8 16:17:15 2006
kohi@alphonse[1]% uname -a
FreeBSD alphonse 4.11-RELEASE-p16 FreeBSD 4.11-RELEASE-p16 #7: Thu Mar 23 14:57:12 JST 2006 kohi@alphonse:/u/FreeBSD4/usr/src-RELENG_4_11/sys/compile/alphonse i386
kohi@alphonse[2]% which make
/usr/bin/make
kohi@alphonse[3]% ./configure
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for gcc... gcc
:
(snip)
:
checking for library containing yp_get_default_domain... none required
checking for SSL... found in /usr
checking for HMAC_CTX_init in -lcrypto... yes
[: unexpected operator
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
kohi@alphonse[4]% sed -ne '1,/^CC/p' Makefile
[On 08 May, @09:28, Koh-ichi Ito wrote in "Re: ANNOUNCEMENT: NSD 2.3.4 re ..."]
Hello, allow me inform you the failure occured while
building NSD 2.3.4.> Please see the README document for configuration and installation
> instructions.Summary:
make fails with the message 'Error expanding embedded variable.'Condition:
OS is FreeBSD 4.11-RELEASE-p16
make is /usr/bin/make on it.Everything seems good with GNU make. It was okey with
/usr/bin/make on NSD 2.3.3.
ahh, yes this is because of the addition of the unit test target
which introduces some gnuism in the Makefile.. I will try to get
work around this, or disable this in our release Makefile.in
I noticed two odd things.
1. configure lefts the message '[: unexpected operator'.
On freebsd 6 I cannot reproduce this... And I don't have access
to freebsd 4 to test it...
2. @nsdxfer@ is left on Makefile generated by configure.
This was also in the 2.3.3 (and before) release and can go.
Thanks for your report,
Greetings,
> I noticed two odd things.
>
> 1. configure lefts the message '[: unexpected operator'.On freebsd 6 I cannot reproduce this... And I don't have access
to freebsd 4 to test it...
On the other hand, I have no access to FreeBSD 6 
I tried on lab machine with FreeBSD 5.4, and it occurs, too.
I found it. Here is the point.
configure:
7919 # big fat warning
7920 if [ "$enable_checking" == "yes" ]; then
7921 echo "************************************************"
7922 echo "* You have activated \"--enable-checking\" *"
7923 echo "* *"
7924 echo "* This will instruct NSD to be stricter *"
7925 echo "* when validating its input. This could lead *"
7926 echo "* to a reduced service level. *"
7927 echo "************************************************"
7928 fi
Though I can't check it on FreeBSD 6, on FreeBSD 4 and
FreeBSD 5, operator "==" isn't described on test(1), so "["
says "==" as "invalid operator", I guess.
Because I'm not familiar with autoconf, I can't distinguish
this is your issue or autoconf's issue.
Overall, this issue may not causes practical problem,
doesn't it?
Thanks
Koh-ichi Ito
BroadBand Tower
[On 09 May, @08:56, Koh-ichi Ito wrote in "Re: ANNOUNCEMENT: NSD 2.3.4 re ..."]
> > 1. configure lefts the message '[: unexpected operator'.
>
> On freebsd 6 I cannot reproduce this... And I don't have access
> to freebsd 4 to test it...On the other hand, I have no access to FreeBSD 6
I tried on lab machine with FreeBSD 5.4, and it occurs, too.
I found it. Here is the point.
Overall, this issue may not causes practical problem,
doesn't it?
no,
thanks for the fix,
regards,