similar to: [LLVMdev] Request: Add a LLVM_VERSION define to llvm-c/core.h or llvm/Config/config.h

Signed-off-by: Sedat Dilek <sedat.dilek at gmail.com> --- CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index ed7aeb026f5d..60fe427e456e 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -66,7 +66,7 @@ set(LLVM_VERSION_PATCH 0) set(LLVM_VERSION_SUFFIX svn) if (NOT PACKAGE_VERSION) - set(PACKAGE_VERSION

> Can you answer my question on how to set the version-string correct > when generating tarballs out of the release_38 Git branch? > ( I generated source-tarballs out of my local Git repositories, see below. ) [ llvm.src/CMakeLists.txt ] ... if(NOT DEFINED LLVM_VERSION_MAJOR) set(LLVM_VERSION_MAJOR 3) endif() if(NOT DEFINED LLVM_VERSION_MINOR) set(LLVM_VERSION_MINOR 8) endif() if(NOT

[ Please CC me I ma not subcribed to this mailing-list ] [ CC Tom and Hans as LLVM/stable maintainers ] Hi, I want to understand the version handling in LLVM/Clang/LLD. Normally, I build from "release/10.x" Git branch by using the tool tc-build from ClangBuiltLinux project. With "llvm-10.0.1-rc1" Git tag I was able to setup a llvm-toolchain consisting of the projects

LGTM. -Chris > On Feb 27, 2015, at 3:27 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > Signed-off-by: Sedat Dilek <sedat.dilek at gmail.com> > --- > CMakeLists.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/CMakeLists.txt b/CMakeLists.txt > index ed7aeb026f5d..60fe427e456e 100644 > --- a/CMakeLists.txt > +++

On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/19/2020 09:05 PM, Sedat Dilek wrote: > > Hi Tom, > > > > thanks and congrats for LLVM 10.0.1-rc1 release. > > > > [1] shows 2 assets. > > 10.0.0 RCs had a lot of more assets. > > I am missing the llvm-project-10.0.1rc1.tar.xz tarball. > > > > Will

On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

Hi everyone, I just reported the following issue: https://llvm.org/bugs/show_bug.cgi?id=24927 Using the Xcode 7 linker, one gets messages such as the following when linking objects generated using llvm: ld: warning: object file (foo.o) was built for newer OS X version (14.5) than being linked (10.9) The issue is the following: a) In lib/Support/Unix/Host.inc, sys::getDefaultTargetTriple()

Jeff Bezanson <jeff.bezanson at gmail.com> writes: > LLVM 3.2 came as a nice Christmas present. Just one minor question: I > noticed that the version string (used to name the shared library etc.) > is "3.2svn" instead of the expected "3.2". This violates our build > system's expectations of what things are called. It would be easy for > us to change,

Xerxes Rånby wrote: > Frits van Bommel skrev: >> Benjamin Kramer wrote: >>> The attached patch modifies the llvm build system (both autotools and >>> cmake) to write the revision into PACKAGE_VERSION: >>> >>> $ llvm-config --version >>> 2.6-71981 >>> >> I don't think that's enough for LDC; we want to be able to

On 2009-05-18 20:06, Frits van Bommel wrote: > Xerxes Rånby wrote: > >> Frits van Bommel skrev: >> >>> Benjamin Kramer wrote: >>> >>>> The attached patch modifies the llvm build system (both autotools and >>>> cmake) to write the revision into PACKAGE_VERSION: >>>> >>>> $ llvm-config --version

Frits van Bommel skrev: > Benjamin Kramer wrote: > >> At the moment llvm-config outputs "2.6svn" if llvm is build from trunk >> >> $ llvm-config --version >> 2.6svn >> >> Some external projects (built out-of-tree) need to know which revision >> of llvm is installed. LDC currently asks llvm-config --src-root for the >> source

Just in case someone is having similar problems and/or following this thread, here's my final "solution" (at least, for now). In my bash build script, prior to configure, I set the C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to empty strings, and then set some other environment variables instead: export C_INCLUDE_PATH= export CPLUS_INCLUDE_PATH=

Applied as r79307, thanks On Sat, Aug 15, 2009 at 8:57 AM, José Fonseca<jose.r.fonseca at gmail.com> wrote: > Hi, > > Using a JIT engine on LLVM-C currently fails on SVN because the > LLVMInitialize???Info is never called. > > The attached patch fixes this. > > BTW, would it be possible to include a simple LLVM-C test case, like >

Does the 2.5 release version also fail for this reason? I'm trying to JIT (through LLVM-C) from code generated by my compiler, and it's segfaulting... I'd like to know if this is the problem or if something else is going wrong. On Mon, Aug 17, 2009 at 10:06 PM, Daniel Dunbar<daniel at zuster.org> wrote: > Applied as r79307, thanks > > On Sat, Aug 15, 2009 at 8:57 AM,

On Sun, Jun 26, 2016 at 2:48 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> What you're probably missing is that 3.8.1 is made in release_38 >> branch. So, everything is there and already mirrored. >> >> Source tarballs will be available upon the

--- include/llvm-c/Core.h | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/include/llvm-c/Core.h b/include/llvm-c/Core.h index 3ffaddd..becba7f 100644 --- a/include/llvm-c/Core.h +++ b/include/llvm-c/Core.h @@ -33,6 +33,10 @@ #ifndef LLVM_C_CORE_H #define LLVM_C_CORE_H +#ifndef __STDC_LIMIT_MACROS +#define __STDC_LIMIT_MACROS +#endif + #include

On 02/05/2019 11:26 AM, Michał Górny wrote: > On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: >> On 02/05/2019 08:07 AM, Michał Górny wrote: >>> On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers >>> wrote: >>>> Hi, >>>> >>>> The release_70 branch is ready for the 7.1.0 release. I have updated the

On 03/24/2011 03:30 PM, Jakob Stoklund Olesen wrote: > > On Mar 24, 2011, at 7:23 AM, José Fonseca wrote: >>>> >>> I normally use 403.gcc, but if you don't have SPEC sources, these >>> tests in the nightly test suite take a while to compile: >>> >>> MultiSource/Applications/ClamAV >>> MultiSource/Applications/JM/ldecod

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the

To the mailing list this time... On Sat, Mar 6, 2010 at 4:26 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > On Sat, Mar 6, 2010 at 4:19 PM, José Fonseca <jose.r.fonseca at gmail.com> wrote: >>>> --- a/include/llvm/System/DataTypes.h.cmake >>>> +++ b/include/llvm/System/DataTypes.h.cmake >>>> @@ -100,6 +100,9 @@ typedef u_int64_t uint64_t;