<br><br><div class="gmail_quote">2010/11/7 Arjen de Korte<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Citeren Arnaud Quette<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Log:<br>
Exclude -I. and extra developer warning flags with Net-SNMP support enabled<br>
(using them is the responsibility of the NUT developers)<br>
<br>
Modified:<br>
branches/AsciiDoc/m4/nut_check_libnetsnmp.m4<br>
<br>
</blockquote>
<br>
Arjen,<br>
<br>
was this really intended to target the AsciiDoc branch?<br>
</blockquote>
<br></div>
Yes.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
note that I've not checked if it's simply a sync with trunk, but in this<br>
case you would probably have mentioned it...<br>
</blockquote>
<br></div>
It actually was a sync with the trunk. I get so many warnings with the -Wcase-qual flag from the NetSNMP --cflags that I decided to switch to the trunk version where we already have --base-cflags. When we merge the AsciiDoc into the trunk, this should be no problem.<br clear="all">
</blockquote></div><br>thanks for the confirmation Arjen.<br><br>cheers,<br>Arnaud<br><br>