> > > > Also, almost everything works after changing all the .lo's to .o's. > > > > Yup. In the multi-language branch, IIRC, the .lo file is placed in > > the .libs directory, named `.o', and the .lo file is created as a > > wrapper script, just like the .la files. > > Yes indeed. :-) Is there any hack that anyone can think of to switch libtool's usage of .lo's to .o's for the time being. I don't really mind if it's a huge hack :-), as long as I can get this product building with autoconf/automake/libtool... Thanks, Chris Knight <[EMAIL PROTECTED]> Bank of America Assistant Vice President
- Build problems with SunWorkshop 4.2 Christopher Knight
- Re: Build problems with SunWorkshop 4.2 Alexandre Oliva
- Re: Build problems with SunWorkshop 4.2 Ossama Othman
- Re: Build problems with SunWorkshop 4.2 Alexandre Oliva
- Re: Build problems with SunWorkshop 4.2 Alexandre Oliva
- Re: Build problems with SunWorkshop 4.2 Christopher Knight
- Re: Build problems with SunWorkshop 4.2 Stephan Kulow
- Re: Build problems with SunWorkshop 4.2 Christopher Knight
- Re: Build problems with SunWorkshop 4.2 Ossama Othman
- Re: Build problems with SunWorkshop 4.2 Christopher Knight
- Re: Build problems with SunWorkshop 4.2 Christopher Knight