Hi,
In /etc/make.conf, I put WITH_LLDB="yes"
and rebuilt/reinstalled the world.
I then tried:
(lldb) script
error: your copy of LLDB does not support scripting.
Is there a way to configure LLDB with script support?
--
Craig
___
rodrigc added a comment.
Sorry for the late response. Please address @dim 's comment, if you have not
addressed it already.
Also, removing the type-alias punned warnings is trickier than the other types
of fixes that we have done to clean up the code.
For this change, I would feel more
rodrigc created this revision.
rodrigc added reviewers: araujo, bapt, emaste, dim.
rodrigc added a subscriber: freebsd-toolchain.
rodrigc set the repository for this revision to rS FreeBSD src repository.
Herald added a subscriber: imp.
REVISION SUMMARY
Without this fix, compiling ypbind with
Hi,
On a FreeBSD 10.1-RELEASE system I just did:
pkg install devel/amd64-gcc
pkg install devel/amd64-toolchain-gcc
pkg info -o -g '*gcc*'
amd64-gcc-4.9.2_1 devel/amd64-gcc
amd64-xtoolchain-gcc-0.1 devel/amd64-xtoolchain-gcc
The devel/amd64-toolchain-gcc package installs this
On Sun, Apr 19, 2015 at 2:10 AM, Eitan Adler li...@eitanadler.com wrote:
Perhaps it would be useful to do a second run of this, but with a
modified share/mk to silence the most useless of these warnings?
Sure, that's fine. Can you provide a modified share/mk which you think
does the right
Hi,
After the latest commits by members of freebsd-toolchain@ ,
I have managed to compile latest CURRENT world and GENERIC
kernel on amd64 with an gcc 4.9 external toolchain by doing:
pkg install devel/amd64-xtoolchain-gcc
cd /usr/src
sed -i -e 's/boot2//' sys/boot/i386/Makefile
rodrigc abandoned this revision.
rodrigc added a comment.
Fixed by rS281659
REVISION DETAIL
https://reviews.freebsd.org/D2305
To: rodrigc, imp, emaste
Cc: freebsd-toolchain
___
freebsd-toolchain@freebsd.org mailing list
On Sat, Mar 28, 2015 at 4:05 PM, Craig Rodrigues rodr...@freebsd.org
wrote:
Hi,
To work around the problems build rescue, this time I used a build host
running FreeBSD-CURRENT at svn revision r280353
I took this patch for libc++ and applied it to my tree:
http://reviews.llvm.org/D8461
I
rodrigc created this revision.
rodrigc added reviewers: emaste, imp.
rodrigc added a subscriber: freebsd-toolchain.
REVISION SUMMARY
When using an external gcc 4.9 toolchain on a FreeBSD 10.1 build host,
building of the CURRENT branch failed when trying to build rescue.
See this
rodrigc updated this revision to Diff 4840.
rodrigc added a comment.
Change to
CHANGES SINCE LAST UPDATE
https://reviews.freebsd.org/D2285?vs=4825id=4840
REVISION DETAIL
https://reviews.freebsd.org/D2285
AFFECTED FILES
sys/crypto/aesni/aesencdec.h
sys/crypto/aesni/aesni_ghash.c
rodrigc updated this revision to Diff 4825.
rodrigc added a comment.
OK, here's an updated diff where things are separate out into a different
header file.
CHANGES SINCE LAST UPDATE
https://reviews.freebsd.org/D2285?vs=4798id=4825
REVISION DETAIL
https://reviews.freebsd.org/D2285
AFFECTED
rodrigc closed this revision.
rodrigc added a comment.
Committed under rS277904
REVISION DETAIL
https://reviews.freebsd.org/D1722
To: rodrigc, brooks, imp
Cc: freebsd-toolchain
___
freebsd-toolchain@freebsd.org mailing list
On Tue, Mar 31, 2015 at 10:10 PM, John-Mark Gurney j...@funkthat.com wrote:
This is an issue w/ gcc 4.9's headers... It is including stdlib.h,
via mm_malloc.h which is conflicting w/ sys/malloc.h's version of free..
kan wrapped the include of mm_malloc.h in an #if __STDC_HOSTED__ which is
On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric d...@freebsd.org wrote:
On 31 Mar 2015, at 20:13, Dimitry Andric d...@freebsd.org wrote:
...
but then:
+ patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|Index:
On Sun, Mar 29, 2015 at 1:52 PM, Dimitry Andric d...@freebsd.org wrote:
And none of these prints any compilation command lines? Are you running
with make -s, by any chance? If so, try removing it so we can see how
the various source files are being compiled.
I am not using make -s. If
On Sun, Mar 29, 2015 at 11:04 AM, Warner Losh i...@bsdimp.com wrote:
If we built a UFS1-only boot2, that would fit in the 7.5k we have left
to play with. We could then build a UFS2-only boot2 that would easily
fit in the like 32k limit that UFS2 has.
The only reason we went to supporting
Hi,
When building with gcc 4.9, I am getting unresolved symbols at link
time when building usr.bin/clang/clang. Here is one error message:
/usr/obj/opt2/branches/head/usr.bin/clang/clang/../../../lib/clang/libclangcodegen/libclang
codegen.a(ModuleBuilder.o): In function `(anonymous
Hi,
To work around the problems build rescue, this time I used a build host
running FreeBSD-CURRENT at svn revision r280353
I took this patch for libc++ and applied it to my tree:
http://reviews.llvm.org/D8461
I used this script to build with gcc 4.9:
On Sat, Mar 28, 2015 at 2:34 PM, Craig Rodrigues rodr...@freebsd.org
wrote:
I double checked. cat.lo is not a truncated file.
# ls -l cat.lo ; file cat.lo
-rw-r--r-- 1 jenkins wheel 13112 Mar 28 21:17 cat.lo
cat.lo: ELF 64-bit LSB relocatable, x86-64, version 1 (FreeBSD), stripped
Hmm
On Fri, Mar 27, 2015 at 10:03 PM, Craig Rodrigues rodr...@freebsd.org
wrote:
Hi,
I had problems compiling lldb with gcc 4.9.
See problem description plus patch which I submitted upstream:
https://llvm.org/bugs/show_bug.cgi?id=23051
My patch was accepted upstream:
http://llvm.org/viewvc
Hi,
I had problems compiling lldb with gcc 4.9.
See problem description plus patch which I submitted upstream:
https://llvm.org/bugs/show_bug.cgi?id=23051
--
Craig
___
freebsd-toolchain@freebsd.org mailing list
On Mon, Mar 23, 2015 at 12:12 AM, Dimitry Andric d...@freebsd.org wrote:
On 23 Mar 2015, at 01:49, Craig Rodrigues rodr...@freebsd.org wrote:
Hi,
I tried to build HEAD with gcc 4.9.1 after the latest clang 3.6.0 import,
and am getting
new build failures related to C
Hi,
I tried to build HEAD with gcc 4.9.1 after the latest clang 3.6.0 import,
and am getting
new build failures related to C++ such as:
/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include/c++/v1/type_traits:881:87:
error: use of deleted
On Sun, Mar 22, 2015 at 2:29 PM, Dimitry Andric d...@freebsd.org wrote:
Ah right, that was on i386, on amd64 it does result in -2^63. It is
indeed caused by reliance on signed integer wrapping.
This diff should fix it, without rewriting the utility:
Index: bin/expr/Makefile
On Sun, Mar 22, 2015 at 2:36 PM, Dimitry Andric d...@freebsd.org wrote:
On 22 Mar 2015, at 22:32, Craig Rodrigues rodr...@freebsd.org wrote:
On Sun, Mar 22, 2015 at 2:29 PM, Dimitry Andric d...@freebsd.org wrote:
Ah right, that was on i386, on amd64 it does result in -2^63
On Tue, Mar 3, 2015 at 9:17 AM, Dimitry Andric d...@freebsd.org wrote:
On 03 Mar 2015, at 09:00, Craig Rodrigues rodr...@freebsd.org wrote:
CXXFLAGS+= -D_LIBCPP_HAS_NO_ADVANCED_SFINAE
to the make.conf file you use for building.
Thanks for the tip. I added that to make.conf, but now
I am
Hi,
We currently have a Jenkins job which checks out llvm trunk and builds
it like this:
svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
cd llvm
./configure --enable-optimized --disable-assertions --disable-docs
--enable-targets=host \
Hi,
On Windows, there is a tool, http://www.dependencywalker.com/ , that
can take a DLL as input, and then display all the dependencies that this
DLL has on other libraries. This can be used to detect unresolved symbols.
Does anyone have a script that can do this on FreeBSD?
Basically, this
Hi,
I just tried to build CURRENT with WITH_LLDB=yes
in /etc/make.conf. I got this error:
/usr/obj/opt2/branches/head/usr.bin/clang/lldb/../../../lib/clang/libllvmaarch64disassemble
r/libllvmaarch64disassembler.a(AArch64Disassembler.o): In function
`createAArch64ExternalSy
On Thu, Jan 8, 2015 at 6:04 AM, Ed Maste ema...@freebsd.org wrote:
On 8 January 2015 at 08:45, Craig Rodrigues rodr...@freebsd.org wrote:
I just tried to build CURRENT with WITH_LLDB=yes
in /etc/make.conf. I got this error:
...
Thanks for the report Craig, I'm looking
On Thu, Nov 6, 2014 at 9:13 AM, Arthur Mesh am...@juniper.net wrote:
/usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such file
or directory
Prokash Sinha from Panasas asked the exact same question:
https://lists.freebsd.org/pipermail/freebsd-toolchain/2014-August/001181.html
gdb from
base (at least in CURRENT).
Thanks.
--
Craig
On Wed, Jun 11, 2014 at 11:53 AM, Craig Rodrigues rodr...@freebsd.org
wrote:
Hi,
Recently when trying to debug some coredumps in CURRENT from
a userland process in the devel/libvirt port, I found that the gdb in
base could not get
Hi,
Recently when trying to debug some coredumps in CURRENT from
a userland process in the devel/libvirt port, I found that the gdb in
base could not get a backtrace from the core file:
http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002606.html
I needed to add to my
On Wed, Jun 11, 2014 at 12:34 PM, Warner Losh i...@bsdimp.com wrote:
Except for kgdb functionality, the gdb ports (both the 6.x and 7.x ones) work
much better than the gdb in the tree. This may be a good stop-gap until lldb
is ready.
Warner
I installed devel/gdb which installs gdb762.
On Wed, Jun 11, 2014 at 1:39 PM, Dimitry Andric d...@freebsd.org wrote:
Ah sorry, your objdump prints sections in a different order than mine.
I was mainly interested in the DWARF version of debug information; maybe
the way you built libvirt has caused it to contain DWARF4 instead of
DWARF2.
On Mon, Dec 2, 2013 at 6:40 AM, Justin Hibbits chmeeed...@gmail.com wrote:
Yesterday I started a full world update for my machine (powerpc64), but
the new gcc import ICEs at emit-rtl.c:1784, when compiling zdb. I
haven't tried reverting contrib/gcc yet, but is there a good way to
debug this?
36 matches
Mail list logo