Hi,
the fix/workaround/hack bellow
to configure.ac and similar to configure
is sufficient to build code-saturne on kfreebsd-amd64.
Petr
--- configure.ac
+++ configure.ac
@@ -447,7 +447,7 @@
path = app.applicationDirPath()
sys.stdout.write(path)]
-PYPATH=`${PYTHON} -c ${prog}`
+
On Tue, Feb 23, 2010 at 4:35 PM, Petr Salinger petr.salin...@seznam.cz wrote:
Hi,
the fix/workaround/hack bellow
to configure.ac and similar to configure
is sufficient to build code-saturne on kfreebsd-amd64.
Petr
Hi Petr,
Thanks for the fix/workaround/hack !
I'll integrate it upstream,
I'll look into this issue later to understand why this test doesn't
work on kfreebsd-* systems
The $PYPATH contains . - dot as current working directory.
According to
http://doc.trolltech.com/4.6/qcoreapplication.html#applicationDirPath
it assumes that argv[0] contains the absolute file name
This assumptions does not hold. On kfreebsd-* the argv[0] usually really
contains the file name of the executable, but only sometimes absolute file
name. The argv[0] is just what have been passed by parent
in execve().
Petr
Hmmm, I see. Thanks a lot for the clarification!
So, it should work
Source: code-saturne
Version: 2.0.0.rc1-2
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS, maybe only on kfreebsd-* (for now, it's Installed on
your arch, i386; and Built on amd64; others have it BD-Uninstallable or
Needs-Build) as follows:
|
Le lundi 22 février 2010 à 21:08 +0100, Cyril Brulebois a écrit :
Source: code-saturne
Version: 2.0.0.rc1-2
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS, maybe only on kfreebsd-* (for now, it's Installed on
your arch, i386; and Built
6 matches
Mail list logo
