To whom it concerns, I would like to see a change in behavior in config.guess for AIX so that the default output changes from michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]./config.guess
powerpc-ibm-aix6.1.0.0 to michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]./config.guess.new powerpc-ibm-aix6.1.7.0 CHANGELOG: Add baselevel TL identifier to powerpc-aix-version string (e.g., powerpc-aix-7.1.2.0, powerpc-aix-6.1.7.0 and powerpc-aix-5.3.12.0) Long version: The "logic" within IBM is that if something is successful compiled against a lower-level libc (e.g., 5.3.7.0) it should be runnable even in the latest version of AIX rte (e.g., AIX 7.1 TL3 or 7.1.3.0). This does not work in the reverse - all the way, just some. (see base level references below). As a packager I try to package at AIX 5.3.7 because of this. However, should there be something that cannot be packaged at that level I need a safe base for support questions aka about potential incompatibilities with the libc rte. It is not safe to set this at TL0 everytime. case in point - if I should package something using a host at AIX 6.1.9.X I can expect it to work properly as far back as AIX 6.1.7.0, but not at AIX 6.1.6.0 or older - even if the run-time linker seems to load the program. I am considered "somewhat" of an authority when it comes to AIX and in that sense there are few things I would like to see different in they way GNU looks at and/or works on AIX when it comes to packaging GNU tools. GNU is certainly leading when it comes to setting generic ways for developing open-source (open-platform read any-platform) software. Where things go wrong around AIX the root cause can frequently be found in a overly simplified view of what level of AIX should work with an application. Changes happen, base requirements change. To say that AIX 5.3 from 2004 is the same as AIX 5.3 in 2014 is not logical. The same can be said for AIX 6.1 - arriving in 2007 and still being updated. AIX 7.1 TL0 and AIX 7.1 TL1 also have some incompatibilities (when moving backwards). The patch I suggest is to include something of the TL (technology level). Until 2004-2005 the was called the maintenance level (and would have been seen with oslevel -r). What's in a name? However, in 2007 a new fileset naming convention became official. The third number in the fileset was fixed to the technology level (e.g., 5.3.7.23 can be read as fix 23 for oslevel 5.3.7.0 for that particular fileset). However, even with higher TL levels there may be a common-base that is at a lower TL level. Example: currently I have an AIX system at AIX 6.1 TL9. While the patch/updates are all at 6.1.9.X levels, the so-called base-level levels are AIX 6.1.7.0. The command lslpp reveals these differences (the argument -I reports base levels rather than latest/any levels). As far as problem determination, feature awareness, etc. having the base level is helpful. The change I suggest is looking at the fileset that holds /usr/lib/libc.a. The other choice would be the one that holds /usr/lib/boot/unix_mp. My preference is for libc as that feels closer of software development AND the fileset is the same over all versions of AIX whereas the "/unix" fileset has different names prior to AIX 5.3 TL7. Of course, if this change would break anything, the change is not serving it's intended purpose. If you have any questions I will respond as best I can. Sincerely, Michael Felt aka aixto...@gmial.com, http://www.rootvg.net, http://www.aixtools.net, etc.. ±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±± michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]e.libc | awk -F: ' { print $3 } ' < 6.1.7.0 michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]./config.guess powerpc-ibm-aix6.1.0.0 michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]./config.guess.new powerpc-ibm-aix6.1.7.0 michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]/usr/bin/lslpp -LIqc bos.rte.libc | awk -F: ' { print> 6.1.7.0 michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]time /usr/bin/lslpp -LIqc bos.rte.libc | awk -F: ' { > 6.1.7.0 real 0m0.60s user 0m0.24s sys 0m0.22s michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]time oslevel -s 6100-09-03-1415 real 0m5.50s user 0m2.32s sys 0m1.90s michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]time /usr/bin/lslpp -Lqc bos.rte.libc | awk -F: ' { p> 6.1.9.15 real 0m0.59s user 0m0.00s sys 0m0.01s michael@x054:[/data/prj/gnu/libtool/libtool-2.4.3/build-aux]
config.guess.patch
Description: Binary data
_______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
