On Wed, Sep 19, 2012 at 02:13:41PM -0400, Gary Palmer wrote:
> >
> > Rxvt-unicode seemed to crash reliably whenever I was scrolling through a
> > document with less(1). If I reached the end of the document, and pressed
> > Page
> > Down (keysim Next), it would crash. It was quite weird.
> >
>
On Wed, Sep 19, 2012 at 07:12:50PM +0200, Roland Smith wrote:
> On Tue, Sep 18, 2012 at 12:02:20AM +0200, Dimitry Andric wrote:
> > On 2012-09-17 21:43, Roland Smith wrote:
> > > On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote:
> > ...
> > >> For most of the failures, we are already aw
On Tue, Sep 18, 2012 at 12:02:20AM +0200, Dimitry Andric wrote:
> On 2012-09-17 21:43, Roland Smith wrote:
> > On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote:
> ...
> >> For most of the failures, we are already aware of them, as a result of
> >> our periodic runs. So, just filing a P
Could you elaborate?
After setting WITHOUT_GCC I don't have
installed gcc/++ so it looks like it's working.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Clang-as-default-compiler-tp5742836p5744598.html
Sent from the freebsd-stable mailing list archive at
On 2012-09-17 21:43, Roland Smith wrote:
On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote:
...
For most of the failures, we are already aware of them, as a result of
our periodic runs. So, just filing a PR to say "broken on clang" doesn't
really help us all that much.
Those are b
On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote:
> On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote:
> > Is there a specif PR to use for ports that fails with clang and does
> > not specify to use gcc ( > devel/cdecl and deskutils/calibre so were
> > the culprits so far)
12.09.2012 00:49, Andreas Nilsson wrote:
On another clang note: Is there a page specifying valid settings for
-march, my google-foo is failing me. Ie, I'm looking for the equivalent of
http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
I'm u
>
>
> > in src.conf. No problem so far. However I wanted to avoid building base
> gcc
> > ( the whole collection ). Is WITHOUT_GCC what I'm looking for?
> >
>
> It probably is. However, WITHOUT_GCC is not supported yet.
>
> > On another clang note: Is there a page specifying valid settings for
> >
On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote:
> How about run automated test on two poudriere setups, one with CLANG set
> up, other with USE_GCC=4.2 applied to all ports which marked as broken,
We have been running various tests for quite some time.
> Is there somewhere lis
How about run automated test on two poudriere setups, one with CLANG set
up, other with USE_GCC=4.2 applied to all ports which marked as broken,
and find in pretty long but relatively easy way ports which should have
USE_GCC=4.2 to survive clang-era, and ports which even with that require a
bit mor
On Wed, Sep 12, 2012 at 08:00:46AM +0100, Chris Rees wrote:
> We don't want thousands of PRs duplicating the information from a simple
> list of failures.
Thanks, that was the point I was trying to make.
mcl
___
freebsd-stable@freebsd.org mailing list
h
On 12 Sep 2012 07:19, "Christer Solskogen"
wrote:
>
> On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon
wrote:
>
> > For most of the failures, we are already aware of them, as a result of
> > our periodic runs. So, just filing a PR to say "broken on clang"
doesn't
> > really help us all that much.
>
On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon wrote:
> For most of the failures, we are already aware of them, as a result of
> our periodic runs. So, just filing a PR to say "broken on clang" doesn't
> really help us all that much.
>
I disagree. Just a tiny bit ;-)
If the PR says that USE_GCC=
On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote:
> Is there a specif PR to use for ports that fails with clang and does
> not specify to use gcc ( > devel/cdecl and deskutils/calibre so were
> the culprits so far)
There is no specific PR. We have not yet placed the requirement on
On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote:
> Today I decided to take the plunge and make clang the default compiler, ie
> I set
>
> WITH_CLANG=yes
> WITH_CLANG_IS_CC=yes
> WITH_CLANG_EXTRAS=yes
>
> in src.conf. No problem so far. However I wanted to avoid building base gcc
> ( the wh
Today I decided to take the plunge and make clang the default compiler, ie
I set
WITH_CLANG=yes
WITH_CLANG_IS_CC=yes
WITH_CLANG_EXTRAS=yes
in src.conf. No problem so far. However I wanted to avoid building base gcc
( the whole collection ). Is WITHOUT_GCC what I'm looking for?
On another clang
16 matches
Mail list logo