If you can't or won't spend time in fixing compline/d_gconvert.U ...

If I can fix it, then I will undertake to do so.
At the moment, however, I have no idea how d_gconvert.U fits into "the scheme of things".
AFAICS, it's not part of the perl source.

... but I am always scared of interpolation when requiring quotes

I bothers me a bit, too. Although the configure option that I used seems to have done the trick, it wasn't exactly noiseless:

In file included from sv.c:32:0:
sv.c: In function ‘Perl_sv_vcatpvfn_flags’:
config.h:909:39: warning: ‘%.*g’ directive writing between 1 and 133 b
+ytes into a region of size 127 [-Wformat-overflow=]
 #define Gconvert(x,n,t,b) sprintf((b),"%.*g",(n),(x))
                                       ^
perl.h:6791:13: note: in definition of macro ‘WITH_LC_NUMERIC_SET_TO_N
+EEDED_IN’
             block;                                                   
+       \
             ^~~~~
sv.c:48:5: note: in expansion of macro ‘PERL_UNUSED_RESULT’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
     ^~~~~~~~~~~~~~~~~~
sv.c:48:24: note: in expansion of macro ‘Gconvert’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
                        ^~~~~~~~
sv.c:13118:21: note: in expansion of macro ‘SNPRINTF_G’
                     SNPRINTF_G(fv, ebuf, sizeof(ebuf), precis)
                     ^
config.h:909:39: note: assuming directive output of 132 bytes
 #define Gconvert(x,n,t,b) sprintf((b),"%.*g",(n),(x))
                                       ^
perl.h:6791:13: note: in definition of macro ‘WITH_LC_NUMERIC_SET_TO_N
+EEDED_IN’
             block;                                                   
+       \
             ^~~~~
sv.c:48:5: note: in expansion of macro ‘PERL_UNUSED_RESULT’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
     ^~~~~~~~~~~~~~~~~~
sv.c:48:24: note: in expansion of macro ‘Gconvert’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
                        ^~~~~~~~
sv.c:13118:21: note: in expansion of macro ‘SNPRINTF_G’
                     SNPRINTF_G(fv, ebuf, sizeof(ebuf), precis)
                     ^
In file included from /usr/include/stdio.h:862:0,
                 from perlio.h:41,
                 from iperlsys.h:50,
                 from perl.h:3934,
                 from sv.c:32:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___
+sprintf_chk’ output between 2 and 134 bytes into a destination of siz
+e 127
   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       __bos (__s), __fmt, __va_arg_pack ());
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from sv.c:32:0:
config.h:909:39: warning: ‘%.*g’ directive writing between 1 and 133 b
+ytes into a region of size 127 [-Wformat-overflow=]
 #define Gconvert(x,n,t,b) sprintf((b),"%.*g",(n),(x))
                                       ^
perl.h:6791:13: note: in definition of macro ‘WITH_LC_NUMERIC_SET_TO_N
+EEDED_IN’
             block;                                                   
+       \
             ^~~~~
sv.c:48:5: note: in expansion of macro ‘PERL_UNUSED_RESULT’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
     ^~~~~~~~~~~~~~~~~~
sv.c:48:24: note: in expansion of macro ‘Gconvert’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
                        ^~~~~~~~
sv.c:13118:21: note: in expansion of macro ‘SNPRINTF_G’
                     SNPRINTF_G(fv, ebuf, sizeof(ebuf), precis)
                     ^
config.h:909:39: note: assuming directive output of 132 bytes
 #define Gconvert(x,n,t,b) sprintf((b),"%.*g",(n),(x))
                                       ^
perl.h:6791:13: note: in definition of macro ‘WITH_LC_NUMERIC_SET_TO_N
+EEDED_IN’
             block;                                                   
+       \
             ^~~~~
sv.c:48:5: note: in expansion of macro ‘PERL_UNUSED_RESULT’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
     ^~~~~~~~~~~~~~~~~~
sv.c:48:24: note: in expansion of macro ‘Gconvert’
     PERL_UNUSED_RESULT(Gconvert((NV)(nv), (int)ndig, 0, buffer))
                        ^~~~~~~~
sv.c:13118:21: note: in expansion of macro ‘SNPRINTF_G’
                     SNPRINTF_G(fv, ebuf, sizeof(ebuf), precis)
                     ^
In file included from /usr/include/stdio.h:862:0,
                 from perlio.h:41,
                 from iperlsys.h:50,
                 from perl.h:3934,
                 from sv.c:32:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___
+sprintf_chk’ output between 2 and 134 bytes into a destination of siz
+e 127
   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       __bos (__s), __fmt, __va_arg_pack ());
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[download]

Of course, I probably should at least run make test before I start getting too excited about how successful it has been ;-)

Cheers,
Rob

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.