similar to: [LLVMdev] [cfe-commits] r157260 - in /cfe/trunk: include/clang/Rewrite/Rewriter.h lib/Rewrite/Rewriter.cpp unittests/CMakeLists.txt unittests/Tooling/RewriterTest.cpp unittests/Tooling/RewriterTestContext.h

I get the following problem building LLVM 2.7 on AIX 6: gmake[1]: Entering directory `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' llvm[1]: Compiling Path.cpp for Release build In file included from Path.cpp:262: Unix/Path.inc: In static member function 'static llvm::sys::Path llvm::sys::Path::GetTemporaryDirectory(std::string*)': Unix/Path.inc:142: error: 'mkdtemp' was

Reid Spencer wrote: > Folks, > > With some MacOS help from Nate, I've begun the conversion of LLVM to use > lib/System, the operating system independence layer. FYI, I'm getting this on an up-to-date tree: Compiling Path.cpp In file included from platform/Path.cpp:20, from Path.cpp:37: platform/../Unix/Path.cpp: In static member function `static

/lib/System/platform/Path.cpp is not compilable under Cygwin (although it was motivated to be for Cygwin...): ----------------------------------- Compiling Path.cpp In file included from Path.cpp:37: platform/Path.cpp: In static member function `static llvm::sys::Path llvm::sys::Path::GetTemporaryDirectory()': platform/Path.cpp:41: error: `mkdtemp' undeclared (first use this function)

You can use llvm::sys::Path::GetTemporaryDirectory() and put the inputs and outputs there. Reid On Wed, Jul 7, 2010 at 4:23 PM, Guoliang Jin <jingl1345 at gmail.com> wrote: >  Hi, > > I want to pass parameter to a analysis pass. My pass need to use some > result from some other tools. I can hard code a file name into my pass, > and let my pass read input there, but what if I

On Aug 22, 2010, at 3:38 PM, Patrick Simmons wrote: > I get the following problem building LLVM 2.7 on AIX 6: > > gmake[1]: Entering directory > `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' > llvm[1]: Compiling Path.cpp for Release build > In file included from Path.cpp:262: > Unix/Path.inc: In static member function 'static llvm::sys::Path >

Dear Patrick, Documentation on some AIX routines to do the same thing can be found at http://publib.boulder.ibm.com/infocenter/comphelp/v8v101/index.jsp?topic=/com.ibm.xlcpp8a.doc/proguide/ref/dynamic_load.htm. Interestingly enough, the same page suggests that AIX does, in fact, support dlopen() and friends for POSIX compatibility. You might need to find out if there's a header file or a

Hi, I want to pass parameter to a analysis pass. My pass need to use some result from some other tools. I can hard code a file name into my pass, and let my pass read input there, but what if I do not want the file name to be hard coded? Is it possible to do that? If yes, where can I find some documentation about it? Thanks, Guoliang

On Mon, 4 Jun 2012 08:15:09 +0900 NAKAMURA Takumi <geek4civic at gmail.com> wrote: > 012/6/3 Hal Finkel <hfinkel at anl.gov>: > >> Author: chapuni > >> Date: Sat Jun  2 10:34:26 2012 > >> New Revision: 157890 > >> > >> URL: http://llvm.org/viewvc/llvm-project?rev=157890&view=rev > >> Log: > >> Revert r157819,

012/6/3 Hal Finkel <hfinkel at anl.gov>: >> Author: chapuni >> Date: Sat Jun  2 10:34:26 2012 >> New Revision: 157890 >> >> URL: http://llvm.org/viewvc/llvm-project?rev=157890&view=rev >> Log: >> Revert r157819, "#ifdef out a broken test on win32" >> >> FYI, LLVM_ON_WIN32 is useless. > > Can you be more specific? I

Folks, With some MacOS help from Nate, I've begun the conversion of LLVM to use lib/System, the operating system independence layer. Currently, the library has implementations for three abstractions: Path, Program, and Signals. These provide some basic utilities for manipulating file system paths, finding and executing programs, and cleaning up after Signals. The implementations should work

Thanks for noting it. I'll see what cygwin has to offer in this area and correct the implementation. Thanks, Reid. On Wed, 2004-09-01 at 09:11, Valery A.Khamenya wrote: > /lib/System/platform/Path.cpp is not compilable under Cygwin > (although it was motivated to be for Cygwin...): > ----------------------------------- > Compiling Path.cpp > In file included from

If you think a commandline option is the way to go, LLVM makes it pretty easy to do so, see the documentation here: http://llvm.org/docs/CommandLine.html . Mostly you can just add an appropriate "cl::opt<string>" option (for your filename, for example) and you're on your way. ~Will On Wed, Jul 7, 2010 at 9:55 PM, Reid Kleckner <reid.kleckner at gmail.com> wrote: >

Hi, Just a minor fix to get Path.cpp to compile on Interix. Henrik _________________________________________________________________ Find det, du s�ger med MSN S�g http://search.msn.dk/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Path.cpp.zip Type: application/x-zip-compressed Size: 463 bytes Desc: not available URL:

List, we are working on implementing an antivirus solution (samba-vscan + clamav)on our samba shares. We performed the steps mentioned on some guides we found in Portuguese and things seems to be installed ok. But when we make a test and try to access a share, every file on it is not accessible (though we can mount the share) and after looking at /var/log/messages we see the following: ... Mar 11

I did not report this first error earlier as I thought it trivial. Basically it looks like something odd is happening with the configuration and 'include/llvm/config/config.h' Getting this error on building the tools on a fresh Cygwin install and update :- $ make tools-only make[1]: Entering directory `/usr/build/llvm/lib/System' llvm[1]: Compiling Path.cpp for Debug build In file

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

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > > ..... >> From the existence of the dependency-tracker scripts, it obviously was >> a problem for autoconf as well. >> > > This seems a different issue, but are those dependency-tracker scripts > for tracking dependencies among cpp files and its headers? CMake gives >

Like the title says, the CMakeLists.txt does not contain the current information. Attached is a patch to fix it. - Thanks, Jeff Kunkel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101220/285746bf/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name:

I've been experimenting with building various llvm variants on mac OS X. Ususally, it's a case of cloning, running cmake with Xcode as generator and loading the resulting xcodeproj. In trying to build the skeleton openrisc backend from https://github.com/asl/llvm-openrisc as described in "building a backend in 24 hours" at

Kenneth Boyd <zaimoni at zaimoni.com> writes: >> 1) either CMake becomes the de facto standard for LLVM, deprecating >> autoconf&&gmake and thus requiring the developers to update the >> CMakeLists.txt files to compile their sources... >> > Sorry, but this is a noticeable obstacle for CMake becoming the de-facto > standard for LLVM. Writing a new