search for: error_categori

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

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

On Jun 16, 2012, at 3:51 PM, Chris Lattner wrote: > On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote: > >> In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not readable) or file may be malformed. We are also using C++11 in lld, so we use std::unique_ptr for managing

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

I couldn't get it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote: > LLVM on a Developer Command Prompt. The ones I want to fix first are the > ones from Boost and Jinja2Cpp. I saw some from those as well. > > If there any standard library ones missing, could it be

On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote: > In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not readable) or file may be malformed. We are also using C++11 in lld, so we use std::unique_ptr for managing object ownership. > > The Reader class currently has an

So how do I get it to build libcxx and libcxxabi? I got it from the mono repo and enabled lld, clang, libcxx and libcxxabi. But I built the two main CMake targets only--all_build and install. What else do I have to do? Please let me know. ________________________________ From: Zachary Turner <zturner at google.com> Sent: Wednesday, December 12, 2018 11:10 AM To: blubee blubeeme Cc: Osman

On Mon, Jun 18, 2012 at 1:22 PM, Nick Kledzik <kledzik at apple.com> wrote: > On Jun 16, 2012, at 3:51 PM, Chris Lattner wrote: >> On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote: >> >>> In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s).  But in doing so, there could be I/O errors (file not readable)

How can I tell CMake during the configuration step where to find my zlib installation? ________________________________ From: blubee blubeeme <gurenchan at gmail.com> Sent: Wednesday, December 12, 2018 7:31 PM To: Osman Zakir Cc: llvm-dev Subject: Re: [llvm-dev] Using LLD to link against third-party libraries? How? I would agree with the next email from Brian Cain If you do not have

On Jun 18, 2012, at 1:22 PM, Nick Kledzik wrote: >>> But this interface has become awkward to use. There are two "return" values. This method is a unique_ptr "source" but the use of a by-refernce parameter means you have to start with an uninitialized unique_ptr and the readFile() has to std::move() into it. unique_ptr is much nicer to use as a return value.

I already mentioned what flag I tried. It's in the first email in this thread. And I want to link against Boost.System and the Jinja2Cpp library (the latter's documentation can be found here: https://github.com/flexferrum/Jinja2Cpp . And I also have some GUI applications using FLTK as well that I want to try to build using LLVM as well, so I'll have to know how to link against

I need them so I can build stuff using clang or clang-cl with its C++ standard libraries. To make sure that lld-link won't give errors about missing symbols from any standard libraries. By the way, you wouldn't happen to know how to use link.exe, would you? I might need some help on that to understand how to use lld-link.exe. ________________________________ From: Zachary Turner

In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not readable) or file may be malformed. We are also using C++11 in lld, so we use std::unique_ptr for managing object ownership. The Reader class currently has an interface that can be simplified down to: virtual error_code

On Jun 18, 2012 1:24 PM, "Nick Kledzik" <kledzik at apple.com> wrote: > > On Jun 16, 2012, at 3:51 PM, Chris Lattner wrote: > > On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote: > > > >> In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not

On Jun 18, 2012, at 4:36 PM, Michael Spencer wrote: >>>> >>>> In asking around for clean models on how to do this better, I've heard two interesting ideas: >>>> >>>> 1) Incorporate the error_code and string message into the File class. That is the factory method always returns a File object. But there is a method on File objects to query if

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>