On Sun, 30 May 2010 16:36:45 +0300, Erik Cederstrand
wrote:
Andrius, would it make sense to create e.g. a wiki page tracking the status and
current known problems with compiling ports with clang? Just like there's a
wiki page ClangBSD status.
http://wiki.freebsd.org/PortsAndClang
It doesn't
Den 30/05/2010 kl. 14.51 skrev Andrius Morkūnas:
> On Sun, 30 May 2010 14:58:05 +0300, Volodymyr Kostyrko
> wrote:
>> 1. __dso not found after link. Some symbols seems to be omitted from
>> libraries and linking of plugins fails badly.
> Known problem with known fix.
>
>> 2. Assembler errors.
On Sun, 30 May 2010 14:58:05 +0300, Volodymyr Kostyrko
wrote:
1. __dso not found after link. Some symbols seems to be omitted from
libraries and linking of plugins fails badly.
Known problem with known fix.
2. Assembler errors. Xorg has some in x11-servers/xorg-server
x11-drivers/xf86-video-
On 2010-May-03 16:33:19 +0300, Andrius Morkūnas wrote:
>I wasn't talking about any specific port. What I meant is that new hardware
>won't stop coming out just because FreeBSD decided not to update their gcc.
>New CPUs may have new instructions and other things that are different from
>their prede
On Mon, 03 May 2010 15:34:43 +0300, C. Bergström
wrote:
What fancy stuff is in the ports tree which clang will take advantage of?
I wasn't talking about any specific port. What I meant is that new hardware
won't stop coming out just because FreeBSD decided not to update their gcc.
New CPUs may
On 2010-05-03 13:19, "C. Bergström" wrote:
>> Of course it does. It forces you to make your software portable.
>>
> and your point is?
>
> Are you trying to say that s/building/porting/ between compilers is
> going to magically make the software (have less bugs, more performance
> or better
Andrius Morkūnas wrote:
On Mon, 03 May 2010 13:38:07 +0300, C. Bergström
wrote:
I can understand from a commercial perspective why having a permissive
licensed production compiler could be good.. I can understand why many
people don't like gcc or fsf, but what does the BSD community get?
1) Pe
On Mon, 03 May 2010 14:27:52 +0300, Kostik Belousov wrote:
For me, the project that makes sense is exactly "making freebsd ports
work with clang", instead of what many have read "making applications
ported to freebsd and compiled with clang work". Please note the subtle
but very important differ
On 03/05/2010 12:38, "C. Bergström" wrote:
> What's really the goal here?
In my opinion it's about staying away from the GPLv3. According
to my understanding of the situation, GPLv3 code is not accepted
into the project and that means we're stuck with gcc 4.2, which
has already reached its EOL.
T
On Mon, 03 May 2010 13:38:07 +0300, C. Bergström
wrote:
I can understand from a commercial perspective why having a permissive
licensed production compiler could be good.. I can understand why many
people don't like gcc or fsf, but what does the BSD community get?
1) Performance?
2) Robustness
On Mon, May 03, 2010 at 06:19:48PM +0700, "C. Bergstr??m" wrote:
> Dimitry Andric wrote:
> >On 2010-05-03 12:38, "C. Bergstr??m" wrote:
> >
> >>What's really the goal here? What problem are you working to solve?
> >>May I humbly say that building software with a different compiler in
> >>itse
On Mon, 03 May 2010 12:44:54 +0200
Dimitry Andric wrote:
> On 2010-05-03 12:38, "C. Bergström" wrote:
> > What's really the goal here? What problem are you working to
> > solve? May I humbly say that building software with a different
> > compiler in itself doesn't really accomplish anything.
>
Dimitry Andric wrote:
On 2010-05-03 12:38, "C. Bergström" wrote:
What's really the goal here? What problem are you working to solve?
May I humbly say that building software with a different compiler in
itself doesn't really accomplish anything.
Of course it does. It forces you to m
On 2010-05-03 12:38, "C. Bergström" wrote:
> What's really the goal here? What problem are you working to solve?
> May I humbly say that building software with a different compiler in
> itself doesn't really accomplish anything.
Of course it does. It forces you to make your software portable.
Peter Pentchev wrote:
On Sun, May 02, 2010 at 11:51:52PM +0300, Andrius Mork??nas wrote:
On Sun, 02 May 2010 10:25:22 +0300, Yuri wrote:
Having tried clang++ I have a feeling that it's not quite ready to be a
generic c++ compiler.
[snip]
Very immature.
Many problems
On Sun, May 02, 2010 at 11:51:52PM +0300, Andrius Mork??nas wrote:
> On Sun, 02 May 2010 10:25:22 +0300, Yuri wrote:
> > Having tried clang++ I have a feeling that it's not quite ready to be a
> > generic c++ compiler.
[snip]
> > Very immature.
>
> Many problems that C++ ports have with clang is
On Sun 02 May 2010 at 14:03:06 PDT Andrius Mork??nas wrote:
On Sun, 02 May 2010 23:17:00 +0300, Eitan Adler
wrote:
Good - and those 30% of ports will help improve clang++ even more.
Some probably will, we submit a lot of bug reports for clang/llvm.
Hopefully over time that number will incre
On Sun, 02 May 2010 23:17:00 +0300, Eitan Adler
wrote:
Good - and those 30% of ports will help improve clang++ even more.
Some probably will, we submit a lot of bug reports for clang/llvm.
Hopefully over time that number will increase to 100% and we will be
able to say goodbye to gcc for goo
On Sun, 02 May 2010 10:25:22 +0300, Yuri wrote:
Having tried clang++ I have a feeling that it's not quite ready to be a
generic c++ compiler.
It crashes a lot, fails on many quite simple c++ patterns.
The current state of clang doesn't bother me too much. I'm aware of its
limitations, but I'm
> Having tried clang++ I have a feeling that it's not quite ready to be a
> generic c++ compiler.
> It crashes a lot, fails on many quite simple c++ patterns. Very immature.
> Don't you feel it's too early to start project like you are going to given
> the state of clang with c++?
> You will just k
Andrius Morkūnas wrote:
Hi,
I'm Andrius Morkūnas from Lithuania. My Summer of Code proposal was
accepted
this year and be working on my project, which is to make clang and
ports to
be friendly with each other.
My main goals are:
* Create an easy way to set ports compiler to either clang or gc
Hi,
I'm Andrius Morkūnas from Lithuania. My Summer of Code proposal was accepted
this year and be working on my project, which is to make clang and ports to
be friendly with each other.
My main goals are:
* Create an easy way to set ports compiler to either clang or gcc (and no,
CC=clang is not
22 matches
Mail list logo
