Bug 1171 - configure can't always figure out LLONG_MAX.
Summary: configure can't always figure out LLONG_MAX.
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: -current
Hardware: Other All
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks: V_4_4
  Show dependency treegraph
 
Reported: 2006-03-03 16:40 AEDT by Darren Tucker
Modified: 2006-09-28 19:26 AEST (History)
0 users

See Also:


Attachments
reinvent the "%lld" wheel of printf. (2.10 KB, patch)
2006-03-03 16:42 AEDT, Darren Tucker
djm: ok+
Details | Diff
configure.gz: configure from 4.3p2 rebuilt with patch #1089 (75.67 KB, application/octet-stream)
2006-03-04 09:05 AEDT, Darren Tucker
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Tucker 2006-03-03 16:40:32 AEDT
Apparently the fix for bug #1104 doesn't cover all cases.

Some Tru64 systems have slightly different arch-vendor-os triples (eg "alphaev56-dec-osf4.0e") and some really old systems (AIX 3, Ultrix) have a similar problem with printf("%lld", n);

I will attach a patch to (hopefully) fix the general case and remove the Tru64 specific hack.
Comment 1 Darren Tucker 2006-03-03 16:42:17 AEDT
Created attachment 1089 [details]
reinvent the "%lld" wheel of printf.
Comment 2 Darren Tucker 2006-03-04 09:05:51 AEDT
Created attachment 1090 [details]
configure.gz: configure from 4.3p2 rebuilt with patch #1089

A rebuilt configure for those without autoconf handy.  Replace the configure from 4.3p2 with this one and re-run ./configure.
Comment 3 Damien Miller 2006-03-12 15:07:56 AEDT
Comment on attachment 1089 [details]
reinvent the "%lld" wheel of printf.

looks ok to me, but i am not in a position to test
Comment 4 Darren Tucker 2006-03-13 19:08:45 AEDT
(In reply to comment #3)
> (From update of attachment 1089 [details] [edit])
> looks ok to me, but i am not in a position to test

The original reporter was able to test successfully (thanks!)

Patch applied, will be in 4.4p*.
Comment 5 Darren Tucker 2006-09-28 19:26:01 AEST
With the release of 4.4, we believe that this bug is now closed.  For information about the release please see http://www.openssh.com/txt/release-4.4 .