2012/4/24 Paulo César Pereira de Andrade
Polybori needs to be built. In Fedora 16, essentially, this is
required to build
with current cudd-devel
2012-04-24 23:17:47.328677842 -0300
2012-04-24 23:17:53.406678079 -0300
@@ -54,8 +54,6 @@ inline const char* error_text(PBORI_PREF
- case CUDD_TIMEOUT_EXPIRED:
- return("Timed out.");
return("No error. (Should not reach here!)");
I don't understand. What problem does this solve?
Also, note that up through Fedora 16, we had a package named
python-polybori, with various subpackages. A few months ago, I
reorganized the packages to produce a package named polybori and
various subpackages (including a python-polybori subpackage). This is
available in Fedora 17 (to be released in about a month) and Fedora
Rawhide. I will probably not backport that reorganization to Fedora
16, as it would involve making some changes that violate the Package
Update Policy; see https://fedoraproject.org/wiki/Updates_Policy
Bottom line: Fedora 16 has polybori 0.7.2 and cudd 2.4.2, and will
probably stay that way. Fedora 17 and above currently have polybori
0.8.1 and cudd 2.5.0. Any changes we need to make should be done
It is also required a patch similar to this one to be able to build
sagemath with it:
Okay, I can add that easily. I'm going to wait until I understand why
you wanted the other change above, though.
Also, I haven't yet built polybori with NTL support. Is that going to
be necessary for Sage?
I am still too noob with fedora, so, I could not finish the build,
because, while I know
how to git clone a fedora package, do not know how to fetch sources.
Use "fedpkg sources", or you can even run "fedpkg srpm" to build the
$ fedpkg clone polybori
Cloning into 'polybori'...
The authenticity of host 'pkgs.fedoraproject.org (22.214.171.124)'
can't be established.
RSA key fingerprint is fe:2e:6a:86:f3:41:e7:03:95:ea:9c:7f:75:9c:ce:9d.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'pkgs.fedoraproject.org,126.96.36.199'
(RSA) to the list of known hosts.
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Could not execute clone: Command '['git', 'clone',
'ssh://email@example.com/polybori']' returned non-zero exit
I believe this is because you are not yet a packager. Once you are
sponsored, this problem should go away. If I'm wrong about that,
hopefully someone else reading this will correct me.
The patch to use unpatched ntl should have a nasty side effect in
because it will miss the error message, if in the terminal, it will
print the error message
to stderr anyway before calling abort. But really, it should have been sagemath
to convince upstream NTL for the need of a more complete api.
What patch would NTL need to solve this problem?