I installed gcc-4.3.4 on cygwin , which would always bomb out the
install before , and trying it with that I get this error

/bin/sh ../libtool --tag=CC   --mode=compile gcc-4 -std=gnu99 -
DHAVE_CONFIG_H -I
. -I../../mpn -I.. -D__GMP_WITHIN_GMP -I../.. -DOPERATION_`echo
fib2_ui | sed 's
/_$//'`    -m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2 -c -
o fib2_ui
.lo fib2_ui.c
libtool: compile:  gcc-4 -std=gnu99 -DHAVE_CONFIG_H -I. -I../../mpn -
I.. -D__GMP
_WITHIN_GMP -I../.. -DOPERATION_fib2_ui -m32 -O2 -fomit-frame-pointer -
mtune=cor
e2 -march=core2 -c fib2_ui.c -o fib2_ui.o
In file included from fib2_ui.c:26:
/usr/include/stdio.h:53: error: expected '=', ',', ';', 'asm' or
'__attribute__'
 before 'fpos_t'
In file included from fib2_ui.c:26:
/usr/include/stdio.h:210: error: expected declaration specifiers or
'...' before
 'fpos_t'
/usr/include/stdio.h:216: error: expected ';', ',' or ')' before '*'
token
/usr/include/stdio.h:379: error: expected declaration specifiers or
'...' before
 'fpos_t'
/usr/include/stdio.h:380: error: expected ';', ',' or ')' before '*'
token
/usr/include/stdio.h:535: error: expected declaration specifiers or
'...' before
 'fpos_t'
/usr/include/stdio.h:540: error: expected declaration specifiers or
'...' before
 'fpos_t'
make[2]: *** [fib2_ui.lo] Error 1
make[2]: Leaving directory `/home/root/mpir/trunk/cygwin/mpn'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/mpir/trunk/cygwin'
make: *** [all] Error 2

There is a gcc-4.5.0 to try , perhaps that may make things clearer or
not , can someone else confirm this , as it's possible my machine is
doo-lally

PS This is the only issue holding up RC1

Thanks
Jason


On Nov 8, 2:43 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
> It actually looks like a gcc problem doesn't it. I've never seen a
> "parse error" before. Though I would normally expect it to say
> "internal error" or something.
>
> I wonder if the cygwin trac system has a bug listed for this.
>
> Bill.
>
> On 8 November 2010 12:52, jason <ja...@njkfrudils.plus.com> wrote:
>
>
>
> > I tried it with some other stuff  , and I get the same error , so it does
> > look like it is a cygwin problem , or my machine.
>
> > Jason
>
> > ----- Original Message ----- From: "jason" <ja...@njkfrudils.plus.com>
> > To: "mpir-devel" <mpir-devel@googlegroups.com>
> > Sent: Monday, November 08, 2010 12:37 PM
> > Subject: [mpir-devel] cygwin fails on mpir new and the old versions
>
> >> Hi
>
> >> I noticed this a few weeks ago and I assumed I had somehow corrupted
> >> my cygwin installation , so I have now wiped it , and reinstalled from
> >> scratch and mpir , and I still get the same errors
>
> >> /bin/sh ../libtool --tag=CC   --mode=compile gcc -std=gnu99 -
> >> DHAVE_CONFIG_H -I.
> >> -I../../mpn -I.. -D__GMP_WITHIN_GMP -I../.. -DOPERATION_`echo fib2_ui
> >> | sed 's/_
> >> $//'`    -m32 -O2 -fomit-frame-pointer -mtune=nocona -march=nocona -c -
> >> o fib2_ui
> >> .lo fib2_ui.c
> >> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../mpn -I.. -
> >> D__GMP_WITHIN_GMP -I../..
> >> -DOPERATION_fib2_ui -m32 -O2 -fomit-frame-pointer -mtune=nocona -
> >> march=nocona -c
> >> fib2_ui.c -o fib2_ui.o
> >> In file included from fib2_ui.c:26:
> >> /usr/include/stdio.h:53: error: parse error before "fpos_t"
> >> In file included from fib2_ui.c:26:
> >> /usr/include/stdio.h:210: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:216: error: parse error before '*' token
> >> /usr/include/stdio.h:379: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:380: error: parse error before '*' token
> >> /usr/include/stdio.h:535: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:535: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:535: error: `funopen' declared as function
> >> returning a func
> >> tion
> >> /usr/include/stdio.h:540: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:540: error: parse error before "fpos_t"
> >> /usr/include/stdio.h:540: error: `_funopen_r' declared as function
> >> returning a f
> >> unction
> >> make[2]: *** [fib2_ui.lo] Error 1
> >> make[2]: Leaving directory `/home/root/mpir/mpir-2.1/cygwin/mpn'
> >> make[1]: *** [all-recursive] Error 1
> >> make[1]: Leaving directory `/home/root/mpir/mpir-2.1/cygwin'
> >> make: *** [all] Error 2
>
> >> Now stdio.h is the "first line" in the file fib2_ui.c so it appears
> >> it's nothing to do with us , this also happens with mpir-1.3 and
> >> mpir-2.1 . A lot of these stdio.h are used to get NULL , we can use
> >> 0 , or are only needed for debugging , so we dont need them , but
> >> there are a few places where we do need them ie mpn_inp.c  for the
> >> FILE type for input/output.
> >> The simple Hello World program compiles and runs OK , so it's possible
> >> that we are doing something wrong and cygwin is the first to bite
> >> back.
>
> >> Can someone confirm this , in case it's some aspect of my system.
> >> I'll try some other lib's that have the stdio.h in , to see if they
> >> have this problem.
>
> >> Thanks
> >> Jason
>
> >> I'll try
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "mpir-devel" group.
> >> To post to this group, send email to mpir-de...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> mpir-devel+unsubscr...@googlegroups.com.
> >> For more options, visit this group at
> >>http://groups.google.com/group/mpir-devel?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mpir-devel" group.
> > To post to this group, send email to mpir-de...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > mpir-devel+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/mpir-devel?hl=en.- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to