Kevin Oberman writes:
> On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote:
>
>> With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
>> expected, ports/ is going to be essentially unusable for a while.
>>
>> The issue stems from configure scripts (to choose something completel
> It just means that folks didn't plan ahead and didn't think up
> proper contingency plans.
First off, apologies to Garrett, I'm not picking on you directly, but I
kinda knew this would come up.
The undeniable fact is that configure scripts in general have chosen to
do things a certain way. Un
On Mon, Sep 26, 2011 at 9:56 PM, Kevin Oberman wrote:
> On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote:
>> With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
>> expected, ports/ is going to be essentially unusable for a while.
>>
>> The issue stems from configure scripts (
On Mon, Sep 26, 2011 at 10:15 PM, Kevin Oberman wrote:
> On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote:
>> It's not the FreeBSD dev's fault. Unfortunately the autotools folks
>> were microoptimizing and didn't consider that the future would come
>> sooner than it actually did.
>
> First,
On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote:
> It's not the FreeBSD dev's fault. Unfortunately the autotools folks
> were microoptimizing and didn't consider that the future would come
> sooner than it actually did.
Garrett,
First, I'm not complaining or criticizing any of the develop
On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote:
> With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
> expected, ports/ is going to be essentially unusable for a while.
>
> The issue stems from configure scripts (to choose something completely
> at random) assuming that Fre
With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
expected, ports/ is going to be essentially unusable for a while.
The issue stems from configure scripts (to choose something completely
at random) assuming that FreeBSD would never jump to a double-digit
major version number,
On (09/26/11 22:11), Ruslan Mahmatkhanov wrote:
> Problem confirmed and solution is confirmed too. Thanks a lot.
>
> I checked other options and all is fine with them, the problem is only
> in WITH_SSH, so i think your patch is sufficient. This pr is submitted:
>
> http://bugs.freebsd.org/161039
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/26/11 11:25, Chris Rees wrote:
> On 26 September 2011 11:55, Rainer Hurling
> wrote:
>> This morning I tried to upgrade my ports after installing the new
>> 10-CURRENT (amd64).
>>
>> Unfortunately now I am not able to build ports using shared
Hi Chris,
On 26.09.2011 20:25 (UTC+2), Chris Rees wrote:
On 26 September 2011 11:55, Rainer Hurling wrote:
This morning I tried to upgrade my ports after installing the new 10-CURRENT
(amd64).
Unfortunately now I am not able to build ports using shared libraries like
ports/libXext any more. T
On 26 September 2011 11:55, Rainer Hurling wrote:
> This morning I tried to upgrade my ports after installing the new 10-CURRENT
> (amd64).
>
> Unfortunately now I am not able to build ports using shared libraries like
> ports/libXext any more. They only build .a and .la files, but not .so ones.
>
Problem confirmed and solution is confirmed too. Thanks a lot.
I checked other options and all is fine with them, the problem is only
in WITH_SSH, so i think your patch is sufficient. This pr is submitted:
http://bugs.freebsd.org/161039
Ryan, may be you can get it, since you touched it recent
On 26 September 2011 09:27, Thomas Mueller wrote:
> from Michael Holmes :
>
>> HAL shouldn't be necessary, but you might need to manually set up
>> CUPS. Winemaker is just a tool for building open-source Windows apps
>> on Wine with ease. There are a few GUI tools to set up CUPS, but if I
>> recal
Please note that all the consumers were handled,
so i submitted this pr:
http://bugs.freebsd.org/161038
Thank you all for working on this.
Ruslan Mahmatkhanov wrote on 30.08.2011 08:14:
Baptiste Daroussin wrote on 30.08.2011 01:48:
They may be safely removed after all of this guys will be co
This port fails to build with:
===> gtkextra-2.1.2 Bad autotool stanza: libtool:22.
*** Error code 1
Stop in /usr/ports/x11-toolkits/gtkextra2.
Libtool big and scary; anyone want to have a quick look?
Robert Huff
__
Meant to CC ports.
- Forwarded message from Jason Hellenthal -
Date: Mon, 26 Sep 2011 10:43:59 -0400
From: Jason Hellenthal
To: cvs-...@yandex.ru
Subject: security/hydra 7.0 add include path.
When building the new hydra with options WITH_SSH you need to add
/usr/local/include to the
On Mon, 26 Sep 2011 08:40:06 -0400
b. f. articulated:
> On 9/26/11, Stephen Montgomery-Smith wrote:
> > On 09/25/2011 08:19 PM, Jerry wrote:
> >> When attempting to build the "math/fftw3" port, the following error
> >> message is immediately displayed and the build halted:
> >>
> >>Variable C
On 9/26/11, Stephen Montgomery-Smith wrote:
> On 09/25/2011 08:19 PM, Jerry wrote:
>> When attempting to build the "math/fftw3" port, the following error
>> message is immediately displayed and the build halted:
>>
>> Variable CFLAGS is recursive.
...
> I am unable to reproduce this problem.
On 09/25/2011 08:19 PM, Jerry wrote:
When attempting to build the "math/fftw3" port, the following error
message is immediately displayed and the build halted:
Variable CFLAGS is recursive.
I have filed a PR against it.
I am unable to reproduce this problem. Is it possible that so
Selon Warren Block le lun 26 sep 06:01:13 2011 :
Recent discussion here about the desirability of replacing procmail
finally convinced me to switch to maildrop. It turned out to be
relatively painless. I took some notes that may be helpful for
others considering the change:
http://www
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
No matches t
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
This morning I tried to upgrade my ports after installing the new
10-CURRENT (amd64).
Unfortunately now I am not able to build ports using shared libraries
like ports/libXext any more. They only build .a and .la files, but not
.so ones.
Is it possible that there is something wrong now with l
On Mon, Sep 26, 2011 at 12:01:47PM +0200, Erwin Lansing wrote:
>> When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-)
> Later today. Running a test run as we speak :-)
What about INDEX-9, DESCRIBE.9 / INDEX-10, DESCRIBE.10 for portsnap?
--
Adios
___
On Sep 26, 2011, at 11:32 AM, Sergey V. Dyatko wrote:
> Hi Erwin,
>
Hi Sergey,
> When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-)
>
Later today. Running a test run as we speak :-)
Erwin
___
freebsd-ports@freebsd.org mailing
Hi Erwin,
When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-)
laptop# make fetchindex -C /usr/ports/
fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: Not Found
*** Error code 1
Stop in /usr/ports.
--
wbr, tiger
___
freebsd-ports
On Mon, 26 Sep 2011 04:16:01 -0500
"Matthew D. Fuller" wrote:
> On Mon, Sep 26, 2011 at 04:07:31AM -0500 I heard the voice of
> Conrad J. Sabatier, and lo! it spake thus:
> >
> > OK, I'm starting to get a little better of an idea of what to do.
> > My main concern so far has been the ability to n
On Mon, 26 Sep 2011 03:45:17 -0500
"Matthew D. Fuller" wrote:
> On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of
> Conrad J. Sabatier, and lo! it spake thus:
> >
> > I'm just wondering, though, if you could offer any advice on how to
> > convert something like the following procmail
On Mon, Sep 26, 2011 at 04:07:31AM -0500 I heard the voice of
Conrad J. Sabatier, and lo! it spake thus:
>
> OK, I'm starting to get a little better of an idea of what to do.
> My main concern so far has been the ability to nest a set of
> commands within a recipe the way procmail allows.
Well, it
On Mon, 26 Sep 2011 03:45:17 -0500
"Matthew D. Fuller" wrote:
> On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of
> Conrad J. Sabatier, and lo! it spake thus:
> >
> > I'm just wondering, though, if you could offer any advice on how to
> > convert something like the following procmail
On Mon, Sep 26, 2011 at 02:43:50AM -0500 I heard the voice of
Conrad J. Sabatier, and lo! it spake thus:
>
> I'm just wondering, though, if you could offer any advice on how to
> convert something like the following procmail recipe I use for my
> FreeBSD mailing lists.
I work off the envelope sen
On Mon, 2011-09-26 at 14:54 +0800, wen heping wrote:
> Hi,
>
>The build failed and below is the error message.
>Would you fix it ? Thanks.
>
> wen
>
>
Ok this is fixed in the attached patch.
>
> ===> Building package for ossec-hids-client-2.6
from Michael Holmes :
> HAL shouldn't be necessary, but you might need to manually set up
> CUPS. Winemaker is just a tool for building open-source Windows apps
> on Wine with ease. There are a few GUI tools to set up CUPS, but if I
> recall correctly, the web interface to CUPS is pretty
> self-ex
On Sun, 25 Sep 2011 22:01:13 -0600 (MDT)
Warren Block wrote:
> Recent discussion here about the desirability of replacing procmail
> finally convinced me to switch to maildrop. It turned out to be
> relatively painless. I took some notes that may be helpful for
> others considering the change
Hi,
The build failed and below is the error message.
Would you fix it ? Thanks.
wen
building ossec-hids-client-2.6_1 in directory /usr/local/tinderbox/9.0-FreeBSD
build started at Mon Sep 26 03:28:48 UTC 2011
port directory: /usr/ports/security/ossec-hids-client
building for: 9.0-CURRE
35 matches
Mail list logo
