similar to: LINUX gfortran.so.3 missing

Hi, I replaced my Rtools today as posted at http://www.murdoch-sutherland.com/Rtools/Rtools.exe Trying to build R-devel_2007-12-13.tar.gz without modifying MkRules gives the gfortran command not found error below. I am wondering if gfortran.exe is missing from (recent?) Rtools.exe or I am doing something wrong. Thanks to hints at Duncan's site, I worked around the error by adding

John Putz wrote: > Thanks. > > */ > email: /**/johnputz3655@yahoo.com/* <mailto:johnputz3655@yahoo.com> > */home: 206-632-6522 > cell: 206-910-5229/* > > > ----- Original Message ---- > From: Joe W. Byers <ecjbosu@aol.com> > To: John Putz <johnputz3655@yahoo.com> > Cc: r-sig-finance@stat.math.ethz.ch > Sent: Friday, December 7, 2007

The previously posted benchnarks for gcc vs llvm-gfortran had one mistake. I was actually had the gfortran for 4.3.1 installed instead of that from gcc 4.2.4. Below are the polyhedron benchmark results for all three compilers... gfortran 4.2.4 Benchmark Compile Executable Ave Run Number Estim Name (secs) (bytes) (secs) Repeats Err % --------- -------

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

I've benchmarked the llvm 2.3/llvm-gcc-4.2 release against the stock gfortran compiler from gcc 4.2.4 on a 2.33GHz MacBook Pro using the '-ffast-math -funroll-loops -msse3 -O3' optimization flags. llvm-gfortran Benchmark Compile Executable Ave Run Number Estim Name (secs) (bytes) (secs) Repeats Err % --------- ------- ---------- ------- -------

Hi, in trying to build an llvm-gfortran on linux from today's gcc4 SVN, I get the following link errors that didn't show up on OS X. This is also using LLVM CVS from this morning. They appear to mostly be related to CodeWarrior compatibility code, but a couple are less obvious. What's the best way to fix this? I'm stuck without my powerbook for at least three weeks and I'd

Roger, On 4 August 2019 at 06:48, Koenker, Roger W wrote: | I?d like to solicit some advice on a debugging problem I have in the quantreg package. | Kurt and Brian have reported to me that on Debian machines with gfortran 9 | | library(quantreg) | f = summary(rq(foodexp ~ income, data = engel, tau = 1:4/5)) | plot(f) | | fails because summary() produces bogus estimates of the coefficient

On Mon, Jan 19, 2009 at 2:05 PM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: > The current llvm/llvm-gcc4.2 svn is now fixed with > respect to the extra warnings that were being emitted > by the gfortran compiler. The gfortran testsuite results > under Intel Darwin9 are appended below. Yay! Thanks for testing this out. > Native configuration is i686-apple-darwin9 >

Hello folks, I want to compile some fortran code to IR, but llvm-gfortran 4.2-2.9 does compile my fortran code. gfortran 4.2.1 fail with the same error. but gfortran 4.4.6 and ifort compiles fine. Attached is the file causing error. Error message is m_List.F90: In function 'exporttostring_': m_List.F90:925: error: conversion to non-scalar type requested I wonder if there any way I can

Roger, I have run gfortran -c -fsyntax-only -fimplicit-none -Wall -pedantic rqbr.f in the src folder of quantreg. There are many warnings about defined but not used labels. Also two errors such as "Symbol ?in? at (1) has no IMPLICIT type". And warnings such as: Warning: "Possible change of value in conversion from REAL(8) to INTEGER(4) at ..." No offense intended but

On Tue, Jun 7, 2011 at 2:33 PM, Yuanfang Chen <tabloid.adroit at gmail.com> wrote: > Hello folks, > I want to compile some fortran code to IR, but llvm-gfortran 4.2-2.9 does > compile my fortran code. gfortran 4.2.1 fail with the same error. but > gfortran 4.4.6 and ifort compiles fine. Attached is the file causing > error. Error message is > m_List.F90: In function

Hi Jack, thanks for the numbers. Any chance of analysing why gcc does better on those where it does much better than dragonegg? Ciao, Duncan. > With the case-insensitive file system patch from http://llvm.org/bugs/show_bug.cgi?id=9656#c15 > applied to dragonegg 2.9, the following Polyhedron 2005 benchmarks are seen on x86_64-apple-darwin10 > under gcc 4.5.3svn using the dragonegg

Hello, gfortran-4.4 is not in the synaptic package manager. Effort to search for it on the web is not fruitful. I tried to install gcc-4.4 in place of it. That does not solve my problem either. Another machine that has gfortran-4.4 runs my code without error. Attempt to run the same code with gcc-4.4 failed. I equally tried running the same code with gfortran-4.3 but that resulted in error. Any

We're finding that several of the packages we need don't compile using the version 4.1.2 of gfortran that comes with CentOS 5.4. So, I've built the latest version of gfortran (e.g. 4.4.2) but I've done it so that all the new version's files go in /share/apps/gnu so that they don't interfere with the standard gcc distribution (building gfortran requires building some parts

On Wed, 30 Aug 2006, Michael McCracken wrote: > Hi, in a thread this afternoon about compiling the Fortran SPEC2000 to > LLVM bytecode, Chris mentioned that it should be possible to compile > to LLVM with the gfortran front end, although no one has necessarily > tried it. Yup. > I was surprised (and happy) to hear this, as under the impression that > it would require a

On 9/11/06, Chris Lattner <sabre at nondot.org> wrote: > On Sat, 9 Sep 2006, Michael McCracken wrote: > >> No, gfortran in gcc 4.0 is, ehm, highly experimental (read: a piece of > >> junk). Gfortran in gcc 4.1 was the first one that worked for NIST (and > >> for SPEC). > > > > Hm. I had noticed a bunch of changes in the current sources, but had >

Another option might be g95 instead of gfortran. I haven't used it for a while, but I seem to recall it working fine in gcc 4.0.1. On 9/11/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/9/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > > On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote: > > > On 9/9/06, Chris

Dirk, Thanks for the blog post on this, and the pointers in this email. I have a question: it seems to me that you end up using a different compiler for the package (quantreg) than was used to build R itself. As I understand ABI changes, this is considered unsupported (ok, that depends on what version of gcc/gfortran was used to build R, but there has been a lot of ABI changes in GCC). Is that

On 9/9/06, Steven Bosscher <stevenb.gcc at gmail.com> wrote: > On 9/9/06, Chris Lattner <sabre at nondot.org> wrote: > > On Sat, 9 Sep 2006, Steven Bosscher wrote: > > > You wrote: > > >> The NIST F77 test suite doesn't seem to be compatible with gfortran at > > >> all, > > > Actually, the entire suite compiles flawlessly with

With the case-insensitive file system patch from http://llvm.org/bugs/show_bug.cgi?id=9656#c15 applied to dragonegg 2.9, the following Polyhedron 2005 benchmarks are seen on x86_64-apple-darwin10 under gcc 4.5.3svn using the dragonegg plugin... ================================================================================ Date & Time : 8 Apr 2011 19:52:56 Test Name :