Re: [Openvrml-develop] OpenVRML 0.10.1 under IRIX 6.5

[Braden M. <br...@en...>]

On Thu, 21 Jun 2001, Florian Echtler wrote:

> I've got a problem with installing OpenVRML under IRIX.
> I've installed gcc-2.95.2 and the latest versions of
> libpng, libjpeg and libz. By doing nothing more than
> "configure" and "make" in the top directory, I manage
> to compile everything down to the src/openvrml/OpenVMRL
> directory. There, make aborts with an error because
> of "Too many symbolic links: antlr-prelinked.o and
> scriptjs-prelinked.o", just when it tries to link the
> libopenvrml.a together. Looking at those files, I was
> surprised to discover that there exists a circular
> reference between antlr-prelinked.o and .lo - dito
> for scriptjs-prelinked.o/.lo.

Either you're misunderstanding something, I'm misunderstanding you, or
something has gone horribly wrong. The *.lo files are linked into the
shared library, whereas the *.o files are linked into the static library.
Aside from the fact that <filename>.lo is generated from the same source
as <filename>.o, the two are unrelated.

Could you post the error message you're seeing?

I think I'm gonna get rid of the prelinking step with ANTLR. (It's already
been rendered moot as far as the JavaScript library is concerned.) All I
think it's buying us is a slightly smaller binary size; and at this stage,
that's just not worth the interoperability problems it's causing.

> When I try to remake
> these files seperately, I get those circular refs again.
> Can anyone tell me how I can create those two
> "prelinked" files?

You can modify the Makefile.am to eliminate the pre-linking step. Move the
dependencies for the *-prelinked.* rules to the openvrml_la_LIBADD
variable, and remove or comment out the pre-linking rules. The variable
should look something like this:

  openvrml_la_LIBADD = Vrml97Parser.lo \
                       $(top_builddir)/lib/antlr/libantlr.la ScriptJS.lo \
                       $(top_builddir)/lib/js/libjs.la

-- 
Braden McDaniel                             e-mail: <br...@en...>
<http://endoframe.com>                      Jabber: <br...@ja...>