similar to: LLVM October Status Update

Displaying 20 results from an estimated 1000 matches similar to: "LLVM October Status Update"

2005 Nov 07
0
[LLVMdev] LLVM 1.6 Release Branch
>> Everything builds fine on sparc. The configure script needs to be fixed >> though (see previous email). > > I'm not getting the error with the configure script (on Kain, anyway). I've > tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my > $PATH. I get the error with and without the --with-f2c option. I never used the NAG Fotran
2005 Nov 07
4
[LLVMdev] LLVM 1.6 Release Branch
Tanya Lattner wrote: > > Everything builds fine on sparc. The configure script needs to be fixed > though (see previous email). I'm not getting the error with the configure script (on Kain, anyway). I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my $PATH. Can you verify that the configure script works for you without the --with-f2c option?
2005 Nov 07
1
[LLVMdev] LLVM 1.6 Release Branch
Tanya Lattner wrote: > >>> Everything builds fine on sparc. The configure script needs to be >>> fixed though (see previous email). >> >> >> I'm not getting the error with the configure script (on Kain, anyway). >> I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in >> and out of my $PATH. > > > I get the
2010 Nov 06
1
Hashing and environments
Hi, I'm trying to write a general-purpose "lexicon" class and associated methods for storing and accessing information about large numbers of specific words (e.g., their frequencies in different genres). Crucial to making such a class practically useful is to get hashing working correctly so that information about specific words can be accessed quickly. But I've never really
2010 May 12
6
dynamic searchable fields, best practice?
I have a Lexicon model, and I want user to be able to create dynamic feature to every lexicon. And I have a complicate search interface that let user search on every single feature (including the dynamic ones) belonged to Lexicon model. I could have used a serialized text field to save all the dynamic information if they are not for searching. In case I want to let user search on all fields, I
2004 Aug 29
1
Re: [R] R on gentoo amd64 (gcc 3.3.3) is unstable --- no!
Dear Dirk, I have had the exactly same problem like Ivo and his solution worked for me. Hence the USE=f77 flag is NOT a typo but a Gentoo quirk. As far as modifying the configure script is concerned, I believe that it is certainly possible to perform said check (if 'f77 --version == f2c' then die) only on x86_64 platforms. And I'd argue it is f2c's fault. AMD64 linux distros have
2004 Aug 29
1
Re: [R] R on gentoo amd64 (gcc 3.3.3) is unstable --- no!
My appologies, this estimation is about right, I spent last week at COMPSTAT in prague and didn't follow the list closely. Inspite of this fact I believe my posting is not entirely out of date. regards Diman Todorov ------------------------------ You are 8 days behind the times -- take a look at the current R-devel. On Sun, 29 Aug 2004, Diman Todorov wrote: > Dear Dirk, > I
2000 Jun 28
1
R-1.1.0 - f2c in configure
When trying to build R-1.1.0, the configure script reported no Fortran compiler, even though '/usr/bin/f2c' was present, and R-1.0.1 had found and successfully used this. I traced this to an apparent typo in line 2067 of configure: for name in g77 fort77 f77 f90 xlf cf77 fc; do changing this to: for name in g77 fort77 f77 f90 xlf cf77 f2c; do allowed the script to 'find'
1998 Feb 25
1
R-beta: Re: dse+redhat 4.2 problem
>R INSTALL dse rlibs >Installing package `dse' ... >libs >gcc -g -fpic -I/usr/local/R-0.61/include -c dsefor.c -o dsefor.o >/tmp/cca02533.i:1: numeric constant with no digits >/tmp/cca02533.i:1: numeric constant with no digits >... >is there something wrong with my gcc or is there some >option missing somewhere? >I suspect the problem might have to do with
1998 Feb 25
1
R-beta: Re: dse+redhat 4.2 problem
>R INSTALL dse rlibs >Installing package `dse' ... >libs >gcc -g -fpic -I/usr/local/R-0.61/include -c dsefor.c -o dsefor.o >/tmp/cca02533.i:1: numeric constant with no digits >/tmp/cca02533.i:1: numeric constant with no digits >... >is there something wrong with my gcc or is there some >option missing somewhere? >I suspect the problem might have to do with
2008 Jan 21
1
R configuration is not finding the installed f2c cross-compiler
Last Friday my computer monitor was messed up by on-line patches update. I had to reinstall everything from the o.s. and all applications on top of it. I have downloaded R source from the official site. I have uncompressed the archive and ran the configure as root in /usr/local/bin. The configuration procedure dies writing: *configure: error: Neither an F77 compiler nor f2c found * but actually
2004 Aug 21
1
Re: [R] R on gentoo amd64 (gcc 3.3.3) is unstable --- no!
On Sat, 21 Aug 2004 ivo_welch-rstat8783@mailblocks.com wrote: > > peter/brian: thank you for the help. i can now report that gentoo > amd64 can compile R just fine, too; it requires the f77 USE flag and a > gcc compiler rebuild first, though. I also went to gcc 3.4.1. my > segfault troubles earlier were caused by my use of f2c. > > suggestion: would it be possible to
2001 Jul 09
0
ODP: Re: How to build R-1.3.0 under HP-UX 11.00
Thank you for advice. I my case RPC nedd to be linked with libnsl, so I used "-lnsl" option to link it, but i have still problem: /usr/bin/ld: Unsatisfied symbols: i_len (code) d_sign (code) collect2: ld returned 1 exit status Can you suggest something? Kris
2005 Nov 07
0
[LLVMdev] LLVM 1.6 Release Branch
Everything builds fine on sparc. The configure script needs to be fixed though (see previous email). Sparc testing results: make check: # of expected passes 1189 # of expected failures 34 Regressions Single Source: None New Failures Single Source (new tests): 2005-05-12-Int64ToFP: llc,jit Regressions MultiSource: Applications/d/make_dparser: llc, cbe, jit
2006 Feb 04
1
RUnit - need advice on a good directory structure or tips...
I made my own RUnit testing convention, and I want to introduce this to one of my friends. Before that, I'd like to review my codes. The problem that I met when I tried to polish my codes is: How can I get the file path in the file??? I.e., I want to get the path to the file that I'm writing using some magic R functions. But I couldn't find any good magic. Is there any magic? So, I
1997 Aug 04
1
R-alpha: Re: your mail
>>>>> Thomas Lumley writes: > On Fri, 1 Aug 1997, Kurt Hornik wrote: >> Thomas, >> >> Could you add the "-lf2c" at the end of the line >> @$(LD) $(SHLIBLDFLAGS) -o $(LIBNAME).so $(OBJS) >> in acepack's src-c/Makefile? >> >> I ran across an identical pow_dd problem recently with another package. >> Did we always need
1997 Aug 21
0
R-alpha: f2c
> If we don't assume that everyone has f2c then people distributing > libraries need to distribute all or part of libf2c. Source to libf2c is > readily available. I'm a bit confused about this discussion, but since I don't have f2c on the computer I've been using the past week, I assume most of the necessary parts on this library have been distributed with R (but I
2005 Nov 07
1
[LLVMdev] LLVM 1.6 Release Branch
Chris Lattner wrote: > On Mon, 7 Nov 2005, John Criswell wrote: > >> Tanya Lattner wrote: >> >>> Everything builds fine on sparc. The configure script needs to be >>> fixed though (see previous email). >> >> >> I'm not getting the error with the configure script (on Kain, anyway). >> I've tried it with --with-f2c and with f96
2006 Jan 27
1
R compile on AIX 5.2
Fellow R Enthusiasts.. I'm trying to compile R on AIX 5.2 32bit with gcc 3.3.2-5. I've tried both the development bundle R-devel_2006-01-25.tar.gz and the R-beta.tar.gz from about a month ago. In each instance, I'm using the following options prior to running "./configure --prefix=/usr/local/R": OBJECT_MODE=32 MAIN_LDFLAGS=-Wl,-brtl SHLIB_LDFLAGS=-Wl,-G
2006 Jan 27
1
R compile on AIX 5.2
Fellow R Enthusiasts.. I'm trying to compile R on AIX 5.2 32bit with gcc 3.3.2-5. I've tried both the development bundle R-devel_2006-01-25.tar.gz and the R-beta.tar.gz from about a month ago. In each instance, I'm using the following options prior to running "./configure --prefix=/usr/local/R": OBJECT_MODE=32 MAIN_LDFLAGS=-Wl,-brtl SHLIB_LDFLAGS=-Wl,-G