- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: 32/64-bit portabliity
Operating System - Linux
1753408
Members
7230
Online
108793
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
Discussions
Discussions
Forums
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
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-02-2006 09:25 PM
тАО07-02-2006 09:25 PM
Re: 32/64-bit portabliity
Unfortunately, I can't change the terminfo database on the target machine (it isn't my machine). I'm attempting to get a copy of it to copy onto my machine to see if I can replicate the problem locally.
The application is statically linked with the ncurses archive libraries. There are no ncurses shared libraries on the target machine. Also, perhaps more importantly, there are no ncurses binaries on the target machine, it uses the HP supplied variants of clear/infocmp/tic/toe/tput/tset etc. so the target machine has HP terminfo databases and HP term habdling binaries.
I've been experimenting with setting TERMINFO and TERMCAP, but it doesn't seem to make any difference.
The application is statically linked with the ncurses archive libraries. There are no ncurses shared libraries on the target machine. Also, perhaps more importantly, there are no ncurses binaries on the target machine, it uses the HP supplied variants of clear/infocmp/tic/toe/tput/tset etc. so the target machine has HP terminfo databases and HP term habdling binaries.
I've been experimenting with setting TERMINFO and TERMCAP, but it doesn't seem to make any difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2006 09:39 PM
тАО07-02-2006 09:39 PM
Re: 32/64-bit portabliity
Oh and tic and infocmp both work OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2006 01:12 AM
тАО07-05-2006 01:12 AM
Re: 32/64-bit portabliity
OK, I recompiled the ncurses sources with --disable-termcap and ran the application.
If TERMINFO is not set, you get an error message. If TERMINFO is set (correctly) the application works fine.
Just to check, I then recompiled the ncurses sources without --disable-termcap and ran the application.
If TERMINFO is not set you don't (now) get a core-dump, you get an error message about "Name collision between h hh" etc. IF TERMINFO is set (correctly) the application works fine.
So unless the orginal ncurses build was somehow corrupted, I don't get it. But I have an application that works and I'm seeing if it works on the 32-bit version of 11.00 too.
If TERMINFO is not set, you get an error message. If TERMINFO is set (correctly) the application works fine.
Just to check, I then recompiled the ncurses sources without --disable-termcap and ran the application.
If TERMINFO is not set you don't (now) get a core-dump, you get an error message about "Name collision between h hh" etc. IF TERMINFO is set (correctly) the application works fine.
So unless the orginal ncurses build was somehow corrupted, I don't get it. But I have an application that works and I'm seeing if it works on the 32-bit version of 11.00 too.
- « Previous
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP