In the buildfarm we use -Werror, which results in this error:

cc1: warnings being treated as errors
libstrc.c: In function ‘h_1100’:
libstrc.c:205914: warning: pointer targets in passing argument 1 of ‘ATreadFromBinaryString’ differ in signedness

This is probably the declaration of the parsetable. We should check the signedness in the ATerm library and update the compiler to generate the correct signedness. We might temporarily have to disable -Werror to bootstrap this fix.

Submitted on 2 April 2008 at 02:18

On 10 April 2008 at 15:01 Jira commented:

STR-744, karltk:
This is apparently related to CWI bug #411 (internal bug database). The signature of ATreadFromBinaryString was changed from

ATerm ATreadFromBinaryString(char *s, int size);


ATerm ATreadFromBinaryString(const unsigned char *s, int size);

in revision upstream repository, revision 21921.

If we change the compiler, we can no longer compile with older versions of the ATerm library. This might not be an issue if we’re certain that the newer versions are stable enough for our upcoming stable release.

It’s a quick enough fix, once we decide to do and bump the ATerm dependency.

On 10 April 2008 at 18:32 Jira commented:

STR-744, martin:
note that it is only an issue with -Werror. I think we should just update. Normal users don’t really build with -Werror I suppose?

We might have to disable -Werror to get a new baseline though. (or we need to compile the old strategoxt with a different aterm library.)

On 14 April 2008 at 00:13 Jira commented:

STR-744, martin:
Postponing, since we will be using ATerm 2.5 for Stratego/XT 0.17

On 16 April 2010 at 14:28 Rob Vermaas commented:

as aterm 2.6 is not 64 bit compatible, we stay with aterm 2.5 until an aterm version comes out with proper 64 bit support.

Log in to post comments