https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787655#M93863 I saw a recent thread that I solved that finally may explain your unsat. Where did you put the LDFLAGS macro?<BR /><BR />You should NOT be using LDFLAGS for including libs, you should use another macro that you place at the END of the link line. Sat, 07 Jul 2007 04:08:34 GMT Dennis Handly 2007-07-07T04:08:34Z https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787653#M93861 Hi All,<BR /><BR />I have managed to compile my apache1.3.31 in 64 bits on my 11.23 ia64 itanium with<BR />CFLAGS="-mlp64", CPPFLAGS="-mlp64", <BR />LDFLAGS="-lgcc"<BR /><BR />The issue is that there are 2 modules that behave funny. All modules do not have error.<BR />The two are mod_imap.so and libproxy.so.<BR /><BR />I also tried to compile with option:<BR />LDFLAGS=/opt/hp-gcc-4.1.0/lib/gcc/ia64-hp-hpux11.23/4.1.0/hpux64/libgcc.a -lgcc<BR />but the error still exit.<BR /><BR />Below is the error:<BR />1) mod_imap.so<BR /><BR />/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__modsi3' in load module '/apps/apache/libexec/mod_imap.so'.<BR />Syntax error on line 219 of /apps/apache/conf/httpd.conf:<BR />Cannot load /apps/apache/libexec/mod_imap.so into server: Unresolved external<BR /><BR />2) libproxy.so<BR />/usr/lib/hpux64/dld.so: Unsatisfied code symbol '__divdi3' in load module '/apps/apache/libexec/libproxy.so'.<BR />Syntax error on line 230 of /apps/apache/conf/httpd.conf:<BR />Cannot load /apps/apache/libexec/libproxy.so into server: Unresolved external<BR /><BR />Any help is greatly appreciated.<BR /> Sat, 13 May 2006 03:01:12 GMT https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787653#M93861 Steven_181 2006-05-13T03:01:12Z https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787654#M93862 I don't know about __modsi3 (there is a __moddi3 ?), but __divdi3 should be defined in libgcc.a<BR /><BR />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<BR /><BR />e.g.<BR /><BR />cp <YOUR path="">/libgcc.a /tmp<BR />cd /tmp<BR />ar -x libgcc.a<BR />nm _divdi3.o | grep "__divdi3"<BR />nm _moddi3.o | grep "__moddi3"<BR /><BR />should return something like ...<BR /><BR />00000000 T __divdi3<BR />00000000 T __moddi3<BR /><BR /></YOUR> Fri, 26 May 2006 08:47:43 GMT https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787654#M93862 Stephen Keane 2006-05-26T08:47:43Z https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787655#M93863 I saw a recent thread that I solved that finally may explain your unsat. Where did you put the LDFLAGS macro?<BR /><BR />You should NOT be using LDFLAGS for including libs, you should use another macro that you place at the END of the link line. Sat, 07 Jul 2007 04:08:34 GMT https://community.hpe.com/t5/operating-system-linux/modsi3-and-divdi3-error/m-p/3787655#M93863 Dennis Handly 2007-07-07T04:08:34Z