The short of it: the suggestion below didn't have any effect on the error. The long of it is listed down below.
Basically, the current set of Build instructions for PRC-Tools doesn't seem to be working with the current version of cygwin...When I try to build only the m68K-palmos compiler, I get the error on the 'install' command listed below. The compile works, but installation doesn't. When I try to build both m68K and arm support, I get varied errors, compiler not working, etc. Simply too many problems to mention them all here. Any further ideas from anyone would surely be appreciated! -Ken On Wed, 2003-03-19 at 21:52, Ton van Overbeek wrote: > kcorey <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > Has anyone else tried recompiling prc-tools under Developer Studio's > > version of Cygwin? > > My guess is that you ran configure without any arguments. > It then tries to install it in the /usr/local/ tree: executables in > /usr/local/bin, libs in /usr/local/lib, etc. > I suppose the directory /usr/local does not exist. > If you want the standard prc-tools installation locations (as per the > prc-tools distribution form sourceforge) add the --prefix=/usr option > to configure. Hrm, the info page for install says that "install -c -d path" is the command to create all the elements in the given path, so I don't understand why there should be a problem relating to the --prefix option. Still, I tried it with adding the '--prefix=/usr' to the initial configure command, and no joy, got the same error. Then I tried completely removing Cygwin, and starting from absolute scratch. I downloaded the setup program from the cygwin home page, and did a fresh install, installing *everything*...a 300MB download that ran overnight. No joy again, with a strange error, though this might be because of a misguided attempt to also build the arm tools. So, I removed that big cygwin, did a fresh minimal install, and started at the very top of the 'Building PRC-Tools' page, and tried again. This time, however, I only attempted to build the m68K version. After much crunching and grinding, I got the same error: --------------------------------------------------------- make[1]: Entering directory `/tmp/prctoolsbuild/build/crt' cd mown-gp; make CC="m68k-palmos-gcc" AR="m68k-palmos-ar" RANLIB="m68k-palmos-ra nlib" \ SDKFLAGS="" MULTIFLAGS=-mown-gp \ `echo mown-gp/crt0.o mown-gp/scrt0.o mown-gp/gdbstub.o mown-gp/libcrt.a | sed 's,[^ /]*/,,g'` make[2]: Entering directory `/tmp/prctoolsbuild/build/crt/mown-gp' make[2]: `crt0.o' is up to date. make[2]: `scrt0.o' is up to date. make[2]: `gdbstub.o' is up to date. make[2]: `libcrt.a' is up to date. make[2]: Leaving directory `/tmp/prctoolsbuild/build/crt/mown-gp' /cygdrive/c/Program Files/Cygwin/bin/install -c -d /usr/m68k-palmos/lib make[1]: *** [install] Error 255 make[1]: Leaving directory `/tmp/prctoolsbuild/build/crt' make: *** [install] Error 1 --------------------------------------------------------- FWIW, when I tried to build the arm tools too, the build became unreliable. At various points the build process seemed to overwrite the gcc compiler running on the intel box so that the compiler wouldn't work after that until I did a reinstall of the GCC compiler through the cygwin setup tool. The configure command I used contained '--enable-targets=m68k-palmos,arm-palmos' instead of the standard --target. It seemed to accept this just fine, but I got several different errors at various points during the build cycle. -Ken -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
