search for: libf98

...; *** 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 (Aaron Levenstein) Kenneth Hoste ELIS - Ghent University kenneth.hoste at elis.ugent.be ht...

On 01 Sep 2006, at 10:05, Kenneth Hoste wrote: > >> >>> 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. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective

...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://llvm.org/

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 >>