On Thu, Mar 15, 2012 at 5:46 PM, Ronald F. Guilmette
wrote:
> Of course, I asked the Mesa/DRI dudes for help and advice, and of course
> they suggested that I consider using a rather more current version.
x11@ has an experimental repository available (information here
http://wiki.freebsd.org/Xorg
Jos Backus writes:
> On Thu, Mar 15, 2012 at 4:27 PM, Lowell Gilbert
> wrote:
>> Lowell Gilbert writes:
>>
>>> Lowell Gilbert writes:
>>>
Oleg Moskalenko writes:
> There is no option "-2" in the new BSD sort or in the GNU sort. There is
> no such option in Posix standard, t
On Thu, Mar 15, 2012 at 6:23 PM, Chuck Swiger wrote:
> On Mar 15, 2012, at 4:18 PM, Jeremy Messenger wrote:
>> Figured out. Add custom CFLAGS in the make.conf and you will get a
>> build failure with make but not gmake. Here's what I have in my
>> make.conf:
>>
>> CFLAGS= -O2 -fno-strict-aliasing
On Thu, Mar 15, 2012 at 4:27 PM, Lowell Gilbert
wrote:
> Lowell Gilbert writes:
>
>> Lowell Gilbert writes:
>>
>>> Oleg Moskalenko writes:
>>>
There is no option "-2" in the new BSD sort or in the GNU sort. There is
no such option in Posix standard, too.
What is this option
Lowell Gilbert writes:
> Lowell Gilbert writes:
>
>> Oleg Moskalenko writes:
>>
>>> There is no option "-2" in the new BSD sort or in the GNU sort. There is no
>>> such option in Posix standard, too.
>>>
>>> What is this option about, do we need to add something ?
>>
>> No, clearly I have misd
On Thu, Mar 15, 2012 at 4:14 PM, Niclas Zeising wrote:
> On 2012-03-15 20:50, Jeremy Messenger wrote:
>> I get a build failure on amd64:
>>
>> -
>> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_'
>> can not be used when making a shared object;
Lowell Gilbert writes:
> Oleg Moskalenko writes:
>
>> There is no option "-2" in the new BSD sort or in the GNU sort. There is no
>> such option in Posix standard, too.
>>
>> What is this option about, do we need to add something ?
>
> No, clearly I have misdiagnosed the problem.
> I'll take an
В Thu, 15 Mar 2012 14:46:23 -0700
"Ronald F. Guilmette" пишет:
>
>
> Who is allegedly maintaining the graphics/dri port at this moment in
> time?
>
> I would rather like to know, because it is in serious need of
> updating. (The version upon which the port was based was apparently
> released o
Oleg Moskalenko writes:
> There is no option "-2" in the new BSD sort or in the GNU sort. There is no
> such option in Posix standard, too.
>
> What is this option about, do we need to add something ?
No, clearly I have misdiagnosed the problem.
I'll take another look.
Sorry for the confusion.
On Thu, 15 Mar 2012 14:46:23 -0700
Ronald F. Guilmette articulated:
> Who is allegedly maintaining the graphics/dri port at this moment in
> time?
x...@freebsd.org
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
Who is allegedly maintaining the graphics/dri port at this moment in time?
I would rather like to know, because it is in serious need of updating.
(The version upon which the port was based was apparently released on
June 23, 2009, and there have been numerous new releases since then.)
I wouldn
On 2012-03-15 20:50, Jeremy Messenger wrote:
> I get a build failure on amd64:
>
> -
> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_'
> can not be used when making a shared object; recompile with -fPIC
> lapi.o: could not read symbols: Bad val
In the "old" BSD sort, originated from OpenBSD, there was no -2 option, as far
as I can see.
Oleg
-Original Message-
From: Oleg Moskalenko
Sent: Thursday, March 15, 2012 1:30 PM
To: 'Chris Rees'; Lowell Gilbert
Cc: Gabor Kovesdan; freebsd-ports@freebsd.org
Subject: RE: CFT: new BSD-lice
On 3/15/12 4:29 PM, Michael Scheidell wrote:
# $FreeBSD: ports/security/swatch/files/swatch.in,v 1.7 2012/01/14
08:56:53 dougb Exp $
or this one?
# $FreeBSD: ports/security/swatch/files/swatch.in,v 1.8 2012/02/10
14:37:30 scheidell Exp $
sb swatch 3.2.3_2
--
Michael Scheidell, CTO
>
On 3/15/12 4:24 PM, Chris Widger wrote:
There's a bug in the rc script for /usr/ports/securit/swatch
With the bug swatch can be started, but getting status or stopping the
process' always fail.
To fix this bug I had to change:
procname=/usr/local/bin/perl
to:
procname=/usr/local/
There is no option "-2" in the new BSD sort or in the GNU sort. There is no
such option in Posix standard, too.
What is this option about, do we need to add something ?
Thanks
Oleg
-Original Message-
From: utis...@gmail.com [mailto:utis...@gmail.com] On Behalf Of Chris Rees
Sent: Thursd
There's a bug in the rc script for /usr/ports/securit/swatch
With the bug swatch can be started, but getting status or stopping the
process' always fail.
To fix this bug I had to change:
procname=/usr/local/bin/perl
to:
procname=/usr/local/bin/swatch
With this change all instances of
On 15 March 2012 19:18, Lowell Gilbert
wrote:
> Gabor Kovesdan writes:
>
>> some time ago I started writing a BSDL sort variant from scratch since
>> the OpenBSD version did not support multibyte locales and was hard to
>> modify. The development was a bit stalled but recently, Oleg
>> Moskalenko
I get a build failure on amd64:
-
/usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_'
can not be used when making a shared object; recompile with -fPIC
lapi.o: could not read symbols: Bad value
*** Error code 1
-
I
Gabor Kovesdan writes:
> some time ago I started writing a BSDL sort variant from scratch since
> the OpenBSD version did not support multibyte locales and was hard to
> modify. The development was a bit stalled but recently, Oleg
> Moskalenko showed interest in continuing
> this version and he
On Thu, 15 Mar 2012 11:28:31 -0500, Kurt Jaeger wrote:
As I've read your mail, I had a look at p0f 3. It looks doable.
I've been busy and didn't have a chance to reply earlier -- I look forward
to your work. I am preparing a test environment soon so I can push some
emails through one of o
Hi!
> Is anyone working on a port of p0f v3? It is much more accurate at
> detecting newer OSes. I have seen emails from 2008R2 servers get higher
> than normal SpamAssassin scores because it thought they were Windows XP,
> which is causing spam filter accuracy issues.
>
> I think this woul
On Wed, Mar 14, 2012 at 10:14:28PM +, Jonathan Anderson wrote:
>
> In fact, the runtime behaviour of the Debian "alternatives" system is simpler
> than that:
> http://segfault.in/2010/04/using-the-debian-alternatives-system/
>
> The custom Perl script with a config file is used to set up sym
(12/03/15 0:59), Gabor Kovesdan wrote:
Hi Folks,
some time ago I started writing a BSDL sort variant from scratch since
the OpenBSD version did not support multibyte locales and was hard to
modify. The development was a bit stalled but recently, Oleg Moskalenko
showed interest in continuing thi
Just put in a nice new port, dns/knot (as in NOT bind ... I think).
authoritative ONLY dns server. looks nice.
I have I386 and AMD64 tinderboxes, and am looking to see if this
compiles on sparc64, ppc, and or ia64.
(vendor README mentions special flags and configuration args for
'WITH_X86_64' wh
I (maintainer of security/openssh-portable) need one or two days to
review GSI patch and other patches which are available for openssh-5.9.
But repocopy security/openssh-portable to security/openssh-portable58
and upgrade security/openssh-portable to 5.9 sound reasonable for me.
Beginning from F
Cy,
If the option of splitting openssh into two ports means that one of those
ports is closer to the base system's openssh, and the base system's openssh
requires the FreeBSD patch-set, for base, then this is a commendable
suggestion. Otherwise, I would vote for one kit, subject of course to
Grze
On 03/14/2012 09:01 PM, Cy Schubert wrote:
In message<4f60ef46.2040...@acsalaska.net>, Mel Flynn writes:
Hello Cy,
On 3/14/2012 08:57, Cy Schubert wrote:
[snip]
What I propose to do is remove the GSSAPI
patch from security/openssh-portable and for those who need the GSSAPI
server key exchang
28 matches
Mail list logo
