From: garaf g. <gar...@ya...> - 2006-03-20 21:16:37
|
Hi, I am trying to install the latest CVS snapshot of OpenC++ on Mac 10.4.2 (Tiger). I am facing the following problem: in Mac 10.4.2, libtool is different than the gnu libtool -which is called glibtool- All installation files in OpenC++ assumes that libtool is glibtool, which causes installation problems and errors. I changed every occurence of "libtool" in the file bootstrap with "glibtool" and it worked, but later on, when I tried to run occ2 it caused segmentation fault because it is again calling libtool thinking it is glibtool. I tried to change every occurence of every "libtool" in all OpenC++ files with "glibtool" but again this didn't work. Anyone can help? Please let me know if OpenC++ can be installed on Mac 10.4.2, I have spent over a month trying to install it on my Mac with no success. Thank you garaf __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Stefan S. <se...@sy...> - 2006-03-21 01:59:38
|
garaf garaf wrote: > Hi, > > I am trying to install the latest CVS snapshot of > OpenC++ on Mac 10.4.2 (Tiger). I am facing the > following problem: in Mac 10.4.2, libtool is different > than the gnu libtool -which is called glibtool- > > All installation files in OpenC++ assumes that libtool > is glibtool, which causes installation problems and > errors. AFAICT, 'libtool' is a generated script in the build tree, so it shouldn't matter whether your /usr/bin/libtool (or wherever it lives) is compatible with the GNU version. > I changed every occurence of "libtool" in the file > bootstrap with "glibtool" and it worked, but later on, > when I tried to run occ2 it caused segmentation fault > because it is again calling libtool thinking it is > glibtool. > > I tried to change every occurence of every "libtool" > in all OpenC++ files with "glibtool" but again this > didn't work. I'm not sure. libtool seems to be used both during occ's own compilation, as well as during compilation *with* occ. In the latter case, occ2 appears to accept a --libtool option with which to specify which libtool script to use. HTH, Stefan |
From: Scott D. F. <sd...@cs...> - 2006-03-21 04:10:44
|
Hi Garaf, As part of the OpenC++ build process, a libtool script is generated in the build directory. You can simply copy this file into the bin directory that occ and occ2 were installed in (make sure it's in your PATH), and everything should work (hopefully). I previously used this technique to get occ working on a Solaris machine that lacked libtool. Good luck, Scott On 3/20/06, garaf garaf <garaf_garaf@...> wrote: > Hi, > > I am trying to install the latest CVS snapshot of > OpenC++ on Mac 10.4.2 (Tiger). I am facing the > following problem: in Mac 10.4.2, libtool is different > than the gnu libtool -which is called glibtool- > > All installation files in OpenC++ assumes that libtool > is glibtool, which causes installation problems and > errors. > > I changed every occurence of "libtool" in the file > bootstrap with "glibtool" and it worked, but later on, > when I tried to run occ2 it caused segmentation fault > because it is again calling libtool thinking it is > glibtool. > > I tried to change every occurence of every "libtool" > in all OpenC++ files with "glibtool" but again this > didn't work. > > Anyone can help? > > Please let me know if OpenC++ can be installed on Mac > 10.4.2, I have spent over a month trying to install it > on my Mac with no success. > > Thank you > garaf > |
From: <se...@in...> - 2006-03-24 19:53:11
|
On Mon, 2006-03-20 at 13:16 -0800, garaf garaf wrote: > Hi, > > I am trying to install the latest CVS snapshot of > OpenC++ on Mac 10.4.2 (Tiger). I am facing the > following problem: in Mac 10.4.2, libtool is different > than the gnu libtool -which is called glibtool- > > All installation files in OpenC++ assumes that libtool > is glibtool, which causes installation problems and > errors. The libtool utility is there to resolve incompatibility across architecture, something wrong there. if glibtool package is equivalent, solutions are 1) symlink the the thing 2) provide a mechanism to identify your architecture, for example $ uname will give "Linux", does that thing work so that we can put more intelligence in the script. > I changed every occurence of "libtool" in the file > bootstrap with "glibtool" and it worked, but later on, > when I tried to run occ2 it caused segmentation fault > because it is again calling libtool thinking it is > glibtool. > > I tried to change every occurence of every "libtool" > in all OpenC++ files with "glibtool" but again this > didn't work. > > Anyone can help? > > Please let me know if OpenC++ can be installed on Mac > 10.4.2, I have spent over a month trying to install it > on my Mac with no success. > > Thank you > garaf |