similar to: [LLVMdev] llvm build breakage on OpenBSD after adding system_error

Hi, llvmdev! The diff attached takes the features of OpenBSD binutils into account (which needs --whole-archive) and makes build with ENABLE_SHARED successful. -------------- next part -------------- Index: tools/llvm-shlib/Makefile =================================================================== --- tools/llvm-shlib/Makefile (revision 117443) +++ tools/llvm-shlib/Makefile (working copy) @@

Vladimir, It is as same as freebsd :) See also http://llvm.org/bugs/show_bug.cgi?id=8434 I will commit them fused tomorrow, if no one objects. ...Takumi 2010/10/27 Vladimir Kirillov <proger at uaoug.org.ua>: > Hi, llvmdev! > > The diff attached takes the features of OpenBSD binutils into account > (which needs --whole-archive) and makes build with ENABLE_SHARED >

Hello, llvmdev! I'm using LLVM on OpenBSD. This project proactively advocates usage of 'secure' C apis, especially related to memory bounds checking. Thus using functions like sprintf/strcpy/etc usually spits out a linker warning in base toolchain like this one: /home/proger/dev/llvm/Debug+Asserts/lib/libclangFrontend.a(DocumentXML.o) (.text+0xc65): In function

Hi, I get build errors when trying to build a fresh r139985. Anyone got a clue? carl at carl:~/Downloads/llvm3.0/llvm$ gcc --version gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. carl at

Hi Dean, Wondering if you've seen anything like this: /usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/projects/compiler-rt/lib/xray/tests/unit && /usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/./bin/clang fdr_logging_test.cc.x86_64.o xray_unit_test_main.cc.x86_64.o gtest-all.cc.x86_64.o -o

Committed in r117528, thank you! ...Takumi 2010/10/27 NAKAMURA Takumi <geek4civic at gmail.com>: > Vladimir, > > It is as same as freebsd :) > See also http://llvm.org/bugs/show_bug.cgi?id=8434 > > I will commit them fused tomorrow, if no one objects. > > > ...Takumi > > > 2010/10/27 Vladimir Kirillov <proger at uaoug.org.ua>: >> Hi,

Hi, I am trying to build the LLVM suite on a RedHat Enterprise Linux clone (Scientific Linux <https://www.scientificlinux.org/>). In the latest attempt, the build seems to complete without any explicit failures but the `check-all` process fails. Any ideas about what is wrong or suggestions for how to proceed would be much appreciated. This is the current procedure: sudo yum install

Should I contact the local admin on this? [25/294] Linking CXX executable bin/llvm-itanium-demangle-fuzzer FAILED: bin/llvm-itanium-demangle-fuzzer : && /home/usr4/c74014i/opt/clang/current/bin/clang++ -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers

On Sun, Mar 12, 2017, 4:10 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > > > On 9 Mar 2017, at 09:32, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > I agree that we should clean up the standard library usage even just for > consistency. > > > > +1 -- now that I think about it, it should be fairly doable

Hi! These warnings and errors might be interesting to you when compiling rev. 116572 of llvm and clang on windows: \llvm\utils\killthedoctor\system_error.h(260) : error C2065: 'EAFNOSUPPORT' : undeclared identifier and many similar errors regarding the system error constants. msdn says it's WSAEAFNOSUPPORT instead of EAFNOSUPPORT (prepend WSA... to all system error constants)

On Tue, Mar 14, 2017 at 5:34 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > On 13 Mar 2017, at 15:39, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Sun, Mar 12, 2017, 4:10 PM Dean Michael Berris <dean.berris at gmail.com> > wrote: > > > > On 9 Mar 2017, at 09:32, David Blaikie via llvm-dev < > llvm-dev at

There are several libraries in LLVM that create their own `error_code` categories, so that they can return errors in a consistent way and with convenient messages. To do this, these libraries create an error category type that inherits from `_do_message` in system_error.h. There are a number of ways that this is wrong: 1. From the name, it's quite clear that _do_message is an implementation

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner > Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs() > It would be much better for the linker to return its error in a proper way > (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h does). > The right fix for this is

Michael A. Peters wrote: > For video - I use the totem plugin with xine backend totem. I > compiled > my own but I suspect that rpmforge has it. I found gstreamer backend > totem to be most unsatisfactory. Hi guys, Could you please share some details on how to get totem-xine running on CentOS? I believe this could be interesting to a number of people on the list, not just me.

On Jun 1, 2012, at 3:48 PM, Justin Holewinski wrote: > This isn't the right approach. Nothing in the library part of the compiler should be hard coding a stream to write to. What are you trying to accomplish? > > There are a lot of places where warning/debug information is passed directly to errs(). For example, take the Linker class. You can tell it to omit errors/warnings, but

On 02/25/2014 09:30 AM, Richard Sandiford wrote: > reed kotler <rkotler at mips.com> writes: >> On 02/24/2014 04:42 PM, Eric Christopher wrote: >>> On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at mips.com> wrote: >>>> I need to leave soon and will take a look in the morning. >>>> >>>> I did look at the autoconf input files

this patch removes some redundant includes in llvm-mc.cpp thanks, Jun --- llvm-3.2.src/tools/llvm-mc.org/llvm-mc.cpp +++ llvm-3.2.src/tools/llvm-mc/llvm-mc.cpp @@ -17,7 +17,6 @@ #include "llvm/MC/MCAsmBackend.h" #include "llvm/MC/MCAsmInfo.h" #include "llvm/MC/MCContext.h" -#include "llvm/MC/MCCodeEmitter.h" #include

I see what my problem is here.... I'll continue to move further. Seems like Richards fix is still okay. On 02/25/2014 02:42 PM, Eric Christopher wrote: > On Tue, Feb 25, 2014 at 2:41 PM, reed kotler <rkotler at mips.com> wrote: >> On 02/25/2014 02:38 PM, Eric Christopher wrote: >>> On Tue, Feb 25, 2014 at 2:32 PM, reed kotler <rkotler at mips.com> wrote:

On 02/25/2014 02:38 PM, Eric Christopher wrote: > On Tue, Feb 25, 2014 at 2:32 PM, reed kotler <rkotler at mips.com> wrote: >> On 02/25/2014 09:30 AM, Richard Sandiford wrote: >>> reed kotler <rkotler at mips.com> writes: >>>> On 02/24/2014 04:42 PM, Eric Christopher wrote: >>>>> On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at

On Jun 1, 2012, at 7:08 PM, Caldarale, Charles R wrote: >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner >> Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs() > >> It would be much better for the linker to return its error in a proper way >> (i.e. extending