similar to: [LLVMdev] IMPORTANT: Executables Built In New Location

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

I found use old BUILD_OBJ_ROOT/BUILD_SRC_ROOT in comment in llvm/Makefile.common and in llvm/projects/Stacker/test/Makefile code. I update it to PROJ_* in attached patches. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.common.patch Type: application/octet-stream Size: 1081 bytes Desc: not available URL:

My final foray into the makefiles for a while has been completed. The dist-check target is the golden nugget I was hoping to get out of automake. But, now LLVM Makefiles have it too. dist-check does the following: * builds everything with "check" to ensure the source of the distribution is sane, essentially "make check". * builds the distribution tar balls with

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

I have committed changes to Makefile.rules (and others) that will assist in building releases or distributions. The new "dist" target will first perform a "make check" to ensure that all the software builds and that basic sanity checks pass (none have been implemented). If that succeeds, then the directory structure is traversed again for the "distdir" target which

Is there a way to get the following to work under WINE? (i.e. to get two executables to share global memory as they do under windows) We have a DLL that is at a specified memory location. At the top of the code a variable is declared as follows: #pragma data_seg( "global_mem" ) #pragma bss_seg( "global_mem" ) unsigned uAttachmentCount = 0; Now.. The main program links

Hi, I wonder if someone could help. I needed to transfer (copy) a workspace file that had been generated in linux (R 2.11) to windows running the same version of R 2.11 (but of course windows binary). Usually, there is no problem in doing this and all objects work as expected. I am often doing this to be able to produce wmf or emf graphic files that I need. This time I had some spectra that I

hi, when i change the OBJ_ROOT and recompile the llvm, it's successful. but run following test, then the error occues: ----------------------------------------------------- [yue at RH9 obj]$ make -C ./test/Programs make: Entering directory `/home/yue/llvm/obj/test/Programs' make[1]: Entering directory `/home/yue/llvm/obj/test/Programs/SingleSource' make[2]: Entering directory

Hi Reid, just a quick note while you're doing this, a while ago I ran into a problem that the standard makefiles weren't building libraries (like, say, a new pass) correctly on OS X - they were being built as shared libraries and not bundles, so they couldn't be loaded with dlopen. The discussion is in the archives if you want more details... I fixed it locally by doing the following

Hello all, first of all congratulation to all the wine stuff for the great job. I was trying to run some old 16 bit executables using wine (darwine) for mac, but from what i understand darwine is still not able to execute those exe. On Linux, doing wine TASM.EXE works fine, under mac, typing the same command (but using darwine) i get fixme:module:wine_load_dos_exe DOS executables not

Reid, >As for Interix support in general, I'm having a hard time determining >which variant of Unix Interix implements. It seems to be partially Posix >1 and partially Posix 2 based. Do you have any further information >related to the specific standards supported by Interix? I don't want to >incorrectly categorize the Interix support. I've discussed this subject with

Jeff & others A couple words on how lib/System works that might help you. 1. The configure script identifies the build host and puts it in the $build variable. We use that to determine the basic kind of platform and put it in a variable named $OS. The value of $OS can be: Linux, FreeBSD, Interix, SunOS, Darwin, etc. 2. The platform name is used to create a link from

Hello, I've closed PR106 (use automake) as WONTFIX. I've already delineated the problems with automake in previous posts but as of now, all the automake related stuff has been removed from the repository. In an effort to start making our makefile system better, I've committed changes to Makefile.rules and a few library Makefiles that nearly double the speed of our compilations. I

Hi, I've got a Samba server here that runs great! I've got an NT machine on my laptop and I can interface with the Samba server directly in any way I want, except for one thing: When I try to install a program (Visio) as a network shared app, the installation always tells me "I've determined that the target drive doesn't support long file names" after I choose to

Why not put all this into a pre-commit filter in CVS and be done with it? We'd never be bothered with it again as it would never be committed again. Reid. On Thu, 2005-04-21 at 15:11 -0500, Misha Brukman wrote: > Dear LLVMers, > > If you live on the bleeding edge (i.e. CVS version), please read! > > On Wed, Apr 20, 2005 at 12:12:54PM +0200, Markus F.X.J. Oberhumer wrote:

> > I'm truely sorry to bother your group. But I don't know if this is a bug or > not. I've tried to find help on the samba news group and on the IRC to no > avail. I've also have the Samba book by John D. Blair. I've attached my > smb.conf file. I have full access to the share (read/write/execute). But for > some reason, when I try to run certain

Hi all, I'm running Samba 1.9.18p7 and I'm having a problem where I can't execute a file on the samba drive, but if I copy it to a local drive, it works. The client is Windows NT Workstation 4.0 w/ service pack 3. The executable is named Netscape405.exe. The error I get in explorer is: Can not find F:\Netscape405.exe. Windows needs this to run F:\Netscape405.exe I find that if

Hi List, I get an error message "compiler cannot create executables" when I try to install a package. Searching the list archives reveals many messages with the same error message. The advice is generally to install g++ and development libraries. However, I have g++ installed and can compile and run programs as myself and via sudo. I got the library to install by using %sudo R

Hi, I'm looking for a way to make executable R-scripts -- which are bound to a certain package -- available to the operating system's search path. The executable R-scripts I put in the package's 'exec' directory. Different solutions have come to my mind: o 'configure'-script copies the files to /usr/local/bin o make a 'require'-shell function which