- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: bash + unresolved symbols
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-02-2006 05:29 AM
05-02-2006 05:29 AM
bash + unresolved symbols
I did install the dependent libraries gettext and libiconv.
I have unresolved symbols:
$ ldd -r `which bash`
[...]
symbol not found: __udivsi3 (/usr/local/bin/bash)
symbol not found: __umodsi3 (/usr/local/bin/bash)
Some kind of integer/arithmetic library? I have not run into this before, and am not sure what might have effected this change.
Ideas?
Regards,
Victoria
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 08:42 AM
05-02-2006 08:42 AM
Re: bash + unresolved symbols
Its not unknown to get software from the porting centre that does not work.
As I recall one of those two releases worked for me on PA-RISC 11i v1.
So you might want to see if the download went wrong or check the swlog.
SEP
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
05-02-2006 08:47 AM
05-02-2006 08:47 AM
Re: bash + unresolved symbols
Jeff Traigle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 10:39 AM
05-02-2006 10:39 AM
Re: bash + unresolved symbols
I did install gettext and libiconv prior to installing either bash.
I did install libgcc today, although I do not have and have not had that on my systems prior to installing it on the one system today.
Oh I also re-downloaded the depot and tried again, just for grins.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 04:33 PM
05-02-2006 04:33 PM
Re: bash + unresolved symbols
The pbm is because of gcc. So, install it correctly. And check libgcc.so is present. Also, look for the __udivsi3 in libgcc.so. you can do this by
strings libgcc.so | grep -i __udivsi3
This should show that symbol is there or not.
If not, reinstall GCC again. This should solve your pbm.
HTH,
Prabu.S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2006 06:06 AM
05-03-2006 06:06 AM
Re: bash + unresolved symbols
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2006 05:07 PM
11-22-2006 05:07 PM
Re: bash + unresolved symbols
bash-3.2-ia64-11.23.depot.gz
gtk+-1.2.10-ia64-11.23.depot.gz
ncurses-5.5-ia64-11.23.depot.gz
gcc-4.1.1-ia64-11.23.depot.gz
libgcc-4.1.1-ia64-11.23.depot.gz
vim-7.0-ia64-11.23.depot.gz
gettext-0.16-ia64-11.23.depot.gz
libiconv-1.11-ia64-11.23.depot.gz
xpm-3.4k-ia64-11.23.depot.gz
glib-1.2.10-ia64-11.22.depot.gz
make-3.81-ia64-11.23.depot.gz
, the sample problem happened.
# bash
/usr/lib/hpux32/dld.so: Unsatisfied code symbol '__udivsi3' in load module '/usr/local/bin/bash'.
Killed
and where is libgcc.so? I can not find it.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2007 04:27 AM
07-20-2007 04:27 AM
Re: bash + unresolved symbols
We have a build process that requires several GNU modules including :-
gcc-4.1.1-ia64-11.23.depot
gettext-0.15-ia64-11.23.depot
libiconv-1.11-ia64-11.23.depot
bash-3.1.17-ia64-11.23.depot
The error we were getting on just one server is listed below. Loads of others worked fine.
hiptc058 # bash
/usr/lib/hpux32/dld.so: Unsatisfied code symbol '__udivsi3' in load module '/usr/local/bin/bash'.
Killed
I removed bash and gcc, then installed them, but bash still failed.
The lively cause of our problem was that we had incompatible versions of GNU modules.
root@hiptc058# swlist | grep -i gcc
gcc 4.1.1 gcc
libgcc 4.1.2 libgcc
I removed libgcc, but this did not fix the problem. I removed gcc, gettext, libiconv, bash then installed them again. This fixed the problem!