From this comment:

 *        d_Gconvert='gconvert((x),(n),(t),(b))'
 *        d_Gconvert='gcvt((x),(n),(b))'
 *        d_Gconvert='sprintf((b),"%.*g",(n),(x))'

[download]

... I assume that you should be able to influence the value of the Gconvert macro by supplying a value on the ./Configure command line:

sh ./Configure -des -DGconvert='sprintf(...)'

[download]
# or maybe
d_Gconvert='sprintf(...)' sh ./Configure -des

(but I have not tested this, nor do I really know how to determine if what I see is correct ;) )

The "real fix", I guess, would be to extend the Configure unit for Gconvert (likely d_gconvert.U) to check the output of the respective C programs and then choose an appropriate value...

Update: See below for Tux approach of setting up a Policy.sh file, to evade quoting problems etc

In reply to Re: Influencing the Gconvert macro by Corion
in thread Influencing the Gconvert macro by syphilis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.