Thanks Mikael.
[I too wondered if this topic was appropriate for the list and in the
end thought it might be. We can probably take this offline after this
exchange and summarize if appropriate.]
The actual source of the package is here:
https://download.mosek.com/R/10.1/src/contrib/Rmosek_10
Package Rmosek compiles fine using Matrix versions 1.6.2- but not with
anything beyond Matrix 1.6.2. (FYI, Rmosek provides R interfaces to the
excellent MOSEK solver; academic licenses are free.)
Here is the error message:
rmsk_obj_matrices.cc:50:9: error: use of undeclared identifier
'Ma
people that reports are a lot more useful *before* the
release - that's why we publish RCs.
Thanks,
Simon
On Nov 2, 2021, at 3:03 PM, Balasubramanian Narasimhan
wrote:
The Mac OS M1 pre-built binary arrives with a
/Library/Frameworks/R.framework/Resources/etc/Makevars containing
FLIBS =
The Mac OS M1 pre-built binary arrives with a
/Library/Frameworks/R.framework/Resources/etc/Makevars containing
FLIBS =
-L/Volumes/Builds/opt/R/arm64/gfortran/lib/gcc/aarch64-apple-darwin20.2.0/11.0.0
-L/Volumes/Builds/opt/R/arm64/gfortran/lib/gcc
-L/Volumes/Builds/opt/R/arm64/gfortran/lib -l
For the example provided below, the subsetting happens in evaluating the
call to stats::model.formula in line 583 of nls.R
(https://github.com/wch/r-source/blob/e91be22f6f37644e5a0ba74a3dfe504a3a29e9f7/src/library/stats/R/nls.R#L583)
returning an appropriate (subsetted) data frame.
-Naras
On
Confession: haven't done this in decades.
Isn't the usual way to use 'xwininfo' to figure out the information
about any X window and set a specific resource in the .X11defaults or
equivalent? Also doing the same with windows that aggregate could yield
a common resource, perhaps?
-Naras
On
Also, just came to know about dotcall64::.C64() (on CRAN) which allows
for Fortran to be called using .Call().
-Naras
On 12/23/20 8:34 AM, Balasubramanian Narasimhan wrote:
I think it should be pretty easy to fix up SUtools to use the .Call
instead of .Fortran following along the lines of
CYs$
[3]
https://urldefense.com/v3/__https://github.com/t-kalinowski/RFI__;!!DZ3fjg!s1-ihrZ9DPUtXpxdIpJPA1VedpZFt12Ahmn4CycOmile_uSahFZnJPn_5KPIbwXmXqY$
Tomasz Kalinowski
On Tue, Dec 22, 2020 at 7:24 PM Balasubramanian Narasimhan
wrote:
To deal with such Fortran issues in several packages I deal with, I
wr
To deal with such Fortran issues in several packages I deal with, I
wrote the SUtools package (https://github.com/bnaras/SUtools) that you
can try. The current version generates the registration assuming
implicit Fortran naming conventions though. (I've been meaning to
upgrade it to use the gf
On 8/4/19 7:26 AM, Berend Hasselman wrote:
> 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 IMPL
The original post below refers to an issue that arose with glmnet. It
has since been fixed but the underlying problem (I believe) is a bug in
gcc/gfortran 2.6.3 toolchain. Here is a reproducible example, test.f90.
program dblbug
real :: x, y
x=2
y=exp(dble(x))
end program dblbug
Compile
11 matches
Mail list logo