search for: haveg77

...a description of the differences? (c) Is someone interested in this port? If yes, I can make it available. I tried to make rebuilding easy. Essentially, you untar a small archive in src/ (essentially the makefiles and the pacthed windows sources). Then make RHOME=??? firstofall make RHOME=??? HAVEG77=[YES,NO] make RHOME=??? HAVEG77=[YES,NO] packages should build and install the system with all the packages in src/library; make RHOME=??? HAVEG77=[YES,NO] pkg-??? will make the package ???. You need gnu-make+sed+rm+cp+ls. ( perhaps also a sh-like shell (I used bash)). I have not tried but thi...

...a description of the differences? (c) Is someone interested in this port? If yes, I can make it available. I tried to make rebuilding easy. Essentially, you untar a small archive in src/ (essentially the makefiles and the pacthed windows sources). Then make RHOME=??? firstofall make RHOME=??? HAVEG77=[YES,NO] make RHOME=??? HAVEG77=[YES,NO] packages should build and install the system with all the packages in src/library; make RHOME=??? HAVEG77=[YES,NO] pkg-??? will make the package ???. You need gnu-make+sed+rm+cp+ls. ( perhaps also a sh-like shell (I used bash)). I have not tried but thi...

...windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVEG77=NO pkg-xxx For example, the g77 compiler in egcs-mingw32 was not able to compile the fortran code in the acepack package. However, I was able to build this package with the command > make HAVEG77=NO pkg-acepack (4) When installing a package, i...

...windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVEG77=NO pkg-xxx For example, the g77 compiler in egcs-mingw32 was not able to compile the fortran code in the acepack package. However, I was able to build this package with the command > make HAVEG77=NO pkg-acepack (4) When installing a package, i...

...ctory and type > make This will build the main executable (in R-0.61.3/bin) and the standard packages: base, eda, mva, stepfun. Installing other packages Uncompress the package you want in R-0.61.3/src/library. Then, from the gnuwin32 directory, > make -f MakePkg -C ../library/xxx PKG=xxx [HAVEG77=NO] [DLLNAME=yyy] will try to build the package xxx. The HAVEG77=NO options must be used if: (a) you don't have or don't want to use g77; or (b) the package has a src-c directory but not a src one. The option DLLNAME=yyy must be used if the package requires a dll with a name different from...

...ctory and type > make This will build the main executable (in R-0.61.3/bin) and the standard packages: base, eda, mva, stepfun. Installing other packages Uncompress the package you want in R-0.61.3/src/library. Then, from the gnuwin32 directory, > make -f MakePkg -C ../library/xxx PKG=xxx [HAVEG77=NO] [DLLNAME=yyy] will try to build the package xxx. The HAVEG77=NO options must be used if: (a) you don't have or don't want to use g77; or (b) the package has a src-c directory but not a src one. The option DLLNAME=yyy must be used if the package requires a dll with a name different from...

...windows. You can find it in any SIMTEL mirror. If you want, I can make available a small file with only the needed tools. (3) The gnuwin32/Makefile use the g77 Fortran compiler. If you don't have it, or if you don't want to use it, you can use something like > make HAVEG77=NO or > make HAVEG77=NO pkg-xxx For example, the g77 compiler in egcs-mingw32 was not able to compile the fortran code in the acepack package. However, I was able to build this package with the command > make HAVEG77=NO pkg-acepack (4) When installing a package, i...