>
> 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%2F5gbnNveYGG1
> XCX8vQsiY6orNnjdBtrtn%2BMb0MZjfw%3D%0A&m=m7vyR2p8akeCzEfg2jZunNTQkLwg3
> 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]
http://lists.research.att.com/mailman/listinfo/ast-users
