packages marked "standalone" have their own package-specific instructions this is described in the paragraph immediately before the package listing
On Mon, 22 Jul 2013 16:51:14 +0000 Reimer, George wrote: > I will try this. In fact I have started to try this, I manually downloaded > the sfio package. But I do also want to emphasize the significant differences > between the instructions you've provided me below with those available to > new/prospective users of the AST software at the AST download page. As it > stands now, right at: > http://www2.research.att.com/~gsf/download/ > I read: > +++++++++++++++++++++ > " The INIT package is required by all but the standalone and self extracting > archive > packages. It contains the package(1) script that controls package > installation and > building. > The packages and instructions are probably very different than what you may > have used > before; the initial setup can be tedious. However, once that's done, > downloading, > updating, reading, building, testing and installing can all be scripted from > the command > line: > package setup # instead of CLICK to download -- you must still use the > license agreement > name and password > package make # if you have source packages > package test > package install DIRECTORY # if you want a separate installation > See the download menu on the left for more information. > Follow the package name links below to view the package descriptions, then > use package > setup (installing source or installing binaries) to download. package setup > downloads > the package closure...." > +++++++++++++++++++++ > And besides that, when I decided to use the sfio package for testing I > clicked on the download link for it at the above URL and read: > ++++++++++++++++++++ > sfio Software Download Package List > The table below lists the releases and versions for the sfio package. Use the > package > setup command to download the latest source or binary package by name, or > click the > RELEASE entries below to download specific packages. The latest releases are > marked with > *. > ++++++++++++++++++++ > The concept that I am trying to get across here is that I and other aspiring > AST software users who try and follow these instructions will retrieve the > INIT package, install it and then follow the instructions above to build > other interesting-looking packages and we will start by running "bin/package > setup ..." and we will get an error when mkdir fails to load because it > cannot find libast.so. Indeed, your instructions below to manually run the > system mkdir are necessary *because* it does not work when you try and run > "bin/package setup". It fails. It fails because it tries to run the included > AST version of 'mkdir' which cannot run because it cannot find 'libast.so'. > Which is not included in the INIT package. > Yours, > George Reimer > -----Original Message----- > From: Glenn Fowler [mailto:[email protected]] > Sent: Monday, July 22, 2013 11:59 AM > To: [email protected]; Reimer, George > Subject: Re: [ast-users] No libast in INIT package? > packages come in 2 flavors: source and binary > in general it is best to build from source to rule out os/compiler diffs > between the ast build farm and other systems > all ast source packages require the INIT package the usual procedure is to > download INIT and the ast-* package you want > mkdir -p bin lib/package/tgz > # download INIT*.tgz ast-*.tgz into lib/package/tgz > # download package into bin/package > chmod +x bin/package > bin/package read > bin/package make > if you take these *exact* steps and get failure then you can email me or the > list with the contents of the file named by the path printed on the standard > output by > bin/package results path > attached or included in the message > background details -- ignore if all you want to do is build and use > INIT contains scripts and commands to bootstrap build the other packages from > source ast uses ast nmake as its build engine any packages you build with out > nmake in scope are automatically built by the bootstrap commands/scripts the > bootstrap build is primariliy for build stuff required by nmake > if you want to develop (edit/patch/recompile/test) ast source it would be > best to download an ast package that contains nmake (ast-base ast-open) > because the bootstrap build may not behave nicely in a development cycle > On Mon, 22 Jul 2013 15:40:36 +0000 Reimer, George wrote: > > > > > > INIT contains only the build system and a way to download the individual > > > source packages. > ast-open is AFAIK the recommended way to obtain all > > > stuff, including libast. > > > > > I cannot test and verify the following as extensively as I'd like, > > because the server on which I can run the INIT package sits behind > > corporate firewalls and cannot download packages. But I believe that your > > statement above is false. INIT does *not* contain a functioning build > > system because INIT, by itself, cannot even execute components like > > ${INSTALLROOT}/bin/mkdir which is called by ${PACKAGEROOT}/bin/package > > setup: > > ++++++++++++++++++++ > > root@lipossrp01ga: # echo $PACKAGEROOT /data/archive/asttest > > /data/archive/asttest > > root@lipossrp01ga: # echo $INSTALLROOT > > /data/archive/asttest/arch/ibm.risc > > /data/archive/asttest > > root@lipossrp01ga: # bin/package setup Could not load program mkdir: > > Dependent module libast.so could not be loaded. > > Could not load module libast.so. > > System error: No such file or directory /data/archive/asttest > > root@lipossrp01ga: # > > ++++++++++++++++++++ > > Even though AST versions of standard Unix commands like 'mkdir' are also > > part of the ast-open package, these commands are included as part of the > > INIT package with the intent (I imagine) of being able to execute them in > > the course of using the INIT package to retrieve and build other AST > > packages. Perhaps it is not necessary to run "bin/package setup" in order > > to do that, and perhaps no other use is made of $INSTALLROOT/bin/mkdir? > > (Nor of 'ratz', 'mamake', 'proto' and 'release', all in $INSTALLROOT/bin > > and which also fail with the same error?) Again, firewalls make it > > impractical for me to try all this out. > > But it seems to me that if you are going to include such binaries as part > > of the INIT package they should be able to execute, either by including > > libast.so (& possibly other dependencies?) or supplying statically-linked > > versions. > > Yours, > > George Reimer > > -----Original Message----- > > From: Irek Szczesniak [mailto:[email protected]] > > Sent: Friday, July 19, 2013 3:20 PM > > To: Reimer, George > > Cc: [email protected] > > Subject: Re: [ast-users] No libast in INIT package? > > On Fri, Jul 12, 2013 at 5:03 PM, Reimer, George > > <[email protected]> wrote: > > > Hello, > > > > > > I'm new to the AST software archive and perhaps I am using > > > things improperly, but as best as I understand the instructions at > > > https://urldefense.proofpoint.com/v1/url?u=http://www2.research.att. > > > co > > > m/sw/download/&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=W%2F5gbnNveYG > > > G1 > > > XCX8vQsiY6orNnjdBtrtn%2BMb0MZjfw%3D%0A&m=m7vyR2p8akeCzEfg2jZunNTQkLw > > > g3 > > > mbCAIr7NRhnMUE%3D%0A&s=0ee56e80e9ec3a07f15d8040ddfcad1f6ecd925567b3cfa941e39cbd4109a9bd > > > , I should be able to use the "package" script in the INIT package to > > > retrieve and install other AST packages, though it's also possible to > > > retrieve and install at least some of them manually. > > INIT contains only the build system and a way to download the individual > > source packages. ast-open is AFAIK the recommended way to obtain all stuff, > > including libast. > > Irek > > _____________ > > The information contained in this message is proprietary and/or > > confidential. If you are not the intended recipient, please: (i) delete the > > message and all copies; (ii) do not disclose, distribute or use the message > > in any manner; and (iii) notify the sender immediately. In addition, please > > be aware that any message addressed to our domain is subject to archiving > > and review by persons other than the intended recipient. Thank you. > > _______________________________________________ > > ast-users mailing list > > [email protected] > > https://urldefense.proofpoint.com/v1/url?u=http://lists.research.att.c > > om/mailman/listinfo/ast-users&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r= > > W%2F5gbnNveYGG1XCX8vQsiY6orNnjdBtrtn%2BMb0MZjfw%3D%0A&m=w79RI4yc8tCFTf > > WewVHn%2Blrw6O9NRbawE%2B58z7if0ng%3D%0A&s=eae716e7e41d85113df7aff9dd66 > > f8fed40c49eea00655502a552bfb74bc1bab > _____________ > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; > and (iii) notify the sender immediately. In addition, please be aware that > any message addressed to our domain is subject to archiving and review by > persons other than the intended recipient. Thank you. _______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
