Hi! * Patrick Matthäi <[email protected]> [2010-01-01 11:14:59 CET]: > it is a ppc only issue.
I really don't think so. > Could you please build apt-dater with the patch from upstream svn > revision 438 and test it again? If that patch should fix it (will try so in the next few days) then it definitely doesn't only affect powerpc, there are other architectures too that have char unsigned. > Here is the repository: > https://apt-dater.svn.sourceforge.net/svnroot/apt-dater > > Or just the direct patch: > m...@gnu:~/Coding/apt-dater$ svn diff apt-dater/trunk/src/apt-dater.c > -r437:438 > Index: apt-dater/trunk/src/apt-dater.c > =================================================================== > --- apt-dater/trunk/src/apt-dater.c (Revision 437) > +++ apt-dater/trunk/src/apt-dater.c (Revision 438) > @@ -61,7 +61,7 @@ > > int main(int argc, char **argv, char **envp) > { > - char opts; > + int opts; > char *cfgfilename = NULL; > char *cfgdirname = NULL; > GList *hosts = NULL; Like said, will try so in the next few days, but expecting char to be signed is a portability issue not only for powerpc. I hope that this is the only place, I think the build logs might have warnings about that to check for other places, too. So long, and like said, will try so in the next few days. :) Rhonda -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
