-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Edmund,
On 09/12/14 10:12, Edmund Grimley Evans wrote:
> The changes described above are now in the git repo:
>
> http://github.com/b-k/apophenia
Thanks for the update.
I will look at it soon, I look for upgrading the Debian material.
>
> D
The changes described above are now in the git repo:
http://github.com/b-k/apophenia
Do you want to add them as a patch to the Debian version?
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 11/11/14 18:40, Edmund Grimley Evans wrote:
> Some good news: the code doesn't seem to need a lot of changes to make
> it work on arm64. I did this:
>
> * Changed the type of the local variables to which the value returned
> from fgetc, getop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 11/11/14 18:40, Edmund Grimley Evans wrote:
> Some good news: the code doesn't seem to need a lot of changes to make
> it work on arm64. I did this:
>
> * Changed the type of the local variables to which the value returned
> from fgetc, geto
Some good news: the code doesn't seem to need a lot of changes to make
it work on arm64. I did this:
* Changed the type of the local variables to which the value returned
from fgetc, getopt or get_next is assigned from char to int.
* Made get_next return int instead of char, and, to make it ret
There are also several places where the value returned from getopt is
assigned to a variable of type char before being compared with -1. I
would guess that the programs are going into an infinite loop while
trying to parse their command-line arguments when char is unsigned.
--
debian-science-main
>> By the way, it might be a good idea to remove the ">/dev/null 2>&1"
>> from the command lines in case the compiler wants to warn you about
>> this sort of thing. (I don't know whether GCC does in this particular
>> case.)
>>
>
> Please could you specify the place of this code.
I was wrong. The
On 10/11/14 23:48, Edmund Grimley Evans wrote:
> By the way, it might be a good idea to remove the ">/dev/null 2>&1"
> from the command lines in case the compiler wants to warn you about
> this sort of thing. (I don't know whether GCC does in this particular
> case.)
>
Please could you specify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Edmund for your comment:
I will forward them to the upstream author.
On 10/11/14 23:48, Edmund Grimley Evans wrote:
> By the way, it might be a good idea to remove the ">/dev/null 2>&1"
> from the command lines in case the compiler wants to war
By the way, it might be a good idea to remove the ">/dev/null 2>&1"
from the command lines in case the compiler wants to warn you about
this sort of thing. (I don't know whether GCC does in this particular
case.)
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.d
>From the buildd logs it appears that the tests are timing out.
A quick look at apop_conversions.c suggests a plausible explanation.
In that file there is code like this:
char c = fgetc(infile);
...
while(c!='\n' && c !=EOF){
EOF is negative, and plain char is unsigned on ARM architectu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately I am blind here:
1] I have no access to the tests/test-suite.log ;
2] I cannot reproduce the issue on a virtual i386 box on my amd64 computer (via
pbuild);
3] I have not access to those architectures.
I have contacted the upstream maint
Source: apophenia
Version: 0.999b+ds3-1
Severity: important
Builds of apophenia on most architectures failed because the test
suite either tripped sbuild's inactivity timeout or encountered
unexpected failures, most commonly of distribution_tests. Could you
please take a look? You can find the l
13 matches
Mail list logo
