- From: <Irene.Vatton@inrialpes.fr>
- Date: Wed, 11 Aug 1999 17:25:49 +0200
- To: Bartek Rajwa <rajwa@flowcyt.cyto.purdue.edu>
- cc: www-amaya@w3.org
In-reply-to: Your message of Mon, 19 Jul 1999 16:28:52 -0500." <199907192128.QAA11336@flowcyt.cyto.purdue.edu> > Dear Subscribers, > > I am trying to run Amaya on SGI Indigo2 (with Irix 6.2, latest recommended > patches). I downloaded lates binaries, but when tried to run them the > following error occured: > > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_tcgetattr > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_tcsetattr > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_cfgetispeed > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_cfsetispeed > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_cfsetospeed > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __new_cfgetospeed > 14150:./amaya: rld: Error: unresolvable symbol in ./amaya: __libc_attr > 14150:./amaya: rld: Fatal Error: this executable has unresolvable symbols I seems that there are now too different Irix versions. Perhaps the missing library is located in another place on your SGI. > > BTW: I am not able to compile it as well. On the beginning compilation > goes really fine, but then I have: That problem comes from the configure. The configure generates HAVE_STRING_H and HAVE_STRINGS_H. That doesn't cause any problem except on SGI platforms. I don't know how to solve that problem in an elegant way, but I can suggest you a quick method. After the configure, you can edit the generated file config.h and invalid the #define HAVE_STRINGS_H. - #define HAVE_STRINGS_H 1 + /*#define HAVE_STRINGS_H 1*/ Regards Irene.
Received on Wednesday, 11 August 1999 11:25:55 UTC