On Mon, Apr 25, 2005, Doug Summers wrote:
> I got the farthest I've even gotten on a compile of OpenPKG on an AIX
> platform. Here's the end of the error messages, related to compiling RPM:
>
> /usr/local/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../popt
> -DOPENPKG -DOPENPKG_AIX -I/tmp/openpkg-2.3.1/zlib-1.2.2
> -I/tmp/openpkg-2.3.1/bzip2-1.0.2 -I/tmp/openpkg-2.3.1/beecrypt-4.1.2
> -DOPENPKG -DOPENPKG_AIX -I/tmp/openpkg-2.3.1/zlib-1.2.2
> -I/tmp/openpkg-2.3.1/bzip2-1.0.2 -I/tmp/openpkg-2.3.1/beecrypt-4.1.2 -O2
> -D_GNU_SOURCE -D_REENTRANT -MT fts.lo -MD -MP -MF .deps/fts.Tpo -c fts.c
> -o fts.o
> In file included from ../system.h:401,
> from fts.c:86:
> ../misc/glob.h:53: warning: redefinition of `size_t'
> /usr/local/bin/../lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/sys/types.h:159:
> warning: `size_t' previously declared here
> fts.c: In function `Fts_open':
> fts.c:174: error: invalid type argument of `unary *'
> fts.c:215: error: invalid type argument of `unary *'
> fts.c:224: error: invalid type argument of `unary *'
Yes, I'm working these days on porting OpenPKG to AIX myself, too. The
problem is just that RPM fiddles around with system structures in a
fully non-portable way when it comes to directory handling. For each
type of Unix one has to adjust the RPM source code in fts.c. My attempts
until now have not worked, but I'll try to find time again tomorrow and
hopefully get past this point soon. At least the same issue occurred
on lots of other platforms, too. I hate that RPM is such nasty in this
corner of its source code.
> I have many machines I can run tests on (AIX 4.3 through 5.3) but I'll
> need to install the test code myself (sorry, Ralph - I couldn't get you
> remote access).
No problem, I now received access from someone else.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
