On 11/13/2017 7:46 AM, William A Rowe Jr wrote:
So, when we prepare source packages, we are using vendor or raw
autocruft packages... Depending on which release, this varies every by
a specific RM.
Q. 1) What source package are you talking about?
http://apache.mirror.triple-it.nl//apr/apr-1.6.3.tar.bz2
Building with:
export OBJECT_MODE=64
$ ../src/apr-1.6.3/configure --prefix=/opt --sysconfdir=/var/apr/etc
--sharedstatedir=/var/apr/com --localstatedir=/var/apr
--mandir=/usr/share/man --infodir=/opt/share/info/apr
compiler: xlc
On Nov 12, 2017 11:47, "Michael" <aixto...@felt.demon.nl
<mailto:aixto...@felt.demon.nl>> wrote:
Hi.
I try to package in dual-ABI (i.e., 32-bit and 64-bit modes) -
with binaries (and scripts) from the 64-bit side.
In other words, only the libraries are "dual".
I just noticed that the build-1/libtool sets a dependancy to
64-bit compiles.
root@x064:[/data/prj/apache/apr-util-1.6.1]lslpp -w
/opt/build-1/libtool
File Fileset Type
----------------------------------------------------------------------------
/opt/build-1/libtool
aixtools.apache.apr.rte File
root@x064:[/data/prj/apache/apr-util-1.6.1]grep q64
/opt/build-1/libtool
LTCFLAGS="-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -q64"
I know how to 'fix it' in that I shall just remove the -q64 from
the LTCFLAGS define.
If you wanted to consider making this more automatic you could set
a condition such that when
OBJECT_MODE=64 the flag -q64 is added, otherwise - not used.
FYI!
regards,
Michael
