On 05/05/10 10:13, Roman Divacky wrote:
> 2) mergemaster problems - I have a fix but have not commited it yet
Can you describe the problem, and your proposed fix?
Doug
--
... and that's just a little bit of history repeating.
-- Propellerheads
Improve
On Thursday 06 May 2010 04:13:57 Roman Divacky wrote:
> fwiw, it looks like it may make sense to have 2nd round of runtime testing
> :)
>
> these things were fixed in clangbsd that were reported as problems:
>
> 1) static binaries (eg. make) crash
>
> 2) kernel sound module miscompilation
>
> 3
fwiw, it looks like it may make sense to have 2nd round of runtime testing :)
these things were fixed in clangbsd that were reported as problems:
1) static binaries (eg. make) crash
2) kernel sound module miscompilation
3) bootloader problem which prevented clangbsd from booting
4) fix buildin
On Thu, 29 Apr 2010 14:05:25 +0300, Dima Panov wrote:
Ruby is bad?
More like clang is bad, it's a known issue.
clangbsd errors in my blog:
http://dimapanov.wordpress.com/2010/04/29/clangbsd/
at this moment unbuildable some critical ports:
devel/binutils
devel/icu[4]
devel/pcre
lang/ruby1[
On Thursday 29 April 2010 02:40:24 Dima Panov wrote:
> On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > According to Dima Panov:
> > > while building lang/ruby18:
> > Which options to you use?
> >
> > _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> > WITHOUT_ONIGURUMA=true
> > WITH_RDOC
On Wed, Apr 28, 2010 at 10:32:41PM +0200, Alexey Shuvaev wrote:
> On Thu, Apr 29, 2010 at 02:40:24AM +1100, Dima Panov wrote:
> > On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > > According to Dima Panov:
> > > > while building lang/ruby18:
> > > Which options to you use?
> > >
> >
On Thu, Apr 29, 2010 at 02:40:24AM +1100, Dima Panov wrote:
> On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> > According to Dima Panov:
> > > while building lang/ruby18:
> > Which options to you use?
> >
> > _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> > WITHOUT_ONIGURUMA=true
> > WI
On Wednesday 28 April 2010 23:16:38 Ollivier Robert wrote:
> According to Dima Panov:
> > while building lang/ruby18:
> Which options to you use?
>
> _OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
> WITHOUT_ONIGURUMA=true
> WITH_RDOC=true
> WITHOUT_DEBUG=true
>
> I notice your ruby is compiling w/o a
According to Brooks Davis:
> For the foreseeable future, doing anything but using the latest port is a
> recipe for problems.
The "make BOOTSTRAP=yes makesum" is a wonderful trick, thanks Brooks!
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
In memoriam to Ond
According to Dima Panov:
> while building lang/ruby18:
Which options to you use?
_OPTIONS_READ=ruby+oniguruma-1.8.7.248_1,1
WITHOUT_ONIGURUMA=true
WITH_RDOC=true
WITHOUT_DEBUG=true
I notice your ruby is compiling w/o any -On, try with -O at least?
> clang -I/usr/include -pipe -g -g -std=gnu89
On Saturday 17 April 2010 03:08:18 Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org) into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD
> world on i386/amd64
while I agree that the function is strange there indeed is a bug
in llvm. See: http://llvm.org/bugs/show_bug.cgi?id=6941
On Tue, Apr 27, 2010 at 02:50:53PM +1000, Andrew Reilly wrote:
> On Sun, Apr 25, 2010 at 12:06:49PM +0200, Alexander Best wrote:
> > i was able to pinpoint the
> > exact functio
On Sun, Apr 25, 2010 at 12:06:49PM +0200, Alexander Best wrote:
> i was able to pinpoint the
> exact function which is causing the problem:
>
> it's snd_xbytes().
This is an odd-looking function. Its purpose is to compute the
size of a target buffer for a block of audio samples that might
be sam
Roman Divacky schrieb am 2010-04-24:
> ping any progress on this? :)
sorry it took some time, but i've been rather busy. i was able to pinpoint the
exact function which is causing the problem:
it's snd_xbytes().
[snip]
> > > Great stuff to have narrowed it down so much. Next logical step
>
On Thu, Apr 22, 2010 at 04:32:45PM -0700, K. Macy wrote:
> The current llvm-devel package is woefully out of date. Anyone wishing
> to try this will need to compile the latest port.
For the foreseeable future, doing anything but using the latest port is a
recipe for problems.
-- Brooks
> -Kip
>
The current llvm-devel package is woefully out of date. Anyone wishing
to try this will need to compile the latest port.
-Kip
On Fri, Apr 16, 2010 at 9:08 AM, Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org)
> into FreeBSD, replac
Ulrich Spörlein schrieb am 2010-04-22:
> On Wed, 21.04.2010 at 23:30:15 +0200, Alexander Best wrote:
> > Roman Divacky schrieb am 2010-04-21:
> > > On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> > > > Roman Divacky schrieb am 2010-04-21:
> > > > [snip]
> > > > > 1) cd modules/s
Andrew Reilly schrieb am 2010-04-22:
> On Wed, Apr 21, 2010 at 05:23:38PM +0200, Roman Divacky wrote:
> > On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> > > i might have stumbled upon a problem with clang. i've compiled a
> > > kernel from
> > > the clang branch using `make kerne
On Wed, 21.04.2010 at 23:30:15 +0200, Alexander Best wrote:
> Roman Divacky schrieb am 2010-04-21:
> > On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> > > Roman Divacky schrieb am 2010-04-21:
>
> > > [snip]
>
> > > > 1) cd modules/sound/sound && make CC=gcc
>
> > > after this s
On Wed, Apr 21, 2010 at 05:23:38PM +0200, Roman Divacky wrote:
> On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> > i might have stumbled upon a problem with clang. i've compiled a kernel from
> > the clang branch using `make kernel INSTKERNNAME=clang` and booted from it.
> > i'm n
Roman Divacky schrieb am 2010-04-21:
> On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> > Roman Divacky schrieb am 2010-04-21:
> > [snip]
> > > 1) cd modules/sound/sound && make CC=gcc
> > after this step these are the sizes of sound.ko* in
> > modules/sound/sound:
> > -rw-r--r
Roman Divacky schrieb am 2010-04-21:
> On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> > Roman Divacky schrieb am 2010-04-21:
> > [snip]
> > > 1) cd modules/sound/sound && make CC=gcc
> > after this step these are the sizes of sound.ko* in
> > modules/sound/sound:
> > -rw-r--r
Roman Divacky schrieb am 2010-04-21:
> On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> > Roman Divacky schrieb am 2010-04-21:
> > [snip]
> > > 1) cd modules/sound/sound && make CC=gcc
> > after this step these are the sizes of sound.ko* in
> > modules/sound/sound:
> > -rw-r--r
On Wed, Apr 21, 2010 at 09:44:45PM +0200, Alexander Best wrote:
> Roman Divacky schrieb am 2010-04-21:
>
> [snip]
>
> > 1) cd modules/sound/sound && make CC=gcc
>
> after this step these are the sizes of sound.ko* in modules/sound/sound:
>
> -rw-r--r-- 1 root wheel 449120 Apr 21 21:36 sound
Roman Divacky schrieb am 2010-04-21:
[snip]
> 1) cd modules/sound/sound && make CC=gcc
after this step these are the sizes of sound.ko* in modules/sound/sound:
-rw-r--r-- 1 root wheel 449120 Apr 21 21:36 sound.ko
-rw-r--r-- 1 root wheel 2284757 Apr 21 21:36 sound.ko.debug
-rw-r--r-- 1 r
Roman Divacky schrieb am 2010-04-21:
> On Wed, Apr 21, 2010 at 07:22:00PM +0200, Alexander Best wrote:
> > Roman Divacky schrieb am 2010-04-21:
> > > On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> > > > i might have stumbled upon a problem with clang. i've compiled
> > > > a
> >
On Wed, Apr 21, 2010 at 08:37:10PM +0200, Dimitry Andric wrote:
> On 2010-04-21 20:20, Roman Divacky wrote:
> >>[1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:140:1:
> >> [0m[0;1;35mwarning: [0m[1mcontrol may reach end of non-void function
> >>[-Wreturn-type]
> >>[0
On 2010-04-21 20:20, Roman Divacky wrote:
[1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:140:1:
[0m[0;1;35mwarning: [0m[1mcontrol may reach end of non-void function
[-Wreturn-type]
[0m}
[0;1;32m^
[0m[1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc
On Sat, Apr 17, 2010 at 07:03:14PM +0200, Dimitry Andric wrote:
> On 2010-04-16 18:08, Roman Divacky wrote:
> > cd clangbsd&& make buildworld
>
> Buildworld all goes well, until this stage:
>
> --
> >>>stage 4.2: building libraries
On Wed, Apr 21, 2010 at 07:22:00PM +0200, Alexander Best wrote:
> Roman Divacky schrieb am 2010-04-21:
> > On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> > > i might have stumbled upon a problem with clang. i've compiled a
> > > kernel from
> > > the clang branch using `make kern
On 21 Apr 2010, at 18:22, Alexander Best wrote:
> Roman Divacky schrieb am 2010-04-21:
>> On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
>>> i might have stumbled upon a problem with clang. i've compiled a
>>> kernel from
>>> the clang branch using `make kernel INSTKERNNAME=clang
Roman Divacky schrieb am 2010-04-21:
> On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> > i might have stumbled upon a problem with clang. i've compiled a
> > kernel from
> > the clang branch using `make kernel INSTKERNNAME=clang` and booted
> > from it.
> > i'm now experiencing au
On 2010-04-21 17:24, Roman Divacky wrote:
Tried llvm-devel-2.7.r101995 built with -O2, but no difference in the
result. I guess it's a real bug in llvm. :)
can you try with LLVM svn trunk? it works for me ok (with -O2 compilation)
AFAICS the only change between r101995 and r102001 is in some
On Wed, Apr 21, 2010 at 05:26:03PM +0200, Dimitry Andric wrote:
> On 2010-04-20 16:04, Roman Divacky wrote:
> >>Tried again with llvm r101891, still the same error...
> >
> >the problem is that gcc miscompiles llvm at -O3, I havent managed
> >to contact brooks@ to change the port to default to -O2
On Wed, Apr 21, 2010 at 05:20:57PM +0200, Alexander Best wrote:
> i might have stumbled upon a problem with clang. i've compiled a kernel from
> the clang branch using `make kernel INSTKERNNAME=clang` and booted from it.
> i'm now experiencing audio problems with mp3s and certain video files.
> pla
On 2010-04-20 16:04, Roman Divacky wrote:
Tried again with llvm r101891, still the same error...
the problem is that gcc miscompiles llvm at -O3, I havent managed
to contact brooks@ to change the port to default to -O2
you can do that locally I guess
Tried llvm-devel-2.7.r101995 built with -
i might have stumbled upon a problem with clang. i've compiled a kernel from
the clang branch using `make kernel INSTKERNNAME=clang` and booted from it.
i'm now experiencing audio problems with mp3s and certain video files.
playback is awfully slow and the audio output gets distorted massively. `to
On Fri, Apr 16, 2010 at 12:08 PM, Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang (
> clang.llvm.org)
> into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD
> world
> on i386/amd
On Tue, Apr 20, 2010 at 04:04:37PM +0200, Dimitry Andric wrote:
> On 2010-04-17 20:13, Roman Divacky wrote:
> I'm using the llvm-devel-2.7.r100430 port.
> >>
> >>This is the current devel/llvm-devel port, AFAICS? The system itself
> >>runs -CURRENT as of r206706.
> >
> >sorry.. havent noticed
On 2010-04-17 20:13, Roman Divacky wrote:
I'm using the llvm-devel-2.7.r100430 port.
This is the current devel/llvm-devel port, AFAICS? The system itself
runs -CURRENT as of r206706.
sorry.. havent noticed that you wrote that in your first mail
yes, i386 has a problem. I am just distilling
On Tue, Apr 20, 2010 at 02:38:01PM +0200, Alexander Best wrote:
> Eitan Adler schrieb am 2010-04-20:
> > > i was also wondering: what's the reason gcc is still being used
> > > during step
> > > "Building an up-to-date make(1)" and not clang?
>
> > because make segfaults when using clang ;)
>
> a
Eitan Adler schrieb am 2010-04-20:
> > i was also wondering: what's the reason gcc is still being used
> > during step
> > "Building an up-to-date make(1)" and not clang?
> because make segfaults when using clang ;)
ah ok. that's quite a good reason. ;)
--
Alexander Best
___
On 2010-Apr-20 10:39:26 +0300, Eitan Adler wrote:
>> i was also wondering: what's the reason gcc is still being used during step
>> "Building an up-to-date make(1)" and not clang?
>
>because make segfaults when using clang ;)
(On amd64) I've discovered this as well. It does somewhat restrict
th
> i was also wondering: what's the reason gcc is still being used during step
> "Building an up-to-date make(1)" and not clang?
because make segfaults when using clang ;)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
Roman Divacky schrieb am 2010-04-19:
> you have to use -O2
thanks a lot. using -O2 worked. :)
i was also wondering: what's the reason gcc is still being used during step
"Building an up-to-date make(1)" and not clang?
cheers.
> On Mon, Apr 19, 2010 at 02:29:07PM +0200, Alexander Best wrote:
> >
you have to use -O2
On Mon, Apr 19, 2010 at 02:29:07PM +0200, Alexander Best wrote:
> i'm getting this error during `make buildworld`:
>
> ===> libexec/atrun (all)
> clang -isystem /usr/obj/usr/local/src/clangbsd/tmp/usr/include/clang/1.5
> -isystem /usr/obj/usr/local/src/clangbsd/tmp/usr/include
i'm getting this error during `make buildworld`:
===> libexec/atrun (all)
clang -isystem /usr/obj/usr/local/src/clangbsd/tmp/usr/include/clang/1.5
-isystem /usr/obj/usr/local/src/clangbsd/tmp/usr/include
-B/usr/obj/usr/local/src/clangbsd/tmp/usr/lib/
-L/usr/obj/usr/local/src/clangbsd/tmp/usr/lib/
it looks like people are having problems with make - I'll take a look at that.
it may be libgcc issue of some very strange kind
On Sun, Apr 18, 2010 at 03:31:13PM +0300, George Liaskos wrote:
> >> /usr/obj/usr/src/make.amd64/usr/src/usr.bin/make created for
> >> /usr/src/usr.bin/make
> >> Segment
On Sun, Apr 18, 2010 at 03:09:48PM +0200, Erik Cederstrand wrote:
> Hi Roman
>
> Den 16/04/2010 kl. 18.08 skrev Roman Divacky:
>
> > We kindly ask you to setup ClangBSD chroot and/or use clang compiled kernel
> > and
> > use it as you would normally use FreeBSD. Please report back
>
> I insta
18.04.2010 13:49, Roman Divacky пишет:
On Sun, Apr 18, 2010 at 12:04:16PM +0400, Alex Keda wrote:
16.04.2010 20:08, Roman Divacky ?:
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang
(clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achiev
On 16.04.2010 20:08, Roman Divacky wrote:
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achieved the state when clang can compile all of FreeBSD world
on i386/amd64 platforms (including all
Hi Roman
Den 16/04/2010 kl. 18.08 skrev Roman Divacky:
> We kindly ask you to setup ClangBSD chroot and/or use clang compiled kernel
> and
> use it as you would normally use FreeBSD. Please report back
I installed ClangBSD kernel and world in a VirtualBox virtual machine (amd64)
and rebooted
>> /usr/obj/usr/src/make.amd64/usr/src/usr.bin/make created for
>> /usr/src/usr.bin/make
>> Segmentation fault (core dumped)
>> *** Error code 139
>>
>> Stop in /usr/src.
>> *** Signal 11
>>
>> Stop in /usr/src.
>
> what exactly is crashing here?
I have the same problem with make
Program received
18.04.2010 13:49, Roman Divacky пишет:
On Sun, Apr 18, 2010 at 12:04:16PM +0400, Alex Keda wrote:
16.04.2010 20:08, Roman Divacky ?:
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang
(clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achiev
On Sun, Apr 18, 2010 at 12:04:16PM +0400, Alex Keda wrote:
> 16.04.2010 20:08, Roman Divacky ?:
> >Hi,
> >
> >ClangBSD is a branch of FreeBSD that aims at integrating clang
> >(clang.llvm.org)
> >into FreeBSD, replacing GCC as a system compiler.
> >
> >Recently, we've achieved the state when c
18.04.2010 12:04, Alex Keda пишет:
16.04.2010 20:08, Roman Divacky пишет:
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang
(clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achieved the state when clang can compile all of
FreeBSD world
on i386
16.04.2010 20:08, Roman Divacky пишет:
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achieved the state when clang can compile all of FreeBSD world
on i386/amd64 platforms (including all the
In the last episode (Apr 17), Rui Paulo said:
> On 16 Apr 2010, at 22:41, Ivan Voras wrote:
> > I have a buildworld error here:
> >
> > clang -isystem /usr/obj/mt/clangbsd/tmp/usr/include/clang/1.5 -isystem
> > /usr/obj/mt/clangbsd/tmp/usr/include -B/usr/obj/mt/clangbsd/tmp/usr/lib/
> > -L/usr/o
On Sat, Apr 17, 2010 at 08:14:21PM +0200, Dimitry Andric wrote:
> On 2010-04-17 19:33, Roman Divacky wrote:
> >what version of clang/llvm are you using?
>
> As I mentioned at the end of my previous post:
>
> >>I'm using the llvm-devel-2.7.r100430 port.
>
> This is the current devel/llvm-devel po
On 2010-04-17 19:33, Roman Divacky wrote:
what version of clang/llvm are you using?
As I mentioned at the end of my previous post:
I'm using the llvm-devel-2.7.r100430 port.
This is the current devel/llvm-devel port, AFAICS? The system itself
runs -CURRENT as of r206706.
__
On 04/17/10 10:24, Andrius Morkūnas wrote:
> On Sat, 17 Apr 2010 20:07:05 +0300, Dimitry Andric
> wrote:
>> Btw, http://wiki.freebsd.org/BuildingFreeBSDWithClang says to put these
>> in src.conf, it does not mention make.conf. This is most likely the
>> correct location, right?
>
> Either way wo
On Sat, 17 Apr 2010 20:07:05 +0300, Dimitry Andric wrote:
Btw, http://wiki.freebsd.org/BuildingFreeBSDWithClang says to put these
in src.conf, it does not mention make.conf. This is most likely the
correct location, right?
Either way works, src.conf is probably more "correct" location, but it
what version of clang/llvm are you using?
On Sat, Apr 17, 2010 at 07:03:14PM +0200, Dimitry Andric wrote:
> On 2010-04-16 18:08, Roman Divacky wrote:
> > cd clangbsd&& make buildworld
>
> Buildworld all goes well, until this stage:
>
> ---
what version of clang/llvm are you using?
On Sat, Apr 17, 2010 at 11:48:02AM -0500, James R. Van Artsdalen wrote:
> Roman Divacky wrote:
> > Recently, we've achieved the state when clang can compile all of FreeBSD
> > world
> > on i386/amd64 platforms (including all the C++ apps we have and itsel
Roman Divacky wrote:
> Recently, we've achieved the state when clang can compile all of FreeBSD world
> on i386/amd64 platforms (including all the C++ apps we have and itself)
> and a bootable kernel.
bigback:/usr/clangbsd# make buildworld
.
.
.
clang++ -O2 -pipe
-I/usr/clangbsd/usr.bin/clang/lib/
On 2010-04-17 11:58, Roman Divacky wrote:
svn co http://svn.freebsd.org/base/projects/clangbsd/ clangbsd
cd clangbsd&& make buildworld
echo NO_WERROR=>> /etc/make.conf
echo WERROR=>> /etc/make.conf
you have to do those echos before the buildworld of course..
On 2010-04-16 18:08, Roman Divacky wrote:
cd clangbsd&& make buildworld
Buildworld all goes well, until this stage:
--
stage 4.2: building libraries
--
cd /home/di
On 16 Apr 2010, at 22:41, Ivan Voras wrote:
> Roman Divacky wrote:
>
>> We kindly ask you to setup ClangBSD chroot and/or use clang compiled kernel
>> and use it as you would normally use FreeBSD. Please report back
>
> I have a buildworld error here:
>
> clang -isystem /usr/obj/mt/clangbsd/t
On Fri, Apr 16, 2010 at 06:08:18PM +0200, Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org)
> into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD world
> on i
On Fri, Apr 16, 2010 at 3:45 PM, Ivan Voras wrote:
> Rink Springer wrote:
>>
>> On Sat, Apr 17, 2010 at 12:21:29AM +0200, Ivan Voras wrote:
/mt/clangbsd/lib/libc/sys/stack_protector.c:88:19: error: format string
is not a string literal (potentially insecure) [-Wformat-security]
Rink Springer wrote:
On Sat, Apr 17, 2010 at 12:21:29AM +0200, Ivan Voras wrote:
/mt/clangbsd/lib/libc/sys/stack_protector.c:88:19: error: format string
is not a string literal (potentially insecure) [-Wformat-security]
syslog(LOG_CRIT, msg);
^~~
1 diagnostic ge
On Sat, Apr 17, 2010 at 12:21:29AM +0200, Ivan Voras wrote:
> > /mt/clangbsd/lib/libc/sys/stack_protector.c:88:19: error: format string
> > is not a string literal (potentially insecure) [-Wformat-security]
> > syslog(LOG_CRIT, msg);
> > ^~~
> > 1 diagnostic genera
Ivan Voras wrote:
Roman Divacky wrote:
We kindly ask you to setup ClangBSD chroot and/or use clang compiled
kernel and use it as you would normally use FreeBSD. Please report back
I have a buildworld error here:
clang -isystem /usr/obj/mt/clangbsd/tmp/usr/include/clang/1.5 -isystem
/usr/ob
Roman Divacky wrote:
We kindly ask you to setup ClangBSD chroot and/or use clang compiled kernel and
use it as you would normally use FreeBSD. Please report back
I have a buildworld error here:
clang -isystem /usr/obj/mt/clangbsd/tmp/usr/include/clang/1.5 -isystem
/usr/obj/mt/clangbsd/tmp/u
Hi--
On Apr 16, 2010, at 1:53 PM, Outback Dingo wrote:
> can someone explain the benefit other then not relying on gcc now ?
> performance ?
http://clang.llvm.org/comparison.html
http://clang-analyzer.llvm.org/
Regards,
--
-Chuck
___
freebsd-curren
On Fri, Apr 16, 2010 at 12:08 PM, Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang (
> clang.llvm.org)
> into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD
> world
> on i386/amd
> Recently, we've achieved the state when clang can compile all of FreeBSD world
> on i386/amd64 platforms (including all the C++ apps we have and itself)
> and a bootable kernel. Thus we feel that the time has come to ask the FreeBSD
> community for wider testing on i386/amd64 (you sure can help w
On Fri, Apr 16, 2010 at 9:08 AM, Roman Divacky wrote:
> Hi,
>
> ClangBSD is a branch of FreeBSD that aims at integrating clang
> (clang.llvm.org)
> into FreeBSD, replacing GCC as a system compiler.
>
> Recently, we've achieved the state when clang can compile all of FreeBSD world
> on i386/amd64
Hi,
ClangBSD is a branch of FreeBSD that aims at integrating clang (clang.llvm.org)
into FreeBSD, replacing GCC as a system compiler.
Recently, we've achieved the state when clang can compile all of FreeBSD world
on i386/amd64 platforms (including all the C++ apps we have and itself)
and a bootab
79 matches
Mail list logo
