Anyway, ran this live at a customer who is working with AIX5, AIX6 and AIX7.
Good news: the package I had built on AIX5, Power5 ran (Syntax test OK) on AIX 7.1 on Power7. Less good news: ./configure did not work using gcc (they had a very old one installed) - embedded apr reported many errors and would not "make". Learned something new about APR - a package only works in the same kind of environment. To my surprise, even though configure was finding xlc as a compiler with my vac v7 it returns "cc" as the compiler - so when I tried to get past the embedded apr compile errors - configure failed again - as cc != gcc and configure said it could not create output. Anyway, until I play with gcc on AIX - not having the scripts is probably safer for 2.2.22 considering it's status. Anyone coming to the devs mailing list will be able to contact me for assistance, should that be so desired. I shall continue looking for ways to resolve this - but now I see a need to have two "APR" external modules based on compiler used. On Tue, Feb 28, 2012 at 11:25 PM, Michael Felt <[email protected]> wrote: > > >> > >> > License acceptance is one thing. I dunno what the copyright issue is. >> >> Again,m copyright is just something "nice", such as: > > Michael, would it be possible to clarify? There is nothing in the >> license for httpd that obligates an end user to accept a license before >> installing, so if they don't need to now, there is no need to change that. >> > > If there is no requirement to accept, then it is easy - but the license > will still be installed in the default location - should be IMHO. > Install Software > > Type or select values in entry fields. > Press Enter AFTER making all desired changes. > > [TOP] [Entry Fields] > * LPP_SOURCE > lpp_5307 > * Software to Install [+ 4.5.0.5301 Open > Se> + > > Customization SCRIPT to run after installation > [] + > (not applicable to SPOTs) > > installp Flags > PREVIEW only? > [no] + > Preview new LICENSE agreements? > [no] + > ACCEPT new license agreements? > [no] + > COMMIT software updates? > [yes] + > SAVE replaced files? > [no] + > AUTOMATICALLY install requisite software? > [yes] + > > > With the above settings, you could get a FAILURE with acceptance required > like this: > LICENSE AGREEMENT FAILURES > ------------------ > The software you have selected for installation contains license > agreement(s) that must be accepted before proceeding. Failure to accept > the license terms will prevent the installation of the software. > Accept the license agreement(s) by selecting "yes" in the > "Accept new license agreements" field or by specifying > the -Y option to the installp command. > > Filesets Requiring Software License Acceptance > ---------------------------------------------- > openssh.base.client > > Without it, or with yes specified anyway, a copyright message similar > this could appear: > > ... > © Copyright Jakob Schlyter, 2003. > © Copyright Dug Song. 1995 > © Copyright Kevin Steves. 1995 > © Copyright Peter Stuge <[email protected]>, 2003 > © Copyright Todd C. Miller, 1998. > © Copyright Darren Tucker 2004. > © Copyright Simon Wilkinson, 2001, 2003. > © Copyright Tatu Ylonen <[email protected]>, Espoo, Finland, 1995 > > All rights reserved. > US Government Users Restricted Rights - Use, duplication or disclosure > restricted by GSA ADP Schedule Contract with IBM Corp. > . . . . . << End of copyright notice for openssh.base >>. . . . > > > In short - niceties. > > Regards, >> Graham >> -- >> >> >
