automake/libtool question
I'm looking for a suggestion as to the best way to have some common source code to multiple libraries outside of the directory the library is made in. I've tried LIBADD with .lo files and had problems with libtool resolving that the source file x.c is the same even though the path to it is different relative to the path when the .lo is created (ie the ../../ type stuff confused it or something so I get lots of errors with regards to redefinition of blah). I've tried including the source paths into the _la_SOURCES line with $(top_srcdir)/native/lib/jcl.c for example and automake complains about source file in a subdirectory is not supported. So, since I'm using automake 1.4 and libtool 1.3.5 does this mean I should try upgrading to automake 1.5 and libtool 1.4.2? The warning about inter-library dependencies was removed in libtool 1.4.2 info documentation but no one seemed to bother to provide a clear example of how to use it for libraries that haven't been installed yet. I've avoid the inter-library thing so far because I think that with the way VMs load the single shared library we specify in our source that making one shared library dependent on another could be problematic. Anyone with experience with this? Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: automake/libtool question
> "Brian" == Brian Jones <[EMAIL PROTECTED]> writes: Brian> So, since I'm using automake 1.4 and libtool 1.3.5 does this Brian> mean I should try upgrading to automake 1.5 and libtool 1.4.2? Automake 1.5 has much better support for using source files in other directories. It still isn't perfect, but it's definitely an improvement. Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Why upgrading sucks
I had to share my pain so I hope someone else finds this funny. Tonight I updated to Red Hat 7.2 and afterwards applied the necessary updates as noted by Red Hat. Then I created RPMs of the newest libtool, automake, and autoconf and installed those. After twiddling with the various files like updating ltmain.sh and adding depcomp turns out that the Jikes I now have seg faults building our source... so I'm going to sleep. I'll install gcc 3.0.2 soon (in a standalone fashion away from my current gcc) and presumably won't have to deal with the Jikes problem. Hopefully Eric Blake can shed some light on this and offer a suggestion for what Jikes to use. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Why upgrading sucks
Once again, I meant to send my reply to the list originally... Eric Blake wrote: > > Brian Jones wrote: > > > > I had to share my pain so I hope someone else finds this funny. > > Tonight I updated to Red Hat 7.2 and afterwards applied the necessary > > updates as noted by Red Hat. Then I created RPMs of the newest > > libtool, automake, and autoconf and installed those. After twiddling > > with the various files like updating ltmain.sh and adding depcomp > > turns out that the Jikes I now have seg faults building our > > source... so I'm going to sleep. I'll install gcc 3.0.2 soon (in a > > standalone fashion away from my current gcc) and presumably won't have > > to deal with the Jikes problem. Hopefully Eric Blake can shed some > > light on this and offer a suggestion for what Jikes to use. > > Which version of jikes does RedHat 7.2 ship with? 1.15 has some known > segfaults when compiling nested classes in a static context, which > escaped through the release process. The patch that caused the problems > has since been reverted from CVS, if you are willing to try > bleeding-edge versions. Or, if you prefer a specific time, the > ChangeLog shows that the regression was fixed on Oct 15; and I can > verify that the Jikes CVS tree was stable and successfully compiled > classpath on Oct 18. > > Otherwise, all I can say is stick to 1.14; although I haven't tried that > version on classpath myself, it does not have the blatant problem with > nested classes. The sad part is that I was release manager for 1.15 > back in September, but was not compiling Classpath at the time, or that > regression might not have slipped through! > > :pserver:[EMAIL PROTECTED]:/usr/cvs/jikes (password anoncvs, > module jikes) > > I feel your pain (sorry that I'm partly to blame). > > > > > Brian > -- This signature intentionally left boring. Eric Blake [EMAIL PROTECTED] BYU student, free software programmer ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
