HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Why if putting <limits> and <string> together ...
Operating System - HP-UX
1829208
Members
2598
Online
109987
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2006 06:37 AM
07-17-2006 06:37 AM
Why if putting <limits> and <string> together could cause warnings?
$ uname -a
HP-UX mildev01 B.11.23 U 9000/800
$ cat a.C
#include
#include
int i;
Compile(64bit build):
$ aCC -AA -Aa +DD64 +M2 -c a.C
Warning (suggestion) 818: "/opt/aCC/include_std/limits", line 681 # Type 'long' is larger than type 'wchar_t', truncation in value may result.
_RWSTD_SPECIALIZE_LIMITS (wchar_t, _RWSTD_INT_CONVERTIBLE, _RWST
^^^^^^^^^^^^^^^^^^^^^^^^
Warning (suggestion) 818: "/opt/aCC/include_std/limits", line 681 # Type 'unsigned long' is larger than type 'wchar_t', truncation in value may result.
_RWSTD_SPECIALIZE_LIMITS (wchar_t, _RWSTD_INT_CONVERTIBLE, _RWST
^^^^^^^^^^^^^^^^^^^^^^^^
If remove or from the file, the warning won't come out.
Anyone could explain the reason? How to solve their conflict?(I need both in the file)
Thanks,
Peter
HP-UX mildev01 B.11.23 U 9000/800
$ cat a.C
#include
#include
int i;
Compile(64bit build):
$ aCC -AA -Aa +DD64 +M2 -c a.C
Warning (suggestion) 818: "/opt/aCC/include_std/limits", line 681 # Type 'long' is larger than type 'wchar_t', truncation in value may result.
_RWSTD_SPECIALIZE_LIMITS (wchar_t, _RWSTD_INT_CONVERTIBLE, _RWST
^^^^^^^^^^^^^^^^^^^^^^^^
Warning (suggestion) 818: "/opt/aCC/include_std/limits", line 681 # Type 'unsigned long' is larger than type 'wchar_t', truncation in value may result.
_RWSTD_SPECIALIZE_LIMITS (wchar_t, _RWSTD_INT_CONVERTIBLE, _RWST
^^^^^^^^^^^^^^^^^^^^^^^^
If remove
Anyone could explain the reason? How to solve their conflict?(I need both in the file)
Thanks,
Peter
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2006 06:47 AM
07-17-2006 06:47 AM
Re: Why if putting <limits> and <string> together could cause warnings?
Shalom Peter,
Either you have code that conflicts with the haaders, or the headers are out of date and need replacement.
Or perhaps both.
SEP
Either you have code that conflicts with the haaders, or the headers are out of date and need replacement.
Or perhaps both.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2006 07:58 AM
07-17-2006 07:58 AM
Re: Why if putting <limits> and <string> together could cause warnings?
Steve, thanks for your reply.
You should see my code has just 3 lines. It shouldn't cause the conflict.
As for the system files, we are using HP supported versions and patches.
$ uname -a
HP-UX mildev01 B.11.23 U 9000/800
$ aCC -V
aCC: HP ANSI C++ B3910B A.03.65
It's better to test with my example code in your environment if you have same version OS and aCC.
You should see my code has just 3 lines. It shouldn't cause the conflict.
As for the system files, we are using HP supported versions and patches.
$ uname -a
HP-UX mildev01 B.11.23 U 9000/800
$ aCC -V
aCC: HP ANSI C++ B3910B A.03.65
It's better to test with my example code in your environment if you have same version OS and aCC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2006 04:34 PM
07-17-2006 04:34 PM
Re: Why if putting <limits> and <string> together could cause warnings?
Sounds like a very basic incompatibiltiy.
Check the dates on those include files: was either replaced?
Have you tried swapping those two include lines?
Try to include limits.h before string.h?
fwiw...
limits.h is documented in section-5 'limits'
http://docs.hp.com/en/B2355-90847docs/B2355-90847docs.pdf
Hein.
Check the dates on those include files: was either replaced?
Have you tried swapping those two include lines?
Try to include limits.h before string.h?
fwiw...
limits.h is documented in section-5 'limits'
http://docs.hp.com/en/B2355-90847docs/B2355-90847docs.pdf
Hein.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP