Re: Re: Some bugs?

["Jason Moxham" <jason@njkfrudils.plus.com>]

I try to narrow it down some time this week,
in the meantime , some more bugs :)

This time pari svn , I make distrib under cygwin to remove the dependance on 
perl and bison , then make gp under mingw32

/mingw/bin/gcc  -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer    -I. 
-I../src/headers  -o default.o ../src/language/default.c
/mingw/bin/gcc  -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer    -I. 
-I../src/headers  -o errmsg.o ../src/language/errmsg.c
/mingw/bin/gcc  -c -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer    -I. 
-I../src/headers  -o es.o ../src/language/es.c
../src/language/es.c:3300:17: pwd.h: No such file or directory
../src/language/es.c: In function `pari_get_homedir':
../src/language/es.c:3314: warning: implicit declaration of function 
`getpwuid'
../src/language/es.c:3314: warning: implicit declaration of function 
`geteuid'
../src/language/es.c:3314: warning: assignment makes pointer from integer 
without a cast
../src/language/es.c:3317: error: dereferencing pointer to incomplete type
../src/language/es.c:3324: warning: implicit declaration of function 
`getpwnam'
../src/language/es.c:3324: warning: assignment makes pointer from integer 
without a cast
../src/language/es.c:3325: error: dereferencing pointer to incomplete type
../src/language/es.c: In function `pari_dir_exists':
../src/language/es.c:4170: error: too many arguments to function `mkdir'
../src/language/es.c: In function `init_unique':
../src/language/es.c:4255: warning: implicit declaration of function 
`getuid'
make[1]: *** [es.o] Error 1
make[1]: Leaving directory 
`/c/Users/jasonadmin/pari-2.4.3/O6.0-none-mingw32_nt'
make: *** [gp] Error 2


----- Original Message ----- 
From: "Bill Allombert" <Bill.Allombert@math.u-bordeaux1.fr>
To: <pari-dev@list.cr.yp.to>
Sent: Tuesday, July 07, 2009 9:48 PM
Subject: Re: Re: Some bugs?


> On Tue, Jul 07, 2009 at 01:30:26AM +0100, Jason Moxham wrote:
> > It's just the file language/eval.c , compiling just that with no
> > optimizations fixes the ffison and nffactor test program errors.
>
> Could you try to narrow it down a bit ? It is possible that the problem
> is actually language/eval.c not being standard-compliant and thus having
> different behaviours with different compilers.
>
> Cheers,
> Bill.