Hi Ben,
> The only point I'm not clear on is the note about using a fixed size
> array allocation instead of the dynamic one. Is it acceptable to use
> HOST_NAME_MAX + 1 to achieve a size that is known to the compiler at
> compile time
Yes. Stack allocations are OK up to a size of ca. 4096. HOST
Hi!
coreutils does not allow to use a VPATH with "make dist"; I now use this
gen-ChangeLog rule in GnuPG to allow VPATH builds:
gen_start_date = 2011-12-01T06:00:00
.PHONY: gen-ChangeLog
gen-ChangeLog:
if test -d $(top_srcdir)/.git; then \
(cd $(top_s
When running a testsuite on FreeBSD, I saw a lot of:
1+ records in
0+1 records out
10 bytes transferred in 0.63 secs (158875 bytes/sec)
literring the testsuite, and traced it to the fact that we
were silencing one, but not the other, dd usage in our fallback.
* build-aux/mktempd (rand_bytes)
On 11/29/2011 02:05 PM, Paul Eggert wrote:
> On 11/29/11 09:35, Jim Meyering wrote:
>> + gl_WARN_ADD([-Wno-unsuffixed-float-constants])
>
> How about if we remove -Wunsuffixed-float-constants from
> manywarnings.m4? In practice it typically causes more
> trouble than it cures (the above-quoted g
Eric Blake writes:
> I've just found another problem with the manywarnings module:
>
> gcc 4.6.2 handles -Wabi and -Wdeprecated just fine for C code (I don't
> know if it is silently ignored, or if it could actually trigger); but
> gcc 4.2.1 (as shipped on FreeBSD) complains:
>
> cc1: warning: co
