|
From: | mwoehlke |
Subject: | Re: proposed patch to allocsa, vasnprintf for Tandem NSK (OSS) |
Date: | Wed, 11 Oct 2006 14:29:50 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 |
Paul Eggert wrote:
Here are some proposed changes to the gnulib allocsa and vasnprintf modules prompted by the needs of porting coreutils to Tandem NSK (OSS), along with modernizing the code to use the newer macros like AC_TYPE_LONG_LONG_INT rather than the older macros like gl_AC_TYPE_LONG_LONG. I haven't tested these changes on Tandem but have compiled and run them on Debian stable x86 and in principle they look fairly safe to me. [snip]
In the midst of all these changes to printf-friends, is anyone (else) aware that the 'long long' suffix for the system printf on OSS is "L" ("ll" is not recognized)?
================================ $ cat bar.c #include <stdio.h> int main() { long long m = 0x12345678AB; printf("%Ld\n", m); return 0; } $ cc -o bar bar.c cc: info: checking "bar" for unresolved symbols. $ ./bar 78187493547 ================================ $ cat bar.c #include <stdio.h> int main() { long long m = 0x12345678AB; printf("%lld\n", m); return 0; } $ cc -o bar bar.c cc: info: checking "bar" for unresolved symbols. $ ./bar ld ================================ -- Matthew Will your shell have salvation? Only if it's Bourne Again.
[Prev in Thread] | Current Thread | [Next in Thread] |