On Fri, 02 Oct 2009 10:33:43 +0300, Matthias Apitz wrote:
This morning I went to the FreeBSD ports collection server:
http://www.freebsd.org/cgi/ports.cgi?query=pidgin&stype=all
and there is a version 2.6.2 as well; I've fetched the tar ball of the
port in the hope that I will compile in my Free
On Fri, 02 Oct 2009 14:12:57 +0300, David Southwell
wrote:
Can anyone solve this challenge. In any case it would be good to have wine
available in the ports tree for amd64 as well as i386.
I am sure there used to be an i386 emulator for amd64 but maybe I am imagining
things!
Try this:
http://
Anyone who uses config-recursive more often than once a year knows that
it's broken. Or at least they know it needs to be run multiple times until
it doesn't show options dialog. While some people might just live with it,
I think it should be fixed properly, and so did the person who introduced
th
On Mon, 07 Dec 2009 22:59:22 +0200, Dominic Fandrey
wrote:
Andrius Morkūnas wrote:
Anyone who uses config-recursive more often than once a year knows that
it's broken. Or at least they know it needs to be run multiple times until
it doesn't show options dialog. While some people
On Tue, 09 Feb 2010 13:19:21 +0200, Jerry wrote:
The entire build log is available here:
http://seibercom.net/logs/qt33.txt
That's what you get when you don't read UPDATING file.
However, upon checking, I discovered this:
$ locate libjpeg.so.10
/usr/local/lib/libjpeg.so.10
Your locate da
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=cla
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
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 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, 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 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 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 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
Hi list,
One of the things I've been working on for the past few weeks is
creating an easy way to change ports compiler without breaking things
that shouldn't break "just" because compiler changed. Some of the
current problems are mentioned on the wiki page[1]. Something not
mentioned there is th
14 matches
Mail list logo
