HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Seemingly valid C libraries with no symbols
Operating System - HP-UX
1832919
Members
2755
Online
110048
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-2003 01:51 AM
07-17-2003 01:51 AM
Seemingly valid C libraries with no symbols
I've recentlty been working on some porting, so I've employed depot installs for my tools and some of the requirement libs. I've used depots from the HP-UX Porting Kit CDs and from the HP Porting Archives. I've had a problem with several of the shared libraries (*.sl) having no symbols, as reported by the linker and by nm.
The libraries are not zero byte and look valid, and the static libraries seem okey, but libs from both places have this problem. The main libs in question are: libz, libpng, libtiff, libungif, libjpeg. I manually got libz to build from source and it's compiled lib seems fine, but had serious trouble building PNG and JPEG, and I haven't tried building ungif from source yet....and frankly I don't care to spend my time working on the HP-UX port of JPEG and PNG, I'd much rather get to the stuff I actually want to port.
Has anyone seen this? Is it possibly a linker toolset problem that has a patch? I can't belive that both HP and the HPPA are distrubuting libraries that don't work.
Any help is appreciated.
benr.
The libraries are not zero byte and look valid, and the static libraries seem okey, but libs from both places have this problem. The main libs in question are: libz, libpng, libtiff, libungif, libjpeg. I manually got libz to build from source and it's compiled lib seems fine, but had serious trouble building PNG and JPEG, and I haven't tried building ungif from source yet....and frankly I don't care to spend my time working on the HP-UX port of JPEG and PNG, I'd much rather get to the stuff I actually want to port.
Has anyone seen this? Is it possibly a linker toolset problem that has a patch? I can't belive that both HP and the HPPA are distrubuting libraries that don't work.
Any help is appreciated.
benr.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 02:32 AM
07-17-2003 02:32 AM
Re: Seemingly valid C libraries with no symbols
Chances are you're looking at libraries that have had the symbol table stripped from them. The libraries can function fine without this information, it is really just there for debugging purposes, so you should still be able to link with them. See the strip(1) man page for more information.
This is common practice for proprietary software - it makes it more difficult for things to be reverse engineered. It also reduces the size of the binaries.
Regards,
Steve
This is common practice for proprietary software - it makes it more difficult for things to be reverse engineered. It also reduces the size of the binaries.
Regards,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 02:51 AM
07-17-2003 02:51 AM
Re: Seemingly valid C libraries with no symbols
Hi,
Yes, the compilation will have been done with the "-s" option - this is for both "gcc" and "cc".
I've successfully compiled "libpng" recently. What was your problem?
Ollie.
Yes, the compilation will have been done with the "-s" option - this is for both "gcc" and "cc".
I've successfully compiled "libpng" recently. What was your problem?
Ollie.
To err is human but to not award points is unforgivable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2003 08:39 AM
07-18-2003 08:39 AM
Re: Seemingly valid C libraries with no symbols
There is a separate list of symbols used by shared libraries. It remains even when the symbols reported by nm have been stripped off. You can see the shared library symbol list for 32-bit PA-RISC libraries using
/usr/ccs/bin/odump -slexportlist libN.sl
for defined symbols and
/usr/ccs/bin/odump -slimportlist libN.sl
for wanted symbols. Some symbols will be both exported and imported. That means they are defined by the library but can be overridden by an earlier definition from a program or another library.
You can see the shared library symbol list for 64-bit PA-RISC libraries and IPF libraries using
elfdump -s -n .dynsym libN.sl
or
elfdump -s -n .dynsym libN.so
/usr/ccs/bin/odump -slexportlist libN.sl
for defined symbols and
/usr/ccs/bin/odump -slimportlist libN.sl
for wanted symbols. Some symbols will be both exported and imported. That means they are defined by the library but can be overridden by an earlier definition from a program or another library.
You can see the shared library symbol list for 64-bit PA-RISC libraries and IPF libraries using
elfdump -s -n .dynsym libN.sl
or
elfdump -s -n .dynsym libN.so
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