similar to: [LLVMdev] [PATCH] Fix `clang -print-file-name=include`

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] [PATCH] Fix `clang -print-file-name=include`"

2010 Aug 15
3
[LLVMdev] Linking to the LLVM shared library
The LLVM 2.7 release notes say you can use ./configure --enable-shared to build LLVM as a shared library (libLLVM2.7.so), and the LLVM tools will link against that instead of including the static libraries, so I was wondering: Is there a way to configure LLVM the same way using CMake (so it can work on Windows)? In the other direction, is there an equivalent ./configure flag to setting
2010 Aug 22
2
[LLVMdev] Linking to the LLVM shared library
Óscar Fuentes <ofv at wanadoo.es> wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.comp.compilers.llvm.devel as well. > > nobled <nobled at dreamwidth.org> writes: > >>>> The LLVM 2.7 release notes say you can use ./configure --enable-shared >>>> to build LLVM as a shared library (libLLVM2.7.so), and
2010 Aug 22
0
[LLVMdev] Linking to the LLVM shared library
nobled <nobled at dreamwidth.org> writes: >> AFAIK, the `configure&make' build had so-so support for shared >> libraries. Maybe that is fixed now. What they implemented recently was >> one option for generating a single shared library containing all LLVM. > > Right, that was my original question--when you build libLLVM2.7.so > with --enable-shared,
2010 Aug 22
1
[LLVMdev] Linking to the LLVM shared library
Óscar Fuentes <ofv at wanadoo.es> wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.comp.compilers.llvm.devel as well. > > nobled <nobled at dreamwidth.org> writes: > >> The LLVM 2.7 release notes say you can use ./configure --enable-shared >> to build LLVM as a shared library (libLLVM2.7.so), and the LLVM tools
2010 Aug 04
1
[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types
Óscar Fuentes <ofv at wanadoo.es> wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.comp.compilers.llvm.devel as well. > > nobled <nobled at dreamwidth.org> writes: > > [snip] > > Please move the new code to a new file named > cmake/modules/WindowsCRTControl.cmake and include it from the top level > CMakeLists
2010 Aug 02
2
[LLVMdev] [PATCH] fix "ambiguous call to overloaded function" with Visual Studio 2010
The attached patch gets rid of the "error C2668" mentioned on the wiki page (all the other errors seem to be fixed in SVN already AFAICT): http://wiki.llvm.org/How_do_I_compile_on_Visual_C%2B%2B%3F Applying this to trunk fixes http://llvm.org/bugs/show_bug.cgi?id=5592 for me. -------------- next part -------------- A non-text attachment was scrubbed... Name:
2010 Aug 03
0
[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types
nobled <nobled at dreamwidth.org> writes: [snip] Please move the new code to a new file named cmake/modules/WindowsCRTControl.cmake and include it from the top level CMakeLists when LLVM_ON_WIN32.
2010 Aug 03
2
[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types
Óscar Fuentes <ofv at wanadoo.es> wrote: > I'm a bit wary about this patch. So much complexity for so petty > feature... Maybe the right thing is to determine the scenarios where > people set LLVM_USE_CRT. Maybe all we need is to define another build > type that inherits from Release which uses the debug version of the CRT. > > Anyways, the patch have some issues:
2010 Aug 22
0
[LLVMdev] Linking to the LLVM shared library
nobled <nobled at dreamwidth.org> writes: >>> The LLVM 2.7 release notes say you can use ./configure --enable-shared >>> to build LLVM as a shared library (libLLVM2.7.so), and the LLVM tools >>> will link against that instead of including the static libraries, so I >>> was wondering: >>> >>> Is there a way to configure LLVM the same way
2015 Apr 01
0
Asterisk 13.3.0 compiled with clang on FreeBSD crashes
Hi, I'm maintaining the FreeBSD ports for asterisk(With madpilot at FreeBSD.org as identity). Here's a link to the asterisk13 port for your reference: http://www.freshports.org/net/asterisk13/ I performed some tests with RC1 and am doing some final tests with the final release before committing the update. Up to now the ports forced using gcc, version 4.8 lately, to compile it. And for
2010 Aug 02
1
[LLVMdev] [PATCH] Add 'STRINGS' cache property to LLVM_USE_CRT
This lets CMake's GUI frontend show a drop-down list of the limited possible values for LLVM_USE_CRT, instead of the current freeform input field, so using the variable is less error-prone. -------------- next part -------------- A non-text attachment was scrubbed... Name: add-strings-property-to-msvc-crt.patch Type: text/x-patch Size: 673 bytes Desc: not available URL:
2017 Sep 17
0
FW: CRAN check errors: drake 4.1.0 on r-devel-linux-x86_64-debian-clang
Hello, The CRAN checks for the drake package (4.1.0) fail for r-devel-linux-x86_64-debian-clang. This happened right when crayon 1.3.4 was released, but I suspect the problem is not with crayon or drake, but with base R-devel. I cannot reproduce the error myself, but I have copied a minimal working example (MWE) below that should theoretically isolate the problem. `find_namespaced_functions()`
2010 Aug 02
0
[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types
nobled <nobled at dreamwidth.org> writes: > This patch splits LLVM_USE_CRT into new CMake variables > LLVM_USE_CRT_DEBUG, LLVM_USE_CRT_RELEASE, etc (one for each build > type). It also automatically detects which CRT was already chosen by > CMake's defaults in the CMAKE_CXX_FLAGS_* variables, and defaults to > those values. > > (Before, it was using
2010 Aug 02
2
[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types
This patch splits LLVM_USE_CRT into new CMake variables LLVM_USE_CRT_DEBUG, LLVM_USE_CRT_RELEASE, etc (one for each build type). It also automatically detects which CRT was already chosen by CMake's defaults in the CMAKE_CXX_FLAGS_* variables, and defaults to those values. (Before, it was using add_llvm_definitions(), which worked...somehow, but CMAKE_CXX_FLAGS_RELEASE and friends were still
2017 Jun 05
0
Release 3.12: Scope and calendar!
On 01/06/17 22:47, Shyam wrote: > Hi, > > Here are some top reminders for the 3.12 release: > > 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged > to prepare for the same as per the calendar posted here. > > 2) 3.12 is a long term maintenance (LTM) release, and potentially the > last in the 3.x line of Gluster! > > 3) From this release
2017 Jun 01
3
Release 3.12: Scope and calendar!
Hi, Here are some top reminders for the 3.12 release: 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged to prepare for the same as per the calendar posted here. 2) 3.12 is a long term maintenance (LTM) release, and potentially the last in the 3.x line of Gluster! 3) From this release onward, the feature freeze date is moved ~45 days in advance, before the release.
2010 Oct 06
0
LLVM 2.8 Release!
Hi LLVM Friends, Fans, Followers and Fanatics, LLVM 2.8 is live! You can download it here: http://llvm.org/releases/ and read about it here: http://llvm.org/releases/2.8/docs/ReleaseNotes.html This release includes approximately 6 months of development that provide major enhancements and new features over the LLVM 2.7 release. LLVM 2.8 includes broad improvements in the core LLVM project and
1998 Mar 31
1
Are dashes OK in Domain Name?
I was browsing through the SAMBA workgroups defined here: E51-CAE, E51-WAAS, etc... everything looked fine (well, with the exception of subnet browsing) until I displayed the properties of the machines in the workgroups. Select a SAMBA host, right-click on the hostname and select 'Properties' from an NT4 machine displays the domain as "E51"; everything from the dash onward
2006 Sep 28
3
[Bug 1239] OpenSSL ENGINE support broken on Solaris using Sun Studio compiler
http://bugzilla.mindrot.org/show_bug.cgi?id=1239 Summary: OpenSSL ENGINE support broken on Solaris using Sun Studio compiler Product: Portable OpenSSH Version: 4.4p1 Platform: Other OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo:
2011 Apr 07
0
LLVM 2.9 Release!
Hi LLVM Friends, Fans, Followers and Fanatics, LLVM 2.9 is out, get it while it is fresh and steaming! http://llvm.org/releases/ and read about it here: http://llvm.org/releases/2.9/docs/ReleaseNotes.html This release includes 6 months of development that provide major enhancements and new features over the LLVM 2.8 release. LLVM 2.9 includes much better optimization and code generation than