On Tue, May 17, 2005, Henri Gomez wrote:
> Yes but some definitions here duplicate with the one from gcc stdio.h.
>
> /usr/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../build
> -I../rpmdb -I../rpmio -I../popt -DOPENPKG -DOPENPKG_AIX
> -I/QOpenSys/tmp/openpkg-2.3.1/zlib-1.2.2
> -I/QOpenSys/tmp/openpkg-2.3.1/bzip2-1.0.2
> -I/QOpenSys/tmp/openpkg-2.3.1/beecrypt-4.1.2 -DOPENPKG -DOPENPKG_AIX
> -I/QOpenSys/tmp/openpkg-2.3.1/zlib-1.2.2
> -I/QOpenSys/tmp/openpkg-2.3.1/bzip2-1.0.2
> -I/QOpenSys/tmp/openpkg-2.3.1/beecrypt-4.1.2 -O2 -D_GNU_SOURCE
> -D_REENTRANT -MT getdate.lo -MD -MP -MF .deps/getdate.Tpo -c getdate.c
> -o getdate.o
> In file included from ./getdate.y:33:
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:484:
> error: conflicting types for `fgetpos64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:310:
> error: previous declaration of `fgetpos64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:487:
> error: conflicting types for `fseeko64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:430:
> error: previous declaration of `fseeko64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:488:
> error: conflicting types for `fsetpos64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:312:
> error: previous declaration of `fsetpos64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:489:
> error: conflicting types for `ftello64'
> /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/stdio.h:431:
> error: previous declaration of `ftello64'
> make[3]: *** [getdate.lo] Error 1
> make[3]: Leaving directory `/QOpenSys/tmp/openpkg-2.3.1/rpm-4.2.1/lib'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/QOpenSys/tmp/openpkg-2.3.1/rpm-4.2.1/lib'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/QOpenSys/tmp/openpkg-2.3.1/rpm-4.2.1'
> make: *** [all] Error 2
>
> .....
>
> May be the patch should check also if we're using gcc ?
Usually if GCC has its own (fixed) stdio.h, the system one is no longer
included at all. At least that's the way it should be. Can it be that
your GCC doesn't 100% fit for your particular OS version? It looks like
the GCC headers needs to be re-fixed.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
