On Mar 10, 2016, at 8:04 AM, Schneider schneidt@mail.nih.gov wrote:
Kevan:
Still no success in getting a working gpc built...
Thank you for working on this.
I second that!
It's a great relief to me to see that we have a chance of keeping GPC alive on MacOS for another decade, which I think you will achieve if you get the 10.10 compile going. I am still working on 10.7 because I feared GPC would fail to install on the new OS.
It failed for me in 10.10.5. The installation also modified the system sed and that cause me a lot of trouble. Installation scripts must NEVER ever modify system programs!
At least for now, you need a gnu based sed to get GPC built and you need a gnu help2man installed for documentation building and installation. The other utility programs Adriaan's build script build, installs, and system link clobbers aren't necessary since useable versions of them have been part of the system and Xcode tools package for quite some time. (To temporarily workaround stabs debugging info in generated assembly code, I'm also using a separately installed, non-system clobbering gnu based as assembler.)
I'm not sure how to handle satisfying those needs but I definitely agree the base system configuration shouldn't be messed with. Right now as a working approach, I'm doing version specific separate installs in individual version directories in /usr/local/. Since gpc's build machinery can use a SED environment variable to find the sed version to use, I pass in to make a SED set to invoke the gnu based sed and avoid any alterations to the system PATH or system sed linkages. For help2man, I'm doing a temporary addition to PATH to add help2man's installed bin directory to the search PATH.
I'm not too sure how much automation and/or handholding is needed (or desired) for those utility program needs. They are fairly easy to get, build, and install with little or no help if they haven't already been installed for some other reason.
Gale Paeper gpaeper@empirenet.com