If you compile something yourself and it breaks, it's not our problem!
The problem in question here is fixed by one of the patches (in debian
/50_register-use.patch), so compiling from just the .orig.tar.gz is
going to render a broken binary.
** Changed in: praat (Ubuntu)
Status: Confirmed
Thanks, I didn't know that. That still leaves the problem that when you
download the source from the author's website the resulting executable
won't run when you are using gcc-4.0 on a Debian based system.
--
praat won't run when compiled from its source package
https://launchpad.net/bugs/65494
I compiled the source package fine in a Dapper pbuilder. Praat worked
fine. That's with the Dapper standard gcc 4.0.3 . There are 2 patches in
the source package (debian/patches) that maybe you should try applying
before compiling. Really though, source packages are not neccesarily
meant to be buil
It is first necessary to determine the exact cause of the problem. The
author of the package says that compiling with gcc-4.0 on MacOs X works
without problems. It may be a library problem. What I'll do is set the
status of this bug to confirmed, so the maintainer of the package can
pick it up.
*
> if you agree I would like to mark this bug as fixed, unless you have
any additional comments.
Yes. I can now successfully compile and run praat by compiling with gcc
3.3. Thanks for the help.
Should the Ubuntu praat source package change its
makefiles/makefile.defs.linux.* to specify a gcc vers
I have sent an email to the author of praat to ask him to mention on his
website that praat should not be compiled with version 4.0 or higher of
gcc, until he fixes the problem.
Jonathan, if you agree I would like to mark this bug as fixed, unless
you have any additional comments.
--
praat won't
Hi Jonathan,
Thanks for the additional info. I downloaded the latest praat source
code (file praat4432_sources.tar.gz) installed libmotif3, and compiled
praat. I got the same problem as you described, i.e. praat just hangs
using 100% of the CPU.
>From your description it became clear to me that t
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
I thought I included an attachment, but I don't see it. Anyway. here's
my cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 1800+
stepping: 1
cpu MHz : 1499.148
cache size : 256 KB
fdiv_bug
Thank you for your bug report.
Possibly the problem is caused by using compiler options that are not
compaitible with your CPU. Please check your CPU information (cat
/proc/cpuinfo) and check the makefile of Praat to make sure the compiler
flags match the CPU. Please report your findings.
Wim
**
10 matches
Mail list logo
