| Bug #4757 | Ndb fails to start on IRIX | ||
|---|---|---|---|
| Submitted: | 26 Jul 2004 20:59 | Modified: | 26 Oct 2004 14:24 |
| Reporter: | Jonas Oreland | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | OS: | Other (IRIX) | |
| Assigned to: | Joe Pendleton | CPU Architecture: | Any |
fixed
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.048 sec. using MySQL 8.4.5-u11-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2026, Oracle Corporation and/or its affiliates
Description: irix> man snprintf <-- snip Each function returns the number of characters transmitted (not including the terminating null character in the case of snprintf and sprintf) or a negative value if an output error was encountered. If snprintf is used in strict Unix98 compliance mode (_XOPEN_SOURCE >= 500) and more than len bytes of output would be generated, the return value will be the number of bytes that would be written to s had len been sufficiently large (not including the terminating null character.) --> Ndb relies on Unix98 behavior. Have not fixed define stuff... How to repeat: