Problem building OIS 1.2 in linux

[bear]

I'm trying to build OIS 1.2 in Ubuntu Jaunty but having problem. The error I get is the following:

Code:

$ make
Making all in src
make[1]: Entering directory `/home/bear/code/gass.googlecode/ois/src'
/bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../includes  -I../includes -g -O2 -I/usr/X11R6/include    -g -O2 -MT OISInputManager.lo -MD -MP -MF .deps/OISInputManager.Tpo -c -o OISInputManager.lo OISInputManager.cpp
../libtool: line 777: X--tag=CXX: command not found
../libtool: line 810: libtool: ignoring unknown tag : command not found
../libtool: line 777: X--mode=compile: command not found
../libtool: line 927: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 928: *** Future versions of Libtool will require -mode=MODE be specified.: command not found
../libtool: line 1071: Xg++: command not found
../libtool: line 1071: X-DHAVE_CONFIG_H: command not found
../libtool: line 1071: X-I.: command not found
../libtool: line 1071: X-I../includes: No such file or directory
../libtool: line 1071: X-I../includes: No such file or directory
../libtool: line 1071: X-g: command not found
../libtool: line 1071: X-O2: command not found
../libtool: line 1071: X-I/usr/X11R6/include: No such file or directory
../libtool: line 1071: X-g: command not found
../libtool: line 1071: X-O2: command not found
../libtool: line 1071: X-MT: command not found
../libtool: line 1071: XOISInputManager.lo: command not found
../libtool: line 1071: X-MD: command not found
../libtool: line 1071: X-MP: command not found
../libtool: line 1071: X-MF: command not found
../libtool: line 1071: X.deps/OISInputManager.Tpo: No such file or directory
../libtool: line 1071: X-c: command not found
../libtool: line 1119: XOISInputManager.lo: command not found
../libtool: line 1124: libtool: compile: cannot determine name of library object from `': command not found
make[1]: *** [OISInputManager.lo] Error 1

There seem to be some problems due to new versions of libtool or something. Just wanted to inform you and maybe someone have a solution to the problem for me.

I have the following installed:
ltmain.sh (GNU libtool) 1.5.8 (1.1220.2.117 2004/08/04 14:12:05)
autoconf (GNU Autoconf) 2.63
automake (GNU automake) 1.10.2

[mysterycoder]

I'm fairly sure this is a configuration error on your computer.
I found a page where people have listed some solutions to your problem: http://www.mail-archive.com/libtool@gnu.org/msg10937.html
Hopefully you can find an answer there.

[bear]

Well, it might be something wrong with my configuration but I haven't done anything except downloading OIS 1.2 from sourceforge and installing the autotools needed to compile OIS and and did what it said in ReadMe.txt. The problem still occured and I got the same result on two different computers. So you might think that the problem could be something OIS do/don't do that is needed in latest versions of autotools. Oh well, will investigate the problem closer with guidance from that forum thread you gave me.

[bear]

I'm sorry but I really lack knowledge about autotools. I've looked at the thread you directed me to but what exactly did you mean I should try from the thread to build OIS?

[mysterycoder]

I read on the ubuntu site that if you downgrade to Hardy's version of libtool (1.5.26), then it should work. http://programphases.com/forums/showthread.php?p=29

I've also read that you could also try to edit the bootstrap file and remove "--force" from the line "libtoolize --force --copy"
Then re-run bootstrap, configure and make

I'm still trying to figure out exactly what the problem is, will keep looking.

edit: did you already do a downgrade from Jaunty's version of libtool (2.26) ?

[pjcast]

Do you have dev tools installed on your system? g++/gcc? Doesn't seem like it.

[mysterycoder]

From what I've read, it happens when there is an incompatibility between two libtool versions. For example if a tarball includes ltmain.sh but it still uses the system's libtool aclocals and stuff.
So I was thinking that it might happen if he did a manual downgrade, there are probably left-overs from the newer version of libtool.

[bear]

Yes I have gcc/g++ version 4.3.3.

I tried the downgrade of libtool and that did the trick but as people mention at the ubuntu forum, system constantly inform about new updates which is quite annoying.
When running bootstrap with downgraded I get this output:
"You should add the contents of `/usr/local/share/aclocal/libtool.m4' to `aclocal.m4'"

When I run bootstrap with newest version of libtool I get this output;
"You should update your `aclocal.m4' by running aclocal."

Oh well, let me know if you wan't me to help you out testing something out if you have any idea what might solve the compile with latest version of libtool. Getting it working with latest version of libtool would be nice since it will involve problems when instruction users of our software project to compile OIS as well if they have the "wrong" libtool version install, which they probably will if running jaunty like me.

[bear]

...and I forgot, I tried to remove --force in bootstrap as well but with no success.

[lasilasi]

Code:

$ make
../libtool: X--tag=CXX: command not found
../libtool: libtool: ignoring unknown tag : command not found
../libtool: X--mode=compile: command not found
../libtool: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: *** Future versions of Libtool will require -mode=MODE be specified.: command not found
../libtool: Xg++: command not found
../libtool: X-DHAVE_CONFIG_H: command not found
../libtool: X-I.: command not found
../libtool: X-I../includes: No such file or directory
../libtool: X-g: command not found
../libtool: X-O2: command not found
../libtool: X-I/usr/X11R6/include: No such file or directory
../libtool: X-O2: command not found
../libtool: X-c: command not found

As a bottle to the sea message:

There is an easy fix when you get such messages as "X--tag=CXX: command not found". Just type:

Code:

export echo=echo

And try again.

This is a bug in the script libtool that tries to EXECUTE the parameters (prefixed with X) as if there were programs,
unless the variable $echo is defined.
I don't know who the genius is who coded that, but thanks a lot... I actually had random programs starting with X executing.