- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: __modsi3 and __divdi3 error
Operating System - Linux
1753477
Members
6023
Online
108794
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
тАО05-12-2006 08:01 PM
тАО05-12-2006 08:01 PM
__modsi3 and __divdi3 error
Hi All,
I have managed to compile my apache1.3.31 in 64 bits on my 11.23 ia64 itanium with
CFLAGS="-mlp64", CPPFLAGS="-mlp64",
LDFLAGS="-lgcc"
The issue is that there are 2 modules that behave funny. All modules do not have error.
The two are mod_imap.so and libproxy.so.
I also tried to compile with option:
LDFLAGS=/opt/hp-gcc-4.1.0/lib/gcc/ia64-hp-hpux11.23/4.1.0/hpux64/libgcc.a -lgcc
but the error still exit.
Below is the error:
1) mod_imap.so
/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__modsi3' in load module '/apps/apache/libexec/mod_imap.so'.
Syntax error on line 219 of /apps/apache/conf/httpd.conf:
Cannot load /apps/apache/libexec/mod_imap.so into server: Unresolved external
2) libproxy.so
/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__divdi3' in load module '/apps/apache/libexec/libproxy.so'.
Syntax error on line 230 of /apps/apache/conf/httpd.conf:
Cannot load /apps/apache/libexec/libproxy.so into server: Unresolved external
Any help is greatly appreciated.
I have managed to compile my apache1.3.31 in 64 bits on my 11.23 ia64 itanium with
CFLAGS="-mlp64", CPPFLAGS="-mlp64",
LDFLAGS="-lgcc"
The issue is that there are 2 modules that behave funny. All modules do not have error.
The two are mod_imap.so and libproxy.so.
I also tried to compile with option:
LDFLAGS=/opt/hp-gcc-4.1.0/lib/gcc/ia64-hp-hpux11.23/4.1.0/hpux64/libgcc.a -lgcc
but the error still exit.
Below is the error:
1) mod_imap.so
/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__modsi3' in load module '/apps/apache/libexec/mod_imap.so'.
Syntax error on line 219 of /apps/apache/conf/httpd.conf:
Cannot load /apps/apache/libexec/mod_imap.so into server: Unresolved external
2) libproxy.so
/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__divdi3' in load module '/apps/apache/libexec/libproxy.so'.
Syntax error on line 230 of /apps/apache/conf/httpd.conf:
Cannot load /apps/apache/libexec/libproxy.so into server: Unresolved external
Any help is greatly appreciated.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2006 01:47 AM
тАО05-26-2006 01:47 AM
Re: __modsi3 and __divdi3 error
I don't know about __modsi3 (there is a __moddi3 ?), but __divdi3 should be defined in libgcc.a
If you copy your libgcc.a into (say) /tmp, then extract the object files from it, you should see that __divdi3 is defined in _divdi3.o
e.g.
cp/libgcc.a /tmp
cd /tmp
ar -x libgcc.a
nm _divdi3.o | grep "__divdi3"
nm _moddi3.o | grep "__moddi3"
should return something like ...
00000000 T __divdi3
00000000 T __moddi3
If you copy your libgcc.a into (say) /tmp, then extract the object files from it, you should see that __divdi3 is defined in _divdi3.o
e.g.
cp
cd /tmp
ar -x libgcc.a
nm _divdi3.o | grep "__divdi3"
nm _moddi3.o | grep "__moddi3"
should return something like ...
00000000 T __divdi3
00000000 T __moddi3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2007 09:08 PM
тАО07-06-2007 09:08 PM
Re: __modsi3 and __divdi3 error
I saw a recent thread that I solved that finally may explain your unsat. Where did you put the LDFLAGS macro?
You should NOT be using LDFLAGS for including libs, you should use another macro that you place at the END of the link line.
You should NOT be using LDFLAGS for including libs, you should use another macro that you place at the END of the link line.
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