I doubt it's my CPU, but I've attached the /proc/cpuinfo from two computers where I've tried this and had the problem.
Are other people able to compile praat on a new Ubuntu Dapper installation and run it? Is this a general problem, or is it just me? I suspect it's a general problem. I have a binary of praat (version 4.3.24) that I had previously compiled under another Debian based distro (Mepis 3.4.3) prior to me installing Ubuntu Dapper. This old binary still runs OK on my Dapper installations, but when I now compile the same source (praat 4.3.24) under Dapper then the new binary doesn't run. This suggests that the praat makefile is OK, but something about compiling it on my Dapper installation is causing the problem. Possibly the makefile is not compatible with the compiler on Dapper, although that would give a problem for everyone, not just me. (Note: The old binary was compiled with libmotif3 and libmotif-dev, so I replaced lestif2 and lestif2-dev with these for this test). Note that the praat binary from the Dapper repository runs OK (with lestif2 installed). So, I can run praat binaries which were compiled elsewhere, one with libmotif3 and one with lestif2, but I can't run a binary which I compile on a newly installed clean Dapper installation (neither with libmotif3 nor lestif2). -- praat won't run when compiled from its source package https://launchpad.net/bugs/65494 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
