Simon J Mudd <[EMAIL PROTECTED]> writes: > Doug Summers <[EMAIL PROTECTED]> writes: > > > After I finish my toolset upgrades I'll try building python. > > I'll try and rebuild python on OpenPKG-STABLE or CURRENT, but looking > at the rpmdiff[1] output between openpkg-2.5.0-2.5.0.src.rpm and > openpkg-20061030-20061030.src.rpm I can't see anything that looks like > it will fix the shtool problem. I'll try anyway just to confirm.
openpkg-2.5.4-2.5.4 builds fine but has the same issue (shtool fails). openpkg-2.20061030-2.20061030 fails to build (as reported in the other thread). So on AIX 5.3 we've only built: gcc-4.0.2-2.5.0 perl-5.8.7-2.5.0 bison-2.1-2.5.0 db-4.3.29.0-2.5.0 openssl-0.9.8a-2.5.0 cfengine-2.1.20-2.20060622 openpkg-2.5.4-2.5.4 gpg-pubkey-63c4cb9f-3c591eda make-3.80-2.5.0 m4-1.4.3-2.5.0 flex-2.5.31-2.5.0 fsl-1.6.1-2.5.0 zlib-1.2.3-2.5.0 autoconf-2.59-2.5.0 I'm hoping to use cfengine with yum (which requires python) to deploy our custom rpms (not OpenPKG yet) on to the servers. While yum is not strictly necessary it more closely matches the cfengine procedures currently used on our Linux servers to install software packages. I may try manually adjusting the shtool shell to use $prefix/lib/openpkg/bash rather than /bin/sh as the shell to see if that allows the python build to finish. Not a solution but at least it lets me see if there are other issues when building python. Regards, Simon ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org
