similar to: Installation problem with package mixtools

Hello, Can the x and y axis limits be specified in a density plot with the mixtools package for a finite mixture model? Uncommenting the xlim2/ ylim2 lines in the plot command below generates 'not a graphical parameter' warnings (and does not change the axis settings), and uncommenting the xlim/ylim lines generates a 'formal argument "ylim" matched by multiple actual

Hi, I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04, llvm-gfortran gave me following errors $ llvm-gfortran -Wall hello.f95 -o hellof /home/jli127/LLVM/llvm-gcc/install/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.2.1/../../../../lib64/libgfortran.a(error.o): In function `_gfortrani_gfc_itoa':

I just essentially the same question on this mailing list and the problem ended up being that my cpu's architecture was not supported by the ubuntu releases (or any releases for that matter). I had to build R from source, but it wasn't much headache. The Ubuntu releases only support i386 and amd64 --- i.e. 32 bit & 64 bit intel and amd cpus and not, e.g., the arm cpus that are

Hi Duncan, Thanks for your answers. Compiling .s file is OK after adding the -lgfortran -lgfortranbegin. I replace my Ubuntu 8.04 and by Ubuntu 8.10. And I checked all new packages installed by 'apt-get' are amd64 version. However after compiling the llvm-gfortran, I got the same error. Here is my configure arguments $ ../llvm-gcc4.2-2.3.source/configure --prefix=`pwd`/../install

I've created fink packaging for a building the llvm and llvm-gcc-4.2 svn pulls under fink on Mac OS X. Hopefully the fink info script and patch should be clear enough for some comments on my build approach. The llvm-gcc and llvm-g++ compilers seem okay so far. The llvm-gfortran compiler seems to always spew a warning.. WARNING: 128-bit integers not supported! ...even when just compiling a

Hi, > I have installed llvm and llvm-gfortran on Pentium4 machine using 32-bit > Ubuntu, it works fine. I recently installed them on AMD64-Ubuntu 8.04, > llvm-gfortran gave me following errors > > $ llvm-gfortran -Wall hello.f95 -o hellof this works here on x86-64 ubuntu 8.10. I took a look in my libgfortran.a and it doesn't reference any of the symbols you mention. >

I have 2 questions concerning the EM algorithm. Is it true that the EM algorithm gives unique answers for the means and variances of a mixture of 2 normals? I am using mixtools and I am surprised that it works better than a Bayesian program I wrote. If so can someone say why the mixing probabilities are so good? -- Thanks, Jim. [[alternative HTML version deleted]]

Hello all, May be silly question, but what exactly is beta parameter in functions like regmixEM from mixtools package? I mean, how to determine this beta, if i have a set of metrics for each case? Is there a function for that? I have try to put NULL at this parameter, but function just do not work in this case. Cheers, Dima [[alternative HTML version deleted]]

Ashay, If I understand correctly, in hw.o you would have llvm bytecode, while linker expects regular object binary. Probably first you need to emit asm out of bytecode using llc? - D. 2011/9/12 Ashay Rane <ashay.rane at tacc.utexas.edu>: > Hello, > Sorry for the late reply. Using dragonegg worked well, thanks all! > Just as a note... I had to use llvm-ld during the link step

Dear all, on CentOS 6 one could use -static-libgcc -static-libgfortran to obtain a binary which would run on other computers which don't have gfortran installed. On CentOS 7 one can install the libgfortran-static and libquadmath-static RPMs but the resulting binary _still_ requires /lib64/libquadmath.so as revealed by ldd. gfortran does not recognize an option like -static-libquadmath .

On 9/1/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/1/06, Chris Lattner <sabre at nondot.org> wrote: > > On Fri, 1 Sep 2006, Michael McCracken wrote: [snip] > Now f951 doesn't crash when compiling, but still can't compile the > libgfortran files. It now finds some syntax errors in a generated file > that's part of the intrinsics

Hello, Sorry for the late reply. Using dragonegg worked well, thanks all! Just as a note... I had to use llvm-ld during the link step because gfortran could not link bitcode. Here's an example of the error shown when using gfortran instead of llvm-ld: $ ${GCC_4_5_0}/bin/gfortran hw.f -c -fplugin=${DRAGONEGG_PLUGIN}/dragonegg.so -o hw.o -flto -emit-llvm -S $ ${LLVM_2_9}/bin/opt -mem2reg hw.o

I see. And what's the purpose for outputting bitcode into *.o and *.a files? Do you want to perform an LLVM pass on linking step? 2011/9/13 Ashay Rane <ashay.rane at tacc.utexas.edu>: > Hmm.. I didn't explain the problem completely last time. I am creating a > drop-in replacement for gcc and gfortran that runs an additional pass on the > bitcode before generating the native

Sorry, at what step do you need archive? llc emits binary, it does not perform any linking, thus it does not need anything except the input bytecode file. Then during linking you can link whatever archives of binaries you want. 2011/9/13 Ashay Rane <ashay.rane at tacc.utexas.edu>: > Thats correct. But using llc becomes a problem when I have archives (.a > files). I could, in theory,

Running R version 2.13.1 under Ubuntu 10.10 (kernel version 2.6.35-30-generic) on a x86-64 laptop with gfortran 4.4, I'm trying to install and use the FEAR package from http://www.clemson.edu/economics/faculty/wilson/Software/FEAR/fear.html. I downloaded the the FEAR 1.15 package for 64-bit Linux (compatible with R-2.12.0 compiled with GCC, GNU Fortran 4.1.2, Linux kernel 2.6.16.60 SMP) to the

No, I am running the LLVM pass at the compilation step. So by the time I reach the link step, the transformed bitcode has been generated. Ashay On Mon, Sep 12, 2011 at 4:12 PM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote: > I see. And what's the purpose for outputting bitcode into *.o and *.a > files? Do you want to perform an LLVM pass on linking step? > > 2011/9/13

Thats correct. But using llc becomes a problem when I have archives (.a files). I could, in theory, extract its contents to a tempdir and then use llc and link but just wondering if there is a more elegant solution. Ashay On Mon, Sep 12, 2011 at 3:00 PM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote: > Ashay, > > If I understand correctly, in hw.o you would have llvm

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:

Hmm.. I didn't explain the problem completely last time. I am creating a drop-in replacement for gcc and gfortran that runs an additional pass on the bitcode before generating the native binary. Here's whats happening: If the source code compilation process builds a static library (.a archive file), I need a means to link the `.a' file statically into the application. So if the

I've built R-3.4.3 on HP-UX 11.31 with GCC-4.9.2.? However, it segfaults frequently, and I can't clearly understand why. Some things work, like > 1+2 [1] 3 > sum(c(1,2)) [1] 3 > var(c(1,2,3)) [1] 1 Some don't: > pgamma(1,Inf,Inf) *** caught segfault *** address d0650000, cause 'invalid permissions' Traceback: 1: pgamma(1, Inf, Inf) Possible actions: 1: abort