Re: 7.3.2 make failed on AIX4.3 using native c compiler

I config and make the 7.3.2 on
the one works, then try to install
on the other one which was failed, after
the install, try to start postmaster -
tail -f postmaster.log
exec(): 0509-036 Cannot load program /emrxdbs/pgsql/bin/postmaster because
of the following errors:
Dependent module /usr/local/lib/libz.a(shr.o) could not be loaded.
Member shr.o is not found in archive

But the failed one, libz.a is older
working one -
ls -all /usr/local/lib/libz.a
-rw-r--r-- 1 root system 77308 Mar 20 2000 /usr/local/lib/libz.a

failed one -
ls -all /usr/local/lib/libz.a
-rwxr-xr-x 1 root system 83699 Feb 19 2001 /usr/local/lib/libz.a

johnl

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of John Liu
> Sent: Monday, March 31, 2003 11:24 AM
> To: Bruce Momjian
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] 7.3.2 make failed on AIX4.3 using native c
> compiler
>
>
> Hi, Bruce,
> I've tried on two AIX4.3.3 boxes,
> both are the same oslevel=4330-09,
> both are the same compiler version,
>
> lslpp -l|grep -i xlc
> xlC.aix43.rte 4.0.2.1 COMMITTED C Set ++ Runtime for AIX
> 4.3
> xlC.cpp 4.3.0.1 COMMITTED C for AIX Preprocessor
> xlC.msg.en_US.cpp 4.3.0.1 COMMITTED C for AIX Preprocessor
> xlC.msg.en_US.rte 4.0.2.0 COMMITTED C Set ++ Runtime
> xlC.rte 4.0.2.0 COMMITTED C Set ++ Runtime
>
> one make works, the other one failed. I'm trying
> to figure out what makes the differences.
>
> johnl
> > -----Original Message-----
> > From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> > Sent: Monday, March 31, 2003 11:15 AM
> > To: John Liu
> > Cc: pgsql-hackers(at)postgresql(dot)org
> > Subject: Re: [HACKERS] 7.3.2 make failed on AIX4.3 using native c
> > compiler
> >
> >
> >
> > I know we have other AIX users using PostgreSQL. What compiler version
> > is that?
> >
> > ------------------------------------------------------------------
> > ---------
> >
> > John Liu wrote:
> > > make[4]: Leaving directory
> > `/emrxdbs/postgresql-7.3.2/src/backend/parser'
> > > cc -O2 -qmaxmem=16384 -qsrcmsg -qlonglong
> > -I../../../src/interfaces/libpq -I
> > > ../../../src/include -I/usr/local/include
> > -DBINDIR=\"/emrxdbs/pgsql/bin\" -
> > > c -o pg_dump.o pg_dump.c
> > > 2681 | "COMMENT", deps,
> > > ....................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 2777 |
> "COMMENT",
> > > deps,
> > >
> > > ............................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 2795 |
> "COMMENT",
> > > deps,
> > >
> > > ............................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 3121 | tinfo->usename,
> > "TYPE", deps,
> > >
> > .........................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 3226 | tinfo->usename,
> > "DOMAIN", deps,
> > >
> > ...........................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 3515 |
> > "PROCEDURAL LANGUAGE",
> > > deps,
> > >
> > > ................................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > 3882 | "CAST", deps,
> > > .................................................a....
> > > a - 1506-280 (W) Function argument assignment between types
> > "const unsigned
> > > char*(*)[]" and "unsigned char*(*)[]" is not allowed.
> > > cc -O2 -qmaxmem=16384 -qsrcmsg -qlonglong
> > -I../../../src/interfaces/libpq -I
> > > ../../../src/include -I/usr/local/include
> > -DBINDIR=\"/emrxdbs/pgsql/bin\" -
> > > c -o common.o common.c
> > > cc -O2 -qmaxmem=16384 -qsrcmsg -qlonglong
> > -I../../../src/interfaces/libpq -I
> > > ../../../src/include -I/usr/local/include
> > -DBINDIR=\"/emrxdbs/pgsql/bin\" -
> > > c -o pg_backup_archiver.o pg_backup_archiver.c
> > > 590 | ArchiveEntry(Archive *AHX, char *oid, char *tag,
> > > a.................................................
> > > a - 1506-343 (S) Redeclaration of ArchiveEntry differs from previous
> > > declaration on line 135 of "pg_backup.h".
> > > a - 1506-377 (I) The type "unsigned char*(*)[]" of parameter 7
> > differs from
> > > the previous type "const unsigned char*(*)[]".
> > > make[3]: *** [pg_backup_archiver.o] Error 1
> > > make[3]: Leaving directory `/emrxdbs/postgresql-7.3.2/src/bin/pg_dump'
> > > make[2]: *** [all] Error 2
> > > make[2]: Leaving directory `/emrxdbs/postgresql-7.3.2/src/bin'
> > > make[1]: *** [all] Error 2
> > > make[1]: Leaving directory `/emrxdbs/postgresql-7.3.2/src'
> > > make: *** [all] Error 2
> > > lex:emrx[/emrxdbs/postgresql-7.3.2] lslpp -l bos.adt.libm
> > > Fileset Level State Description
> > >
> >
> --------------------------------------------------------------------------
> > > --
> > > Path: /usr/lib/objrepos
> > > bos.adt.libm 4.3.3.50 COMMITTED Base Application
> > > Development
> > > Math Library
> > >
> > >
> > > ---------------------------(end of
> broadcast)---------------------------
> > > TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
> > >
> >
> > --
> > Bruce Momjian | http://candle.pha.pa.us
> > pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> > + If your life is a hard drive, | 13 Roberts Road
> > + Christ can be your backup. | Newtown Square,
> > Pennsylvania 19073
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html