search for: nag

Displaying 20 results from an estimated 410 matches for "nag".

Did you mean: na
2004 Oct 29
1
problem building an R package under Windows XP with calls to NAG C routines
Hello all, I was able to create R packages under windows XP in the past using the dynamic NAG C library for windows XP (Mark 6). Recently, I changed computers and I am now using the static NAG C library for windows XP (Mark 7) to create a simple R package (called "test") which simply returns random numbers simulated using repetitive calls to a NAG C routine (uniform random gen...
2004 Sep 20
1
unable to load shared library "/home/hpc1367/runs/taper/taper.so"
...elocation error: file /home/hpc1367/runs/taper/taper.so: symbol f90_init: referenced symbol not found also tried with default local=T and got same error. my makefile (used to produce the .so) is included below F90S = taper.f90 OBJS = taper.o LIBS = -lsocket -lnsl -lintl OPT = -fast MODS = -M/opt/NAG/fnsol04dbl/nag_mod_dir NAG = /opt/NAG/fnsol04dbl/libnagfl90.a STATNAG = /opt/NAG/flsol20dal/libnag.a taper.o : taper.f90 f95 -c -dalign $(OPT) $(MODS) taper.f90 taper.so: taper.f90 f95 -o taper.so -G -dalign $(OPT) $(MODS) taper.f90 taper.x : taper.o f95 -o taper.x -dal...
2006 Aug 31
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> It doesn't to me. If you set F95_DIR to /work/NAG_f95 things will >> probably 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/....
2006 Aug 31
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...te: >>> $ 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 ok to me... > > It doesn't to me. If you set F95_DIR to /work/NAG_f95 things will > probably work much better for you. No, that doesn't seem to be the problem. If I p...
2017 Jun 15
1
How to expand Replicated Volume
Hi Nag Pavan Chilakam Can I use this command "gluster vol add-brick vol1 replica 2 file01g:/brick3/data/vol1 file02g:/brick4/data/vol1" in both file server 01 and 02 exited without add new servers. Is it ok for expanding volume? Thanks for your support Regards, Giang 2017-06-14 22:26 GMT+07...
2006 Aug 31
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 di...
2006 Nov 08
4
[LLVMdev] Fortran and LLVM
...u can't just link c-common.o in, because then you get multiple definitions of some symbols. However, judging from past threads on here, it seems that getting gfortran support will require a lot of work. I've also seen people who use LLVM and Fortran to compile the SPEC FP benchmarks - the NAG compiler has been mentioned in this context. I have two questions here: 1. I know someone previously tried to get gfortran working - did their changes make it into the SVN mainline? 2. How do you go about hooking LLVM into the NAG compiler? Does it emit an IR that LLVM recognises? Cheers, War...
2008 Oct 31
1
[LLVMdev] Several questions about LLVM
Eduardo Brito wrote: > The only fortran to C compiler that I know of, only accepts Fortran 77. > Fortran 90, 95 and up, aren't supported by any tool... > We have a commercial FORTRAN to C tool from NAG; I believe it supports Fortran 95 and maybe even later versions. Their website is at http://www.nag.co.uk (http://www.nag.com for North America). -- John T. > John Criswell escreveu: > >> Another option is to use a FORTRAN to C compiler to convert your FORTRAN >> code to...
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
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 fo...
2006 Sep 01
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...ow problem. Fix is shown at http://lists.cs.uiuc.edu/ pipermail/llvm-commits/Week-of-Mon-20060828/037184.html Thanks to Reid for mentioning this (on IRC). Reason: crtend is a library used in the old frontend, and the Makefile weren't aware of this. > > +++ following errors seem to be NAG-specific +++ > The NAG support was really friendly, here's how the NAG problems got fixed. > *** BEAM (fma3d) > > There seem to be some issues with the fma3d benchmark, when > translating from Fortran to C: > > f95 -w -S -O2 <path>/SPEC_CPU2000_1.3_src/benchspec/C...
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...; 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 subdirectory of llvm-test/External/SPEC. My setup: LLVM-1.8 with the gcc4 frontend (gcc-4.0.1). The NAG f95 compiler is v5.1(216). My platform is Fedora Core 4 on a Intel Pentium 4. I was confronted with 6 different errors for the various benchmarks, 4 of which are relate to the NAG f95 compiler. See below for details. I seems most of the error are directly related to f95, which seems to have...
2006 Aug 30
2
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...roblem I'm facing is the Fortran benchmarks, for which some partial support is already available it seems (using f2c). Unfortunately the f2c compiler only allows the translation of Fortran-77 programs to C code (which is then compiled using llvm-gcc). Another solution is the commercial f95 NAG Fortran compiler, for which some support seems to be available in the Testsuite. Only, I can't get it to work, although my NAG f95 compiler is working. Is it normal that this support is broken? I'm getting all kinds of errors... Also, with the new gcc4 frontend, it seems the Fortran...
2006 Sep 01
0
[LLVMdev] compiling the full SPEC CPU2000 suite to LLVM bytecode
...u "out of the box". The one useful thing I can contribute w.r.t. this email is that the *warnings* about crtend can be simply ignored. If you update to llvm cvs, they will be gone, but they don't hurt anything with LLVM 1.8. I hope that you do figure out what has changed between NAG 5.0 and 5.1, because I *do* want you to be successful. If NAG doesn't work, perhaps you could contribute to getting gfortran up and running. -Chris > +++ New/remaining problems +++ > > Currently, 9/26 benchmarks compile and run succesfully. One (fma3d) > still has a f95 related...
2015 Jul 01
0
What causes phantom update nags?
On 7/1/2015 2:02 PM, Kay Schenk wrote: > My Update Applet keeps giving me messages to install an update to a > package I do not have installed. To make matters more confusing, when I > actually try to install the package it wants to update, there is a > problem with the installation. > > Any tips on how to resolve this? Is this somehow caused by the > repositories I have
2015 Jul 02
0
What causes phantom update nags?
On 7/1/2015 2:35 PM, Kay Schenk wrote: > OK, here ya go -- > > Obsoleting Packages > > perl-IO-Compress.noarch 2.052-1.el6.rfx rpmforge-extras > perl-IO-Compress-Bzip2.i686 2.021-136.el6_6.1 @updates > perl-IO-Compress.noarch 2.052-1.el6.rfx rpmforge-extras > perl-Compress-Zlib.i686 2.021-136.el6_6.1 @updates > perl-IO-Compress.noarch 2.052-1.el6.rfx rpmforge-extras >
2015 Jul 02
0
What causes phantom update nags?
On 7/2/2015 10:20 AM, Kay Schenk wrote: > Yes, I did see this warning on CentOS wiki re RPMForge but decided to > use it anyway. But how does this relate to the problem? I DO NOT even > have perl-IO-Compress installed. Mostly I figured this was a repository > entanglement problem, but I didn't know why. I mean why do I keep > getting messages about updating something I don't
2011 Aug 15
2
A small nag
Hi, I am not sure how to fix the following error. LGD <- c(11.6, 12.3, 15.8, 33.1, 43.5, 51.3, 67.3, 84.9) cor (x=(file [1:47231,3:10]), y= rep (LGD, 47231), method = "pearson") Error in cor(x = (file[1:47231, 3:10]), y = rep(LGD, 47231), method = "pearson") : incompatible dimensions > sessionInfo() R version 2.13.0 (2011-04-13)
2007 Jan 12
1
cepstral voice still nags after registration
I'm using trixbox and the asterisk agi. I downloaded a cepstral voice and worked with it until I got the code to do what I wanted. I then registered the voice today to get rid of the 'this voice is not yet registered", stuff yet it still does that. Any ideas on how to fix this? It told me my info was valid. Thanks! -------------- next part -------------- An HTML attachment was
2005 Apr 08
2
Nagging error
Hello to all. I keep getting the same error in the logs of all my Samba boxes: Apr 8 09:00:19 hanover smbd[19917]: [2005/04/08 09:00:19, 0] lib/util_sock.c:read_socket_data(384) Apr 8 09:00:19 hanover smbd[19917]: read_socket_data: recv failure for 4. Error = Connection reset by peer If this has been posted before, my apologies. I've RTFM, and I've googled for a solution, and
2012 Jul 02
1
Yet another pull request nag for 6654 -- postgresql-auto-reconnect-2
... to fix a problem with PostgreSQL reconnect after connection loss & put test coverage in place to keep it working in the future. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/EecNy-qyKwgJ. To post to this group, send email to