$PTOLEMY/mk/config-$PTARCH.mkfor the particular architecture you are running under.
vemthat can make the process grow quite big. After editing a few dozen icons, you may wish to exit
pigiRpcmay fail to start up on 4 bit (16 color) screens. At UC Berkeley, we use 8 bit and 24 bit screens. Black and white (1 bit) support in vem is a little weak. If you are on a black and white screen, you may need to modify
$PTOLEMY/lib/pigiXRes9. (Note that
$PTOLEMY/lib/pigiXRes9.bwis read when the
pigioption is used to create black and white screen dumps from a color monitor.
pigiXRes9.bwhas very little to do with running on a black and white screen).
VEMBINARYenvironment variable is set, then
bin/pigiEnv.cshwill use the contents of that variable as the
vembinary. However, the binary must be named
vem, or there will be minor problems with X resources, such as small fonts and incorrect snap. Most users will never use the
VEMBINARYenvironment variable. It is primarily used to debug
vemmay crash. One workaround is to not run color
Netscape, or to limit the number of colors
vemnow mean that
vemis more picky about text label heights. Currently, the range for text label heights is 0 to 80. If you select text and then use E, to edit the label, you may see an error if your text height is greater than 80. One workaround is to delete the text and reenter it with a height that is within the proper range. Another workaround is to use an old
vembinary to edit the height and set it to within the range.
And.input=2refer to the same star, but the former can have any number of inputs, while the latter has exactly two inputs. As of this writing, this facility does not work for galaxies. You should create only one icon for each galaxy.
$PTOLEMY/bin/pigiis a link to
$PTOLEMY/bin/pigiEnv.cshwhich may add to your path. Under certain circumstances, you may get the message `Warning: ridiculously long PATH truncated'. To work around this problem, try shortening your path. One trick is to use shorter pathnames in your path, perhaps using symbolic links.
pigimay crash. One workaround is to not run color hogs like
Netscape, or to limit the number of colors
.hfile for the incrementally linked in star cannot be found by compile-SDF. As a workaround try editing the makefile in
~/PTOLEMY_SYSTEMSand adding the directory where the incrementally linked stars are. Then build the binary by hand.
ptcl(see 3.9.10 on page 3-16) via the Ptolemy console. In both workarounds, the Matlab process will be attached to a terminal.
NOWam) CGC target is slow, but it does run under Solaris. However these demos will not work in an environment that requires Kerberos for
cgddf) CGC target, a file must be recompiled. The changes to
parScheduler.ccare a fairly radical shift in how Ptolemy handles disconnected graphs. These changes could break other parallel schedulers. The script
$PTOLEMY/bin/mkcgddfwill build a
pigiRpc.ptrim.debugbinary that contains the
cgddftarget. This script is basically untested, but should work.
ptvhdlsimrunning after exiting.
tychois ongoing, so the version included in Ptolemy 0.7 is by no means the final version. In particular, there are many more features to be implemented.
tycho -ptrim &), then exiting from the Matlab console may hang. The workaround is to place your
tychoprocess into the foreground. This is a known bug with Matlab.
$PTOLEMY/tycho/doc/bugs.htmlfor a more complete list of Tycho bugs.
chaoticBitsdemos bring up messages about initializable delays.
/dev/audio, then you get a cryptic and uninformative error message, rather than something useful. The CGC
tremolodemo will probably only work on a Sun SPARCstation running SunOS4.1.3 or Solaris2.x. The CGC
alivedemo will only work on an SGI.
CGC:multirate:filterbankdemo produces initializable delay warnings. The output from the
CGC:multirate:filterbankdemo is different than the output from the
SDF:multirate:filterbankdemo in that the original and reconstructed signals don't overlap as much in the CGC version.
pxgraphis given exceptional numeric input, such as the IEEE floating point
NaN, then it displays a blank window only.
pxgraphis given an empty file to plot, all it does is send a message "problems with input data" to the standard output.
ftp://ptolemy.eecs.berkeley.edu/pub/gnu/hppaand you may need to patch HPUX. See
animatedLMSdemo dumps core upon start-up.
Xhistogrammay have rounding problems.
animatedLMSdemo requires editing of Target Parameters to compile.
animatedLMSdemo gets an Arithmetic Exception and core dumps.
animatedLMSdemo generates a "
non-numeric value" error in Tcl if the step size is so large that the system is made to go unstable.
hppa.cfrontmay fail. The problem seems to be with the
ldcommand line argument. You must use the
ldargument when compiling
ptcl, or incremental linking of new stars will fail. However, use of the
+Aargument produces the warning:
CC: error: could not find __head symbol. You must use CC to link. If your main is not in C++, a call to _main() is required.(740)
ldargument is not necessary for other binaries, such as
-DPOSTFIX_OPT=to your c++ command line. See
/bin/ld: (Warning) Inter-quadrant branch in XXXwhere
XXXis the name of the
.ofile you are trying to link in,
ldunder HPUX, you should try patching your operating system with a patch from HP. Try
http://europe-support.external.hp.comif you are in Europe,
http://us-support.external.hp.comif you are anywhere else.
ld: fatal: relocations remain against allocatable but non-writable sectionsThen you may need to apply a patch to
multilinkcommand seems to trigger
Inter-quadrant branch messages, and then hang pigi. We are not sure why.
pigiRpcwith the Process Network (PN) domain, but the event loop is broken. The PN domain is not part of the default hppa build, so this problem will not affect most users.
/usr/include/pthread.h, then you probably don't have the DCE development set installed.
gcc-2.7.2under AIX3.2.5 with
cc, you need the PTF U436313. The PTF U432238 is suggested in the README.RS6000 file from the
gcc-2.7.2distribution, but this PTF is superseded by the PTF U436313. This PTF allows you to upgrade the cc IBM compiler from the release 18.104.22.168 (delivered with AIX 3.2.5) to the release 22.214.171.124 which compiles gcc-2.3.6.
pigiRpcbinary can fail with a `GOT Overflow' message. The problem is that
pigiRpchas too many symbols. The Irix
dsoman page suggests using shared libraries, but
gcc-2.7.2may not support C++ shared libraries under Irix. The workaround is to run
xvman pages will fail. Irix does not have
pigi, set the environment variable
setenv SGI_CC -cckrand restart
pigi. See the sgi
ccman page for more information.
sdf:image:motionCompensationdemo has some odd looking blocks in the McompOutput.1 image. Some of the images from the
irix5run of this demo do not look like images in the sun4 version of this demo.
ar, which seems to have problems if it is run on two files whose names are not unique in the first 13 characters. We have renamed a number of stars to workaround this problem. The
make checkjunkcommand will report the names of files that are not unique in the first 13 characters. You should only have problems with this if you are creating stars of your own and placing them in libraries.
ldwith GNU binutils 2.5.2 does not support dynamic loading (See the
TODOfile distributed with the GNU
binutilssource). One solution is to use an older version of GNU
ld. Another solution would be to use
dlopen()style incremental linking, see
/binin your path before
unable to locate archive symbol table: Format error: archive fmagthen you have probably run out of swap space. See the Solaris
swapcommand for how to add more swap with
src/kernel/MatrixParticle.ccfails to compile. The fix for this may require substantial reimplementation of the Ptolemy
Matrixclass, so the changes did not make it into the 0.7 release.
ld.so.1: make: fatal: relocation error: symbol not found: setlinebuf: referenced in make
pt-0.7.gnu.sun4.tar.gz, then you may have problems if your Ptolemy distribution is not at /users/ptolemy, and you try setting the GNU environment variables with the
$PTOLEMY/bin/g++-setup script. We are working towards a solution, but you might find the following variables will work for you:
unsetenv GCC_EXEC_PREFIXWe are working on a solution for this.
setenv LIBRARY_PATH $PTOLEMY/gnu/$PTARCH/lib
setenv COMPILER_PATH $PTOLEMY/gnu/$PTARCH/lib/gcc-lib/$PTARCH/126.96.36.199
setenv GCC_INCLUDE_DIR $PTOLEMY/gnu/$PTARCH/lib/gcc-lib
ldstyle incremental linking because of problems with g++ shared libraries. This means that the SunOS4.x binaries must be linked statically instead of dynamically, so the binaries are much larger than on platforms that use
dlopen()style incremental linking. It also means that only the symbols that are used by stars present at link time are actually present in the binary. This can be a problem if your incrementally linked star uses a symbol from
libg++.athat is not used by a star present at link time. See Appendix D, "Shared Libraries" for more information.
SIGFPEsignals, which crash
pigi. The DDF
ifThenElsedemo uses such SDF/DDF Wormhole.
/sbin/loader: Fatal Error: lazy_text_resolve: symbol malloc should not have any relocation entryThe workaround is to do:
setenv LD_BIND_NOW yesSee the DEC Unix
loaderman page for more information about
LD_BIND_NOW. You may see similar error messages when you run the CGC fixed point demos.
Unaligned Accessmessages. You can run
uac p noprintto turn them off in the current shell.
gcc-2.7.2may not choose the expected cast. In particular,
g++has been known to cast everything to
Fixif the explicit cast is omitted. The arithmetic is then performed using fixed-point computations. This will be dramatically slower than double or integer arithmetic, and may yield unexpected results. It is best to explicitly cast states to the desired form. For more information, see the ptlang chapter in the Ptolemy Programmers Manual.
gmake, then the installation of the Ptolemy GNU tools may fail. The workaround is to create a link in your path from