Frank Heckenbach wrote:
Gale Paeper wrote:
[snip]
Frank, for your information, the *.command files Glenn has referred to are really just plain text shell scripts. They are a user convenience feature Adriaan added to his Mac OS X GPC "compiler sources" download package. They capture everything Adriaan knew at the time he put them together on what it took to get a successful GPC build on Mac OS X version identified in the name of the .command file. In looking at the shell commands in the files, all three of the .command precanned builds do a full install from a FSF gcc sources base.
Do they do a make install (everything), pascal.install (GPC only), or pascal.install-with-gcc (GPC plus required GCC parts)? In the first and last case, such a mismatch shouldn't happen, if paths are correct and everything, of course.
All the native compilers built are built with "sudo make install". The cross compilers have more elaborate make commands.
The relevant lines from the build-on-powerpc-10-4.command script are (watch out for line wrapping):
A) native host PPC compilers:
sudo rm -R -f build mkdir -p build cd build ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 make STAGE1_CFLAGS="-g -DHAVE_DESIGNATED_INITIALIZERS=0" bootstrap sudo make install
B) 10.4 PPC hosted Intel cross compiler:
sudo rm -R -f build-cross mkdir -p build-cross cd build-cross ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=i386-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 --with-sysroot=/Developer/SDKs/MacOSX10.4u.sdk/ --with-arch=pentium-m --with-tune=prescott make RANLIB_FOR_TARGET=ranlib AR_FOR_TARGET=ar NM_FOR_TARGET=nm CC=/Developer/Pascal/gpc345u2/bin/gcc sudo make RANLIB_FOR_TARGET=ranlib AR_FOR_TARGET=ar NM_FOR_TARGET=nm install
There is quite a bit more in the scripts, but I think those are the lines that are relevant to your question. (The B part appears after the A part in the script.)
Before those lines the script does quite a few other things getting everything done that needs to be done to successfully and correctly execute those particular lines.
Each of the three .command script files is on the order of 170 line each which is a litte bit too much to post in full. If you want copies to see the full context to help in providing help with Glenn's problem, let me know and I can send you copies direct to you by e-mail.
Gale Paeper gpaeper@empirenet.com