pview is working, i haven’t yet tackled the fun of genPyCode. I get the feeling that these errors are related to a deeper problem, but i’m not entirely sure what it is. gut instinct is that something in my system is out of date and confusing things. thoughts?
(1) You may be the first one to try linking Panda with a dynamic libtiff.so instead of a static libtiff.a. I’ve seen problems in the past with transitive references with dynamic libraries; e.g. libpnmimagetypes uses some TIFF symbols and links with libtiff.so, everything’s fine; pview does not use any TIFF symbols and links with libpnmimagetypes.so, and the system complains unless you also link pview with libtiff.so. That’s why putting -ltiff on the link line for pview works as a workaround; a longer-term solution is to modify the Sources.pp rules to do this automatically. I will make this change.
(2) These missing egg symbols are the ones defined in panda/src/egg/lexer.cxx, which is a file generated by flex from lexer.lxx. I bet something went wrong with this file. Is it, for instance, zero-length or otherwise truncated? Try removing it and building again.
1 i also got errors for png and jpeg, it is the same problem. do you need to know what directories i needed to do this for? (they were mostly in pandatool)
2 the file was empty. i deleted it and everything worked after that.
Yes, the list of directories would be helpful, thanks.
That is indeed strange–I’ve never seen that before, except as a temporary network burp when you’re compiling within a remote-mounted (e.g. NFS) directory. It’s not a remote directory, is it? Anything flaky about your PC’s hardware that might cause a hiccup accessing the hard disk?
2 there is nothign flaky about my machine that i know of, but i wouldn’t be surprised. i did have to restart make a few times to ecit the makefiles, would htis affect anything? i did try to build it several times, and it broke each time. which seemed oddly consistant.