On Sat, Jul 28, 2012 at 7:59 PM, Mikhail T. wrote:
> On 28.07.2012 12:25, Thomas Zander wrote:
>
> It also causes the port to use clang when setting CC=clang in
> /etc/src.conf (!) which fails here.
>
> What if you use CC?=clang instead? Thanks,
This works:
CC?=clang
CXX?=clang++
CPP?=clang-cpp
On Sun, Jul 29, 2012 at 8:54 AM, Kimmo Paasiala wrote:
> On Sat, Jul 28, 2012 at 9:26 PM, Boris Samorodov wrote:
>> Hi All,
>>
>> I use clang as default system compiler (WITH_CLANG_IS_CC="YES"
>> at /etc/make.conf). The system is i386-current as of yesterday,
>> fresh ports as of yesterday.
>>
>>
On Fri, 27 Jul 2012, Jeremy Messenger wrote:
>Hello all,
>The MATE base desktop (x11/mate-base) is ready to use and test. ...
>... To get it, you will need to grab
>marcusmerge script from http://www.marcuscom.com/downloads/marcusmerge
>then run 'sh marcusmerge -m ports-experimental'.
Doug Barto
ajtiM writes:
> Hi!
>
> On my FreeBSD 9.0 Release, KDE 4.8.4, Firefox 14.0.1 stooped working with
> linuxflashplugin 11. There is no problem with Opera.
First, try firefox package and show pkg_info -aE output. Blame pointyhat
tardiness if the package (for 14.0.1) is not available yet.
Second,
Eitan Adler writes:
> On 28 July 2012 01:59, Florian Smeets wrote:
>
>> P.S. We really need a way of depending on ports being built with certain
>> OPTIONS.
>
> Slave ports.
In this case APNG has both compatible ABI and Mozilla looking into its
security. For stubborn people there is an undocume
On 2012-07-29 09:47, Kimmo Paasiala wrote:
> On Sun, Jul 29, 2012 at 8:54 AM, Kimmo Paasiala wrote:
>> On Sat, Jul 28, 2012 at 9:26 PM, Boris Samorodov wrote:
>>> Hi All,
>>>
>>> I use clang as default system compiler (WITH_CLANG_IS_CC="YES"
>>> at /etc/make.conf). The system is i386-current as o
On 29/07/2012 02:19, Jan Beich wrote:
>> FWIW, pkgng does track options but there is no *.mk magic to take
>> > advantage of this yet.
>> >
>> > $ tar xOf png-1.5.12.txz --include +MANIFEST | fgrep -i opt
>> > options: {APNG: on}
pkg query "%Ok %Ov" png
Cheers,
Matthew
--
D
On Sat, 28 Jul 2012 16:54:40 -0700 (PDT)
Doug Barton articulated:
> On Wed, 25 Jul 2012, Jerry wrote:
>
> > On Wed, 25 Jul 2012 11:14:25 -0700
> > Doug Barton articulated:
> >
> >> On 07/25/2012 08:03, Michael wrote:
> >>> Hello obrien,
> >>>
> >>> Any plans to update bash-4.2.28 up to patch leve
On Sat, 9 Jun 2012, Doug Barton wrote:
>> Are you saying you actually noticed some leftovers in /tmp, or that
>> there "just" has been more at certain points in time than you would
>> expect?
> I finally had time to watch this closely, and found the culprit(s).
> While building the port creates a l
On 07/29/2012 13:50, Gerald Pfeifer wrote:
> On Sat, 9 Jun 2012, Doug Barton wrote:
>>> Are you saying you actually noticed some leftovers in /tmp, or that
>>> there "just" has been more at certain points in time than you would
>>> expect?
>> I finally had time to watch this closely, and found the
On Thu, 16 Feb 2012, b. f. wrote:
>> The main question is why this port (and everythin else with
>> USE_GCC=4.6+) depend on lang/gcc46 and not lang/gcc. Most port
>> users dislike building latest gcc snapshot on a weekly basis.
> Indeed. But (as discussed before on this list), they don't have to,
Umm ... wow. I'll try to respond substantively below.
On 07/29/2012 04:46, Jerry wrote:
> On Sat, 28 Jul 2012 16:54:40 -0700 (PDT)
> Doug Barton articulated:
>
>> Completely aside from my being thoroughly impressed with your
>> mind-reading abilities, upgrading to the latest/greatest is not
>> al
On Sun, 29 Jul 2012 15:42:38 -0700
Doug Barton articulated:
> Umm ... wow. I'll try to respond substantively below.
>
> On 07/29/2012 04:46, Jerry wrote:
> > On Sat, 28 Jul 2012 16:54:40 -0700 (PDT)
> > Doug Barton articulated:
> >
> >> Completely aside from my being thoroughly impressed with you
On Tue, 13 Dec 2011, b. f. wrote:
>> Ahh. I see the issue. I have not looked at bsd.gcc.mk, but it does not
>> seem like this should be too difficult. Just a matter of the right
>> person having the time. Would ports specifying gcc46 need to be
>> touched?
> Gerald had planned to do this after the
On 07/29/2012 16:55, Gerald Pfeifer wrote:
> lang/gcc and lang/gcc46 should be fully compatible, without rebuilds
> necessary. Only when lang/gcc is going to move to GCC 4.7 later this
> year would I consider that.
IMO this highlights the issue that unversioned instances of ports that
really need
On Sun, Jul 29, 2012 at 4:49 PM, Jerry wrote:
> On Sun, 29 Jul 2012 15:42:38 -0700
> Doug Barton articulated:
>
>> Umm ... wow. I'll try to respond substantively below.
>>
>> On 07/29/2012 04:46, Jerry wrote:
>> > On Sat, 28 Jul 2012 16:54:40 -0700 (PDT)
>> > Doug Barton articulated:
>> >
>> >> Co
Kevin sorry for posting this from your message "it had to go somewhere
since there was no such great message to reply to." not intended
directly toward anyone in general.
This thread has turned to nothing but obnoxious dribble of what used to
be a simple problem to solve.
All of the bash-* patc
Hello Ashish;
The patches applied successfully and the port installation was also
successful, but when I try to run emacs with emacsclient -c, my system
becomes semi-unresponsive. I can still hit the power button on my
laptop for a clean shutdown but a C-c won't stop emacs and I can't log
out of
Joseph Mingrone writes:
> for a few months). Running emacsclient -t works fine. If I start
> emacs with just "% emacs", and I don't wait to long, I can kill it
> with a C-c and the warning/error messages below appear in xterm:
>
> % emacs
> ^C
> (process:1589): GLib-WARNING **: In call to g_spa
19 matches
Mail list logo
