Thanks for your bug report, I've answered the points below
> Hi All - I've just picked up Ptolemy 0.5, so please excuse me if this is
> redundant. I did not find comments to this effect in the archive.
> I was able to build it using gcc 2.4.5 & 2.5.8 with three small problems:
> 1) src/domains/sf/matrix/stars/SDFDataCx_M.pl
> Changed input%k to Complex(input%k)
I fixed this in the development tree and the release tree, so the
change should be in the 0.5.1 release
Added Complex() to: Changed input%k to Complex(input%k)
SDFDataFix_M.pl has a similar cast.
> 2) src/domains/de/kernel/CalendarQueue.h
> Changed HUGE_VAL to MAXDOUBLE
I'm not sure why the change here is necessary. The code seems to work
as is. Can you provide me with more details? I don't have a full
understanding of HUGE_VAL, but it seems to be present on all the
machines we are compiling under.
> 3) src/octtools/makefile
> Changed the load to use the misalign libraries. There
> were a number of cases where I got misaligned core dumps
> when running on sparc. The load must pickup the
> crt0.o and libc from /lib/misalign.
This is fixed in the upcoming release. Basically, the fix is to not
use the octtools memory management library -lmm. There was also a
problem with the octtools kd library and realloc. Both of these
problems have been fixed in the upcoming 0.5.1 release. In 0.5,
$PTOLEMY/src/octtools/README discusses the situation a little.
Quote:> When trying to build Ptolemy 0.5 using gcc 2.6.0, I received
> numerious type clash errors (char * versus const char *).
We've cleaned up some of these warnings, but pigilib still has them.
Also, since we are using gcc -Wall rather than cc to compile .c files,
we get lots of warnings in pxgraph, thor and octtools.
Quote:> I hope this is of some interest.
You bet! We're always interested in bug reports.