On 08/19/2011 16:40, Doug Barton wrote:
This is on 7.x i386. Builds fine, and passes all self-tests.
Thanks,
Doug
( cd PerlMagick gmake CC='cc -std=gnu99 -std=gnu99' \
gmake CC='cc -std=gnu99 -std=gnu99' install )
gmake[3]: Entering directory
On 20 August 2011 08:25, Thomas Zander ri...@rrr.de wrote:
On Fri, Aug 19, 2011 at 22:19, Christian Weisgerber na...@freebsd.org wrote:
I mean just add an unconditional CONFIGURE_ARGS+=--disable-faad
instead of yet another option nobody needs.
I agree. There is no reason to pull in external
On 20 August 2011 05:47, per...@pluto.rain.com wrote:
I've been running it for a little less than
two days now, on a drive which contains a gmirror, and have yet
to see it misbehave. (The HDD indicator does stay on, but this is
not surprising given that, as noted above, diskcheckd is
Hi,
I would like to propose a change to bsd.port.mk which, similarly to
obtaining the OSVERSION, checks if the system on which a port is being
built is a jailed environment.
This change can allow port maintainers to mark ports that do not run in
jailed environments as IGNORE, or adjust
On Sat, Aug 20, 2011 at 07:09:49AM -0400, Glen Barber wrote:
Hi,
I would like to propose a change to bsd.port.mk which, similarly to
obtaining the OSVERSION, checks if the system on which a port is being
built is a jailed environment.
This change can allow port maintainers to mark ports
On 8/20/11 7:52 AM, Kostik Belousov wrote:
On Sat, Aug 20, 2011 at 07:09:49AM -0400, Glen Barber wrote:
Hi,
I would like to propose a change to bsd.port.mk which, similarly to
obtaining the OSVERSION, checks if the system on which a port is being
built is a jailed environment.
This change
On Sat, Aug 20, 2011 at 08:16:09AM -0400, Glen Barber wrote:
On 8/20/11 7:52 AM, Kostik Belousov wrote:
On Sat, Aug 20, 2011 at 07:09:49AM -0400, Glen Barber wrote:
Hi,
I would like to propose a change to bsd.port.mk which, similarly to
obtaining the OSVERSION, checks if the system on
On 8/20/11 8:44 AM, Kostik Belousov wrote:
One thing I can think of off-hand to fix this in that case is setting a
local environment variable to disable a check for security.jail.jailed.
Would this be an ok solution for those cases? If not, I happily agree
that this change should not be made
On 8/20/11 8:44 AM, Kostik Belousov wrote:
One thing I can think of off-hand to fix this in that case is setting a
local environment variable to disable a check for security.jail.jailed.
Would this be an ok solution for those cases? If not, I happily agree
that this change should not be
On 20 August 2011 18:46, Jason Helfman jhelf...@e-e.com wrote:
On 8/20/11 8:44 AM, Kostik Belousov wrote:
One thing I can think of off-hand to fix this in that case is setting a
local environment variable to disable a check for security.jail.jailed.
Would this be an ok solution for those
On Fri, Aug 19, 2011 at 2:39 AM, Patrick Ian pransp...@gmail.com wrote:
Hey,
I would like to use the chromedriver target from the chromium port.
However, I do not know how to add that target to my local ports
chromium configuration. How do I make the chromedriver target?
--
-Patrick
Chris Rees utis...@gmail.com wrote:
Is it logging to syslog?
I haven't seen anything in /var/log/messages or on ttyv0, but
this may be a matter of configuration rather than a problem with
diskcheckd.
* I'm running diskcheckd as a normal user, not as root. (The user
is in the operator group
On Fri, Aug 19, 2011 at 09:47:33PM -0700, per...@pluto.rain.com wrote:
If it's OK to close a PR without fixing it, because no one seems
interested, maybe we should just close 143566 and be done with it
No, we're really not trying to do that.
I keep trying to communicate to PR submitters that
13 matches
Mail list logo
