Re: Building projects on i386-pc-solaris2.8
On the solaris machine there are 3 linkers: /opt/sfw/bin/ld /usr/ucb/ld /usr/ccs/bin/ld If I do a `which ld` it returns /opt/sfw/bin/ld /opt/sfw/bin/c++ [amcintosh@amcintosh 11:57:49 src]# ls -la /opt/sfw/bin/c++ -r-xr-xr-x 2 root bin74868 May 21 2001 /opt/sfw/bin/c++ [amcintosh@amcintosh 11:58:06 src]# /opt/sfw/bin/c++ -v Reading specs from /opt/sfw/lib/gcc-lib/i386-pc-solaris2.8/2.95.3/specs gcc version 2.95.3 20010315 (release) Then if I simply compile from the command line: c++ -o libagent.so -fPIC -L/usr/local/lib -G Agent.o AgentObject.o AgentObjectLinux.o AgentObjectFactory.o Vector.o Attribute.o SharedLibrary.o SharedLibraryMgr.o Storage.o StorageFile.o AttributeContainer.o ObjectContainer.o AgentObjectVersion.o ODParser.o XMLParser.o XMLItem.o md5.o -lcrypt -ldl -lltapi12 -lltstd12 -lz The library builds fine. But if I use libtool to build it. I get many undefined symbols. The libtool script has: LD=/usr/ccs/bin/ld If i change LD=/opt/sfw/bin/ld is that enough? Or must I define LD_RUN_PATH and recompile libtool? any suggestions? Thanks in advance. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: Building projects on i386-pc-solaris2.8
Hi Allan, On the solaris machine there are 3 linkers: /opt/sfw/bin/ld /usr/ucb/ld /usr/ccs/bin/ld If I do a `which ld` it returns /opt/sfw/bin/ld /opt/sfw/bin/c++ [amcintosh@amcintosh 11:57:49 src]# ls -la /opt/sfw/bin/c++ -r-xr-xr-x 2 root bin74868 May 21 2001 /opt/sfw/bin/c++ [amcintosh@amcintosh 11:58:06 src]# /opt/sfw/bin/c++ -v Reading specs from /opt/sfw/lib/gcc-lib/i386-pc-solaris2.8/2.95.3/specs gcc version 2.95.3 20010315 (release) Then if I simply compile from the command line: c++ -o libagent.so -fPIC -L/usr/local/lib -G Agent.o AgentObject.o AgentObjectLinux.o AgentObjectFactory.o Vector.o Attribute.o SharedLibrary.o SharedLibraryMgr.o Storage.o StorageFile.o AttributeContainer.o ObjectContainer.o AgentObjectVersion.o ODParser.o XMLParser.o XMLItem.o md5.o -lcrypt -ldl -lltapi12 -lltstd12 -lz The library builds fine. But if I use libtool to build it. I get many undefined symbols. The libtool script has: LD=/usr/ccs/bin/ld I tried the same thing some time ago (about 2-3 months). Here are my two cents. (1) g++ links some objects implicitly. try to run g++ -v to see them. This means that if you just change g++ to ld it won't work. (2) the order in which this implicit files get linked IS important. That was one reason why libtool couldn't handle c++ properly (static object initializing...). BTW, I would love to know if it works with current version. It seems that you are using c++. Did you try it? HTH, -boris -- Boris Kolpackov mailto:[EMAIL PROTECTED] http://www.kolpackov.net 1024D/EBB172C3 - 9879 C89B 4985 4262 216B 4006 867F 3F22 EBB1 72C3 ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: Building projects on i386-pc-solaris2.8
Allan: It helps to specify the verson of Libtool you're using as well as the actual link line that Libtool creates. For my money I can't think of any reason why the link line you have here should work. It doesn't specify that you want to create a shared library. Rob Allan McIntosh wrote: On the solaris machine there are 3 linkers: /opt/sfw/bin/ld /usr/ucb/ld /usr/ccs/bin/ld If I do a `which ld` it returns /opt/sfw/bin/ld /opt/sfw/bin/c++ [amcintosh@amcintosh 11:57:49 src]# ls -la /opt/sfw/bin/c++ -r-xr-xr-x 2 root bin74868 May 21 2001 /opt/sfw/bin/c++ [amcintosh@amcintosh 11:58:06 src]# /opt/sfw/bin/c++ -v Reading specs from /opt/sfw/lib/gcc-lib/i386-pc-solaris2.8/2.95.3/specs gcc version 2.95.3 20010315 (release) Then if I simply compile from the command line: c++ -o libagent.so -fPIC -L/usr/local/lib -G Agent.o AgentObject.o AgentObjectLinux.o AgentObjectFactory.o Vector.o Attribute.o SharedLibrary.o SharedLibraryMgr.o Storage.o StorageFile.o AttributeContainer.o ObjectContainer.o AgentObjectVersion.o ODParser.o XMLParser.o XMLItem.o md5.o -lcrypt -ldl -lltapi12 -lltstd12 -lz The library builds fine. But if I use libtool to build it. I get many undefined symbols. The libtool script has: LD=/usr/ccs/bin/ld If i change LD=/opt/sfw/bin/ld is that enough? Or must I define LD_RUN_PATH and recompile libtool? any suggestions? Thanks in advance. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool -- Robert Boehne Software Engineer Ricardo Software Chicago Technical Center TEL: (630)789-0003 x. 238 FAX: (630)789-0127 email: [EMAIL PROTECTED] ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Building projects on i386-pc-solaris2.8
Hey, I rewrote a project's build process to use autotools and libtool. Everything builds fine but the binary seg faults at run time(in i386 solaris2.8 ). Does anyone know of any issues or AC_ AM_ macros that are absolutely required to build shared objects and dynamicly linked binaries(when porting to intel solaris2.8)? The binary builds and runs fine on Redhat 7.2. However when I build the target in i386-pc-solaris2.8 it segment faults when I run it. If I build it with out libtool and autotools it is fine. My make set up builds a few binarys that link to existing libs as well as some of the shared objects and libraries built with in the project. Not sure if the info I have included is helpful or not. Thanks in advance. i386-pc-solaris2.8 gcc version 2.95.3 20010315 (release) libtool 1.4.2 Al ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: Building projects on i386-pc-solaris2.8
On Thu, Jan 31, 2002 at 02:04:27PM -0500, Allan McIntosh wrote: I rewrote a project's build process to use autotools and libtool. Everything builds fine but the binary seg faults at run time(in i386 solaris2.8 ). Does anyone know of any issues or AC_ AM_ macros that are absolutely required to build shared objects and dynamicly linked binaries(when porting to intel solaris2.8)? The binary builds and runs fine on Redhat 7.2. However when I build the target in i386-pc-solaris2.8 it segment faults when I run it. If I build it with out libtool and autotools it is fine. Even if you --disable-shared? -- albert chin ([EMAIL PROTECTED]) ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: Building projects on i386-pc-solaris2.8
On Thu, Jan 31, 2002 at 02:04:27PM -0500, Allan McIntosh wrote: I rewrote a project's build process to use autotools and libtool. Everything builds fine but the binary seg faults at run time(in i386 solaris2.8 ). Does anyone know of any issues or AC_ AM_ macros that are absolutely required to build shared objects and dynamicly linked binaries(when porting to intel solaris2.8)? The binary builds and runs fine on Redhat 7.2. However when I build the target in i386-pc-solaris2.8 it segment faults when I run it. If I build it with out libtool and autotools it is fine. Even if you --disable-shared? Then I get ld errors: Undefined first referenced symbol in file url_open /usr/local/lib/libltapi12.a(sgmlfiles.o) Fprintf /usr/local/lib/libltapi12.a(sgmllib.o) strcasecmp8 /usr/local/lib/libltapi12.a(sgmlparse.o) url_merge /usr/local/lib/libltapi12.a(dtd.o) Toupper /usr/local/lib/libltapi12.a(query.o) LTSTD_set_error_handler /usr/local/lib/libltapi12.a(sgmllib.o) LTSTDError /usr/local/lib/libltapi12.a(sgmllib.o) CharacterEncodingName /usr/local/lib/libltapi12.a(sgmlfiles.o) -- Allan McIntosh, Software Designer http://www.atreus-systems.com Phone: (613) 233-1741, (800) 764-5514 Ext 217 -- ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
