More follow-up: Thanks to Glenn Fowler for making a suggestion that I use a symbolic link to the root directory. I got past my original problem of the package command generating directory names beginning with "//" (e.g., //arc, //bin, etc.). To get to this stage I created a symbolic link in my CygWin root directory and called it /ast which I targeted to the root directory. Thus /ast ==> /
Before running the package command again I executed a "cd /ast" This works to resolve my initial problem . But now I have others. Package generates some directory names that don't make sense (part of the directory chain doesn't exist or binaries actually exist in other directories. For example, _RLD_ROOT=/ast/arch/cygwin.i386/arch::/ Export _RLD_ROOT There isn't an arch subdirectory under /ast/arch/Cygwin.i386. arch is located at /ast/arch. It is not located at /ast/arch/Cygwin.i386/arch. Another erroneously generated path is SHELL=/ast/arch/cygwin.i386/bin/sh. sh exists in /ast/bin, not in /ast/arch/whatever... After all the environment names and values are generated, I get to a debug line that says Export VPATH Following that, I get line after line of package: <some environment name>: package archive not found. <some environment name> is PACKAGEROOT, HOSTTYPE, SecureID, Token, Files, Files/Roxio and so on. Basically, every directory in the global Windows PATH setting is listed on its own line with the message from package telling me the archive is not found. I thought the archive package was being pulled remotely from http://www.research.att.com/sw/download/ast-base.2011-02-08.cygwin.i386.tgz. So why is the package command looking for it on my local drive in all of the directories in the Windows PATH? Richard Naff Genesis Network Solutions, Abilene, TX 325-437-9186 Office 888-671-3711 Call-back pager [email protected]<mailto:[email protected]> Text pager
_______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
