Pascal wrote:

>Looks promising! I downloaded it and tried to compile it on a Debian PPC
>linux of mine.
>I ran into the following troubles :

Thank you so much Pascal for your help. I will make the
suggested changes to the configure.in file.

>missing packages: I had to install the following packages (Did I say I love
>the Debian packaging system ?)
>
>mesag3
>glutg3-dev
>libtiff-dev
>libjpeg-dev

One of my former colleague (Nicolas Sabouret) is a Debian
developper... I know that package updating is very easy
with Debian.

>Build Problems:
>
>1)  I ran into an automake/autoconf problem that seems to be related to the
>autotools version :
>    During the automake phase, it aborts with "AC_Dest macro undefined", at
>the AC_OUTPUT macro in configure.in.
>
>Workaround :
> in configure.in, changed AC_OUTPUT( <file1> <file2> ...)
> with
>  AC_CONFIG_FILES(<file1>)
>  AC_CONFIG_FILES(<file2>) ...
>  AC_OUTPUT
>
>2) fr-sound.cpp -> gcc aborts due to isdigit() : missing #include <ctype.h>
>
>3) link phase: -L/usr/X11R6/lib was missing in the "libtool mode=link"
>command
>
>4) After installation, and downloading Spheres.conf & Spheres.xml, when I
>launch VirChor
>I get :
> Loading Spheres.conf

> Aborted

Strange. It looks like if you had an incorrect character at the
end of the Spheres.conf file. I assume that it could
come from the Mac character encoding in which the end-of-file
character has a different value different from PC linux systems
(DOS encoding also works fine). Could you send me by email
the Spheres.conf and Spheres.xml files so that I can test
them on my PC (mailto:Chr### [at] limsifr).
Did you edit and saved these files before using them?

About PPC, a friend of mine has been able to compile VirChor
directly in MacOSX and make it run on the sample files.
I can suggest him to write a short notice on how he
managed to compile the application if you wish.

You can also use an empty file for Spheres.conf. You will not
get the expected result because you will get all the default
presets of the parameters. But it works. I have just checked it.

If such a message happens with the xml file,
I would suggest to change the value of the attribute
trace_input_file of the <trace> tag to "true" in the
configuration file (Spheres.conf):

<trace trace_input_file="true" ....etc.

You will get a trace of the input file on the standard output
and check where the parsing problem occurs.

I hope it helps.

Sorry for my late reply. And thanks again.

-Christian

Post a reply to this message