Displaying 20 results from an estimated 1200 matches similar to: "trunk check-all failing on Linux using compiler-rt and libcxx"
2016 Dec 27
4
Bootstrapping with in-tree libcxx
On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake
<asiri.rathnayake at gmail.com> wrote:
>
>
> On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>>
>> When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that
>> it doesn't try to use the in-tree libcxx but looks for one built
>> and
2016 Dec 27
0
Bootstrapping with in-tree libcxx
On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that
> it doesn't try to use the in-tree libcxx but looks for one built and
> installed
> in the system.
>
IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see [1]) to
the compiler.
What you can
2007 Dec 15
2
[LLVMdev] fix warning with newer g++ compilers
Ok, here is the patch again... I also included fixes for the bits
that originally gave my mailer fits...
Two votes for orange, so I went with orange...
Doing diffs in .:
--- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800
+++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800
@@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char *
Result +=
2007 Dec 15
4
[LLVMdev] fix warning with newer g++ compilers
Newer g++ compilers can emit:
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
function 'int llvm::LLLexer::LexAt()':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp:287:
warning: suggest a space before ';' or explicit braces around empty
body in 'for' statement
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
2015 Jul 08
2
[LLVMdev] [cfe-dev] Building clang + libc++ + libc++abi
If your cut-n-paste is accurate, you seem to be missing a closing quote for
CMAKE_CXX_LINK_FLAGS.
hth...
don
On Jul 8, 2015 2:22 AM, "David A. Greene" <greened at obbligato.org> wrote:
> greened at obbligato.org (David A. Greene) writes:
>
> > I looked at the instructions on the libc++ page and for Linux it
> > recommends building with -stdlib=libc++ -lc++abi.
2016 Dec 29
0
Bootstrapping with in-tree libcxx
On Tue, Dec 27, 2016 at 2:45 PM, Carsten Mattner <carstenmattner at gmail.com>
wrote:
> On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake
> <asiri.rathnayake at gmail.com> wrote:
> >
> >
> > On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> >>
> >> When I tried to build with
2007 Dec 15
2
[LLVMdev] fix warning with newer g++ compilers
On Dec 15, 2007, at 2:13 AM, Duncan Sands wrote:
> Hi,
>
>> - for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr);
>> + for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr) ;
>
> personally I like
>
> for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr) {}
>
> better since it is more explicit.
I think the bikeshed should be orange:
for (++CurPtr; isdigit(CurPtr[0]);
2016 Dec 27
2
Bootstrapping with in-tree libcxx
When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that
it doesn't try to use the in-tree libcxx but looks for one built and installed
in the system.
Since building all of llvm required CXX and using libcxx with the same
version as the rest of llvm makes sense, I would certainly appreciate
an option to build the in-tree libcxx as a first step and use it in when
building llvm, lld,
2016 Dec 28
0
Bootstrapping with in-tree libcxx
If you're willing to install libc++ you can easily work around this by
running `ninja install-cxx install-cxxabi` before running any of the LLVM
or Clang build targets.
/Eric
On Tue, Dec 27, 2016 at 7:45 AM, Carsten Mattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake
> <asiri.rathnayake at gmail.com> wrote:
>
2007 Dec 15
0
[LLVMdev] fix warning with newer g++ compilers
Hi,
> - for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr);
> + for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr) ;
personally I like
for (++CurPtr; isdigit(CurPtr[0]); ++CurPtr) {}
better since it is more explicit.
Ciao,
Duncan.
2000 Dec 11
2
Point in usernames / scp
Hi,
we are using usernames on our systems that contain a point '.', like
"r.john".
We found it necessary to patch the source to make the "scp" command work
with those usernames.
Cheers
Kai
--- openssh-2.2.0p1/scp.c Wed Aug 30 01:11:30 2000
+++ withpoint/scp.c Mon Dec 11 02:06:35 2000
@@ -1042,7 +1042,7 @@
c = *cp;
if (c & 0200)
goto bad;
- if
2016 Mar 14
2
LLVM-3.8.0 libcxx in-tree build fails with cmath error ::signbit has not been declared
Greetings!
I have been building llvm-3.6.x, 3.7.1 and 3.7.2 with (glibc-2.12.1, binutils-2.24, gcc-4.9.2) almost same set if CMake flags.
However while building LLVM-3.8.0 using same CMake flags I am observing projects/libcxx/include/cmath errors...
...'::signbit' has not been declared
...'::fpclassify' has not been declared
...'::isfinite' has not been declared
...
2002 Aug 02
3
[Bug 377] New: Reduce compiler warnings. Use unsigned args to the ctype.h is*() macros.
http://bugzilla.mindrot.org/show_bug.cgi?id=377
Summary: Reduce compiler warnings. Use unsigned args to the
ctype.h is*() macros.
Product: Portable OpenSSH
Version: -current
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: trivial
Priority: P2
Component: Miscellaneous
2005 Apr 25
2
How about a --min-size option, next to --max-size
There's a rather old bug report in Debian's bug tracking system
(see http://bugs.debian.org/27126) about wanting to be able to specify
the maximum file size, as well as the minimum file size. Here's the
text:
Sometimes, it's useful to specify a file size range one is
interested in.
For example, I'd like to keep an up-to-date mirror of Debian, but I
currently
2013 May 14
5
tools/libxl: fix compilation and link errors on NetBSD
commit cad172d7b88bd443c81d865051297875ce2551bc
Author: Christoph Egger <chegger@amazon.de>
Date: Thu Feb 7 14:42:29 2013 +0000
tools/libxl: fix compilation and link errors on NetBSD
- Fix testidl link error that libyajl is not found
- Make linking of xl and testidl consistent
- fix error: array subscript has type ''char''
Signed-off-by:
2008 May 27
2
[PATCH] Fixes bug which strips every other digit in klibc-utils dmesg output
There is a bug in the way which klibc/usr/utils/dmesg.c tries to strip
the initial <[0-7]> from kernel messages. The bug causes every other
numerical digit to be stripped from the output. Fixed.
A bug report with lots of details has been filed for Debian and Ubuntu:
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483186
* https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/235282
2016 May 25
4
Runtime interception: design problem
Hi everyone,
I am having troubles but this shouldn't be hard to solve for many people
here. I am beginning a runtime feature for the BoundsChecking pass and I
want to replace the libc malloc&free. I followed the design of
AddressSanitizer (Asan) and tried to use the INTERCEPTOR macro from the
interception.h file of compiler-rt library.
Here is the problem. The file I modify
2010 Aug 09
8
Call for testing: OpenSSH-5.6
Hi,
OpenSSH 5.6 is almost ready for release, so we would appreciate testing
on as many platforms and systems as possible. This is a moderately large
release, with a number of new features and bug fixes.
Snapshot releases for portable OpenSSH are available from
http://www.mindrot.org/openssh_snap/
The OpenBSD version is available in CVS HEAD:
http://www.openbsd.org/anoncvs.html
Portable OpenSSH
2017 Nov 21
2
[PATCH REPOST 1/2] common/mlstdutils: Add return statement.
No change, just reposting without the "for discussion" tag.
I think we should allow this as it seems like a nice coding style for
a limited subset of imperative-style code.
Rich.
2017 Nov 05
2
[PATCH 0/2] (mainly for discussion) Add ‘return’ statement.
When rewriting the heavily imperative original inspection code, I
longed for a ‘return’ statement so I could keep the new code as close
as possible to the original. OCaml of course does not have such a
statement, but it's relatively simply to implement it in the language.
The first patch does so, and the second patch rewrites a sample of the
inspection code to use it.
Rich.