search for: alt_duleg

..., and I get the same (incorrect) behavior as the PC. Simply by inserting debug WRITE statements in the FORTRAN I would get different, and correct, results, so I assumed it was an optimization error. So, 1) R CMD SHLIB duleg.f does not work, and produces bogus code however, 2) gfortran -c alt_duleg.f gcc -O -std=gnu99 -shared -L/usr/local/lib -o alt_duleg.so alt_duleg.o -lgfortran -lm -lgcc_s does work (note the -O low optimization). Otherwise the gcc command is identical to the one produced by R CMD SHLIB. Has anyone else seen this? Is there a simple way to have my package...