search for: nagfortran

...work much better for you. No, that doesn't seem to be the problem. If I provide the additional --with-f95 option with the correct directory to configure, I still get the same errors (although it mentions /work/NAG_f95/lib/ NAGWare/... not found as errors now). It seems the paths in Makefile.nagfortran (in llvm-test) are hardcoded (lib/NAGWare/quickfit.o and such). When I adjust the settings in Makefile.nagfortran as follows, I'm able to get bytecode file for lucas, galgel and facerec, but make still quits with an error (after generating bytecode files for 7 (out of 26) benchmarks. Al...

...to be the problem. If I provide the additional > --with-f95 option with the correct directory to configure, > I still get the same errors (although it mentions /work/NAG_f95/lib/ > NAGWare/... not found as errors now). Okay, well that's progress. > It seems the paths in Makefile.nagfortran (in llvm-test) are hardcoded > (lib/NAGWare/quickfit.o and such). ok > When I adjust the settings in Makefile.nagfortran as follows, I'm able to get > bytecode file for lucas, galgel and facerec, but make still quits with an > error (after generating > bytecode files for 7 (...

On 31 Aug 2006, at 19:13, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: > >> When I adjust the settings in Makefile.nagfortran as follows, I'm >> able to get bytecode file for lucas, galgel and facerec, but make >> still quits with an error (after generating >> bytecode files for 7 (out of 26) benchmarks. >> >> Also, the file 'libf97.dylib' isn't in my NAG_f95/lib directory...

On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> $ grep F95 .../projects/llvm-test/Makefile.config > > -bash-3.00$ grep F95 projects/llvm-test/Makefile.config > # F95: Enable LLVM to run Fortran benchmarks without a Fortran front-end > USE_F95=1 > F95_DIR := > F95 := /work/NAG_f95/bin/f95 > F95_INC := /work/NAG_f95/lib > F95_LIB := /work/NAG_f95/lib > > Looks

On 30 Aug 2006, at 23:04, Chris Lattner wrote: > On Wed, 30 Aug 2006, Kenneth Hoste wrote: >>> I use NAG with llvm-gcc4. What sort of errors do you get? Did >>> you configure llvm-test with the appropriate flags to find it? >> Yes, I did. llvm-test is configured as follows: (in /work/LLVM/ >> 1.8/ llvm/project/llvm-test): >> ./configure

On Thu, 31 Aug 2006, Kenneth Hoste wrote: > Bummer. I think I'll contact the NAG support for more info on this. Can you > show me the content of your Makefile.nagfortran? It is identical to yours. > Also, it is possible to tell make only to compile benchmark X? How can I > enforce this? Go into the directory for that benchmark, then run 'make' or whatever. -Chris -- http://nondot.org/sabre/ http://llvm.org/

...file | |-- CINT95 | | `-- Makefile | |-- Makefile | |-- Makefile.spec | |-- Makefile.spec2000 | |-- Makefile.spec2006 | |-- Makefile.spec95 | `-- Makefile.spec.config |-- Makefile |-- Makefile.common |-- Makefile.config |-- Makefile.f2c |-- Makefile.nagfortran |-- Makefile.programs |-- Makefile.tests |-- mklib |-- MultiSource | |-- Applications | | |-- Burg | | | |-- Makefile | | | `-- Output | | | `-- be.ll | | `-- Makefile | |-- Makefile | `-- Makefile.multisrc |-- SingleSource | |-- Makefile | |-- Makefile.singl...

On 31 Aug 2006, at 23:46, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> Bummer. I think I'll contact the NAG support for more info on >> this. Can you >> show me the content of your Makefile.nagfortran? > > It is identical to yours. > >> Also, it is possible to tell make only to compile benchmark X? How >> can I >> enforce this? > > Go into the directory for that benchmark, then run 'make' or whatever. OK, I seem to be getting closer to the problem... W...

...my system. I guess this changed in the 5.1 release of f95. Also, there's no NAGWare subdirectory of the lib directory, which should be the case according to the NAG documentation. It seems the libraries are directly located in <path>/lib. This should probably be fixed in the Makefile.nagfortran, but I don't know how (since there's no other *dylib file available it seems). This only generates a warning from gccld, but I think it's the cause of the problems which are reported subsequently. Affected benchmarks: galgel, facerec, sixtrack *** BEAM (fma3d) There seem to be so...

...it (available at ftp://ftp.nag.co.uk/pub/nagware_support/ nplux51na_rh90_282.tgz). > > *** libf97.dylib not found > It appears the *.dylib files are Mac specific. Apparently the usage of f95 was only tested on Mac (I think Chris did this?). Solution (for Linux/x86): modify Makefile.nagfortran: CPPFLAGS += -I$(F95_DIR)/lib LDFLAGS += $(F95_DIR)/lib/quickfit.o $(F95_DIR)/lib/libf98.so $ (F95_DIR) /lib/libf98.a I'll also submit a bug report for this one. greetings, Kenneth -- Statistics are like a bikini. What they reveal is suggestive, but what they conceal is vital (...

...king which extension is used for loadable modules... .so configure: creating ./config.status config.status: creating Makefile.config config.status: executing setup commands config.status: executing Makefile commands config.status: executing Makefile.common commands config.status: executing Makefile.nagfortran commands config.status: executing Makefile.f2c commands config.status: executing Makefile.programs commands config.status: executing Makefile.tests commands config.status: executing TEST.aa.Makefile commands config.status: executing TEST.aa.report commands config.status: executing TEST.example.Make...

...ware_support/ > nplux51na_rh90_282.tgz). >> >> *** libf97.dylib not found >> > > It appears the *.dylib files are Mac specific. Apparently the usage > of f95 was only tested on Mac (I think Chris did this?). > > Solution (for Linux/x86): > > modify Makefile.nagfortran: > > CPPFLAGS += -I$(F95_DIR)/lib > LDFLAGS += $(F95_DIR)/lib/quickfit.o $(F95_DIR)/lib/libf98.so $ > (F95_DIR) /lib/libf98.a > > I'll also submit a bug report for this one. > > greetings, > > Kenneth > > -Chris -- http://nondot.org/sabre/ http://ll...