search for: libnames

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

gccld would barf if you tried to specify the full pathname of an archive on the command line to gcc, (e.g., instead of gcc ... -L/full/path/to -lFOO you say gcc ... /full/path/to/libFOO.a) which many GNU Makefiles try to do. This patch fixes that. Ok to commit? -- gaeke at uiuc.edu gccld.cpp: Fix typo in header. Add IsArchive static method. Roll LoadLibraryFromDirectory() into

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

Anton, Thanks for your comment. 2nd patch attached. - s/SharedDir/SharedLibDir/g - move prefix=cyg sunk into if(cygwin or mingw) arigato gozaimasu...Takumi * Additional issues - You may build LLVMHello.dll but I don't modify lib/Transforms/Makefile. Because making LLVMHello.dll requires the library LLVM.dll, but it oughta be on the way to making libs at building

Hello friends, in SAS there is the 'libname' source. You associate a way.. ex: ab .. "C:\My Paste\Works" and when u do data ab.example; (...) run; you are saving the archive "example" in a SAS format, and you can see C:\My Paste\Works\example "growing" ("example"'s size:200MB... refresh.. 500MB.. refresh.. 1.2GB...) >How can I do

Hello, I am a total beginner with ?R? and found a package ?venn? to create a venn diagram. The problem is, I cannot create the vectors required for the diagram. The manual say: "R> venn(accession, libname, main = "All samples") where accession was a vector containing the codes identifying the RNA sequences, and libname was a vector containing the codes identifying the

On OpenBSD we still use the "classic" SunOS 4 shared library versioning scheme where the major and minor number are part of the library name (and recorded in DT_NEEDED entries). For example the shared libc on the OpenBSD-current is named libc.so.89.2. With this scheme, linker has to pick the pick the library with the highest major and minor (within the highest major version); the

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

Hi Mark, If we have to do this, or LLD doesn't work on OpenBSD, I think we need to do this. But can I ask one question? I wonder why OpenBSD systems don't have symbolic links unlike the other Unix-like systems in the first place. On Mon, Dec 19, 2016 at 2:27 PM, Mark Kettenis via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On OpenBSD we still use the "classic"

I'm forwarding this bug resolution because it has a pretty wide impact on LLVM developers. This bug (451) has been resolved (well, works for me anyway). If you have reconfigured your build tree since October 4th, you need to reconfigure again. The bug produced shared objects that don't have a .so extension. Reconfiguring will fix this problem. The notes below show what was needed to

I'm trying to read in a sas system file (.sas7bdat) created under SAS 8.2 using read.ssd as follows: > library(foreign) > libname <- "c:/sasuser/consult/" > sascmd <- "c:/Program\ Files/SAS\ Institute/SAS/V8/sas.exe" > subset <- read.ssd(libname, "subset", sascmd=sascmd) SAS failed. SAS program at c:\windows\TEMP\Rtmp6673\file24544.sas a

The Details. In the following version. > version _ platform i386-pc-linux-gnu arch i386 os linux-gnu system i386, linux-gnu status major 1 minor 8.1 year 2003 month 11 day 21 language R > lookup.xport ignores some datasets in sas export file. File "emptySasData3.xpt" (available at http://biostat.mc.vanderbilt.edu/tmp/emptySasData3.xpt) is a

I am attempting to read in a SAS 9.1 data file. After starting R I change to the directory containing the sas data file and use the "dir" command to confirm that it is there. Then I run the following R-code: library(foreign) sashome <- "/Program Files/SAS/SAS 9.1" test<-read.ssd(file.path(sashome), "pcb", sascmd = file.path(sashome,

Hello, I'm trying to import a SAS file made using SAS on Unix. Currently I'm using SAS on Windows and I'm trying to import that .ssd04 file to R. The file name of the file is testfile.ssd04 and it is located in 'M:\sasuser'. I'm using Windows XP and R 2.91. Basically what I'm doing is ############ r code ############## > library(foreign) > sashome <-

Hi All, I've been working on updating the 'genetics' package. As a consequence of the upgrade, .First.lib() looks like: .First.lib <- function(libname, pkgname) { if (!require(combinat)) warning("Unable to load 'combinat' library. Function `diseq.ci' will fail.") require(gregmisc) genotype <-

Hi, I am trying to read a SAS version 9.1.3 SAS dataset into R (to preserve the SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc

Dear all, My apologies for re-posting this question, but I have not found any solution to my problem so far. I also think that my post may have been overseen due to the posting time and high traffic on this list. I experience a problem in implementing a S4 class in a package and would appreciate your help in this matter. The class is implemented using Rcpp, which works well. I then extend

Hi I'm trying to read SAS-data on VAX/VMS to Windows R using foreign pakage read.xport and experience some problems. Following lines are used in SAS to create XPORT file LIBNAME a ''xxx; LIBNAME b XPORT ''; PROC COPY IN=a OUT=b; RUN; and I succeed in getting file that looks like correct xport file.However when typing in R following

Scot, Thanks for the info. I will try your code out to verify the result, but before I do that, will your code (SAS and R) work with variable names that are longer than 8 characters long without truncating the variable name in R? Also, I wonder about using your method or the PROC EXPORT method with larger data sets. The data sets I will be working with for the most part will not be that large,