Hi all,
On Wednesday 30 August 2006 23:54, Peter Adrian Meyer wrote:
> Which version of gcc are you using?
gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
> A quick check of google for the
> unterminated argument list in macro error makes it look like that could be
> an issues (on my systems, it wor
Hi Noel,
Which version of gcc are you using? A quick check of google for the
unterminated argument list in macro error makes it look like that could be
an issues (on my systems, it works for gcc-3.4.5 and 4.0.2; but that's
using make instead of python distutils). It looks to me like a c
preproc
Hi all,
As suggested by Peter, I tried compiling PyMol from src
(pymol-0_99rc6-src.tgz). Unfortunately it fell over :(
Attached is the output.
The error occurs in layer0/Crystal.c. I've look at the file in vim and there
does not seem to be anything untowards (weird characters etc...) in it.
HI all,
This is a follow on from the e-mail below. Frequently I'm also getting this
error when pymol crashes:
*** glibc detected *** /home/fauxn/software/pymol/pymol.exe: double free or
corruption (!prev): 0x0aaef170 ***
=== Backtrace: =
/lib/libc.so.6[0xc69d88]
/lib/libc.so.6(__li
