Date: Wed, 31 Jul 2013 10:13:42 -0500 From: The BSD Dreamer <beastie@tardisi.com> To: freebsd-chromium@freebsd.org Subject: Re: chromium (unclickable links) still not fixed Message-ID: <93050061ddc663a68b43e3a117a411e4@lhaven.homeip.net> In-Reply-To: <51F9107A.9070303@freebsd.org> References: <51F82EB3.7020700@janh.de> <CANcjpOAVErrhhZT%2BWq9Hs9DX9WjFq4Dt8SYYZe=sVcWp7SamNg@mail.gmail.com> <51F90C2B.6060503@freebsd.org> <51F90DCD.3020905@janh.de> <51F9107A.9070303@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-07-31 08:26, René Ladan wrote: > On 31-07-2013 15:14, Jan Henrik Sylvester wrote: >> On 07/31/2013 15:07, René Ladan wrote: >>> On 31-07-2013 13:57, George Liaskos wrote: >>>> https://github.com/gliaskos/freebsd-chromium/blob/master/www/chromium/Makefile#L137 >>>> >>>> This is wrong, even if clang port is installed CC points /usr/bin/clang. >>>> It's obviously working only for releases that don't have clang. >>>> >>>> >>> My bad, can you try http://people.freebsd.org/~rene/chromium-clang.diff ? >> I can test later, but currently, I see 404 for your link. I will try >> again later today. > Whoops, http://people.freebsd.org/~rene/patches/chromium-clang.diff > I had wondered what caused lang/clang to get installed on my system, when none of the ports that use clang seem to use it. In fact, chromium is the (only) port (for me) that caused lang/clang to get installed. Compiling now.... will check when I return.... Though I thought I saw discussion about using lang/clang33 - lang/clang is 3.2 -- Name: Lawrence "The Dreamer" Chen Call: W0LKC Snail: 1530 College Ave, A5 Email: beastie@tardisi.com Manhattan, KS 66502-2768 Blog: http://lawrencechen.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?93050061ddc663a68b43e3a117a411e4>