Bug 464 - Conditionally define MAXHOSTNAMELEN
Conditionally define MAXHOSTNAMELEN
Status: RESOLVED FIXED
Product: NSD
Classification: Unclassified
Component: NSD Code
3.2.x
i386 other
: P5 enhancement
Assigned To: NSD team
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-16 12:25 CEST by Jeroen Schot
Modified: 2012-08-21 11:04 CEST (History)
1 user (show)

See Also:


Attachments
Patch to conditionally define MAXHOSTNAMELEN (348 bytes, application/octet-stream)
2012-08-16 12:25 CEST, Jeroen Schot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeroen Schot 2012-08-16 12:25:39 CEST
Created attachment 211 [details]
Patch to conditionally define MAXHOSTNAMELEN

Hello,

NSD uses MAXHOSTNAMELEN, which doesn't exist on some platforms (for example GNU/Hurd). The Debian package contains the attached 3-line patch to set it to a reasonable value on these platforms.

Kinds regards,
Jeroen Schot
Comment 1 Matthijs Mekking 2012-08-21 11:04:02 CEST
Hi Jeroen, 

Thanks for your report. We have a macro for checking the MAXHOSTNAMELEN, it was not called by the configure.ac script.

Since we have a common macro for it, lets use it:-) :

--- branches/NSD_3_2/configure.ac	2012-08-21 08:41:09 UTC (rev 3635)
+++ branches/NSD_3_2/configure.ac	2012-08-21 08:58:14 UTC (rev 3636)
@@ -807,6 +807,7 @@
 ])
 AH_BOTTOM(
 AHX_MEMCMP_BROKEN(nsd)
+AHX_CONFIG_MAXHOSTNAMELEN
 )
 AH_BOTTOM([

Also applied to trunk.