Displaying 20 results from an estimated 4000 matches similar to: "Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15"
2016 May 24
0
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
Kevin Enderby added those symbol uses in r270491. It has a cmake
feature test, and all the uses of those symbols appear bracketed in
HAVE_LIBXAR, so I don't know what went wrong for you.
On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in
> current trunk?
>
> [
2016 May 24
2
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote:
> Kevin Enderby added those symbol uses in r270491. It has a cmake
> feature test, and all the uses of those symbols appear bracketed in
> HAVE_LIBXAR, so I don't know what went wrong for you.
The trigger for this build failure is the usage of
-DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that
2016 May 24
0
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 1:22 PM, Jack Howarth
<howarth.mailing.lists at gmail.com> wrote:
> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote:
>> Kevin Enderby added those symbol uses in r270491. It has a cmake
>> feature test, and all the uses of those symbols appear bracketed in
>> HAVE_LIBXAR, so I don't know what went wrong for you.
2016 May 24
2
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 1:24 PM, Jack Howarth
<howarth.mailing.lists at gmail.com> wrote:
> On Tue, May 24, 2016 at 1:22 PM, Jack Howarth
> <howarth.mailing.lists at gmail.com> wrote:
>> On Tue, May 24, 2016 at 12:08 PM, Reid Kleckner <rnk at google.com> wrote:
>>> Kevin Enderby added those symbol uses in r270491. It has a cmake
>>> feature test, and
2016 May 24
0
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
Hi Jack,
Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via:
#ifdef HAVE_LIBXAR
extern "C" {
#include <xar/xar.h>
}
#endif
I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this.
Kev
> On May 24, 2016, at
2016 May 24
0
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
Jack,
What version of CMake are you using?
-Chris
> On May 24, 2016, at 11:00 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote:
>
> On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote:
>> Hi Jack,
>>
>> Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not
2016 May 24
2
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 1:35 PM, Kevin Enderby <enderby at apple.com> wrote:
> Hi Jack,
>
> Just a guess here, this may be the bug Chris helped me out with in the use of the include file xar/xar.h which is not C++ safe. I needed to wrap my include via:
>
> #ifdef HAVE_LIBXAR
> extern "C" {
> #include <xar/xar.h>
> }
> #endif
>
> I think we
2016 May 24
1
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 3:03 PM, Jack Howarth
<howarth.mailing.lists at gmail.com> wrote:
> On Tue, May 24, 2016 at 2:37 PM, Jack Howarth
> <howarth.mailing.lists at gmail.com> wrote:
>> On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote:
>>> Jack,
>>>
>>> What version of CMake are you using?
>>>
>>>
2016 May 24
0
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 2:37 PM, Jack Howarth
<howarth.mailing.lists at gmail.com> wrote:
> On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote:
>> Jack,
>>
>> What version of CMake are you using?
>>
>> -Chris
>
> Chris,
> I am using cmake 3.5.2. My read of this problem is as follows.
> While libLLVM.dylib is
2016 May 24
2
Undefined symbols in llvm-objdump linkage on x86_64-apple-darwin15
On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote:
> Jack,
>
> What version of CMake are you using?
>
> -Chris
Chris,
I am using cmake 3.5.2. My read of this problem is as follows.
While libLLVM.dylib is being linked against -lxar when
-DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib
is created with -Wl,-dead_strip such that
2018 Sep 21
2
msan test failures
I'm seeing some test failures for unit tests for msan (check-msan)
happening in googletest, which I find weird. I'm on Arch Linux, with
r342711. Below is one type of error that I see. The full log is 416MB (!)
big. My guess is that those errors are related, but if anyone needs the
full log, I'll provide it. Here is a reduced log from the end:
2008 Dec 05
0
[LLVMdev] Build errors on trunk for about a week now.
On Fri, Dec 5, 2008 at 1:57 PM, OvermindDL1 <overminddl1 at gmail.com> wrote:
> On Fri, Dec 5, 2008 at 1:52 PM, OvermindDL1 <overminddl1 at gmail.com> wrote:
>> / * snip */
>
> Actually, rebuilding it makes "debug tblgen" fail with the errors at
> the end of this email, and as such everything that depends on it, how
> odd...
> When I get back to that
2016 Mar 02
2
EH failures in MCJIT
After re-cmaking and rebuilding everything from scratch, I'm seeing
failures in MCJIT. It this something known or expected? I build
LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++".
Example failure:
/w/bld/org/./bin/lli -remote-mcjit
-mcjit-remote-process=/w/bld/org/./bin/lli-child-target
/w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll
--
Exit Code:
2007 Feb 22
2
[LLVMdev] opt -verify
I am writing an interprocedural compiler pass. Because the passneeds
information from a FunctionPass, e.g., the post-dominance frontier
(PDF), and because a ModulePass is not permitted to require a
FunctionPass, I am forced to make my pass a FunctionPass and do majority
of its work in the doFinalization() method.
When I run "opt -mypass -verify -o code2.bc code1.bc" I get no
2010 May 04
1
errors when installing rjags
Hi,
With the sid package jags (2.0.0-1) and r-base-core (2.11.0-1), I cannot
install package rjags anymore (this used to work at some point; can't
recall exactly at what R/JAGS versions):
---<--------------------cut here---------------start------------------->---
R> install.packages("rjags", configure.args="--with-jags-modules=/usr/lib/JAGS/modules-2.0.0")
2007 Feb 23
2
[LLVMdev] bytecode reader assertion failure
I have a compiler transform that I have been working on that produces
bytecode that passes the verifier. However, when I try to read that
bytecode back in, I get the assertion failure below.
llvm::BytecodeReader::ParseConstantPoolValue(unsigned int):
Assertion `(!isa<Constant>(Result) ||
!cast<Constant>(Result)->isNullValue()) || !hasImplicitNull(TypeID) &&
2018 Dec 11
2
Using LLD to link against third-party libraries? How?
In my code here https://github.com/DragonOsman/currency_converter , I used C++17 and managed to get it to work (though I'm only using std::map::insert_or_assign() from C++17). And I'm using Windows, so I shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use them directly on the compiler command line instead. The libraries I need to link against are
2018 Dec 11
3
Using LLD to link against third-party libraries? How?
Are you linking with a C++ compiler? A lot of those missing symbols
look like they come from the C++ standard library.
-David
Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> writes:
> @blubee blubeeme So what do you think? Got any ideas?
> ----------------------------------------------------------------------
> From: Osman Zakir <osmanzakir90
2007 Feb 22
0
[LLVMdev] opt -verify
On Wed, 21 Feb 2007, Ryan M. Lefever wrote:
> I am writing an interprocedural compiler pass. Because the passneeds
> information from a FunctionPass, e.g., the post-dominance frontier
> (PDF), and because a ModulePass is not permitted to require a
> FunctionPass, I am forced to make my pass a FunctionPass and do majority
> of its work in the doFinalization() method.
ok
> When
2007 Feb 22
3
[LLVMdev] opt -verify
I followed what you said and called verifyModule() with the
AbortProcessAction option. verifyModule() returns false, but does not
abort and does not print out any information about what caused the
verification to fail.
Chris Lattner wrote:
> On Wed, 21 Feb 2007, Ryan M. Lefever wrote:
>> I am writing an interprocedural compiler pass. Because the passneeds
>> information from a