On Sat, Apr 02, 2016 at 02:59:06PM +0200, Michael Grimm wrote:
> Baptiste Daroussin wrote:
> >
> > On Sat, Apr 02, 2016 at 02:42:06PM +0200, Michael Grimm wrote:
>
> >> 26 seconds for 74 ports within a jail and pkg-1.6.4:
> […]
> >> 309 seconds for the very same 74 ports within the very same jai
On 07.04.2016 01:40, Kevin Oberman wrote:
> On Wed, Apr 6, 2016 at 2:05 PM, tatoolz--- via freebsd-ports
> mailto:freebsd-ports@freebsd.org>> wrote:
>
> I use FreeBSD 10.3 on AMD64.
> When i will install x11/tint, stop with this error:
> [ 21%] Building C object
> src/tint2conf/CM
On Wed, Apr 6, 2016 at 2:05 PM, tatoolz--- via freebsd-ports <
freebsd-ports@freebsd.org> wrote:
> I use FreeBSD 10.3 on AMD64.
> When i will install x11/tint, stop with this error:
> [ 21%] Building C object
> src/tint2conf/CMakeFiles/tint2conf.dir/__/util/common.c.oIn file included
> from
> /usr
I use FreeBSD 10.3 on AMD64.
When i will install x11/tint, stop with this error:
[ 21%] Building C object
src/tint2conf/CMakeFiles/tint2conf.dir/__/util/common.c.oIn file included from
/usr/ports/x11/tint/work/tint2-0.12.7/src/server.c:28:/usr/ports/x11/tint/work/tint2-0.12.7/src/server.h:17:10:
Hi!
> > a new release of Pan is available:
> >
> > http://pan.rebelbase.com/download/releases/0.140/source/
> >
> > How can I trigger the maintainer to update the FreeBSD port of Pan?
>
> The best approach is providing a patch and submitting it
> via bugs.freebsd.org, probably with a changelog
Hi!
> a new release of Pan is available:
>
> http://pan.rebelbase.com/download/releases/0.140/source/
>
> How can I trigger the maintainer to update the FreeBSD port of Pan?
The best approach is providing a patch and submitting it
via bugs.freebsd.org, probably with a changelog about it ?
--
Jim Ohlstein wrote:
Hello,
On 4/6/16 12:39 PM, Mathieu Arnold wrote:
+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein wrote:
| Hello,
|
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold wrote:
|>
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein wrote:
|> | Hello,
|> |
|> | On 4/6/16 12:44 AM, Ku
Kurt Jaeger wrote:
Hi!
This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
for just this purpose and is used in many ports.
In 9.x this is sometimes a problem, if port X builds in variant 1
and port Y depends/links on X, but builds in variant 2. So it's
a temporary solution
Hello,
On 4/6/16 12:39 PM, Mathieu Arnold wrote:
+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein wrote:
| Hello,
|
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold wrote:
|>
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein wrote:
|> | Hello,
|> |
|> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> |
+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein wrote:
| Hello,
|
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold wrote:
|>
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein wrote:
|> | Hello,
|> |
|> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> |> Hi!
|> |>
|> |>> Actually, I just noticed (whe
## Kurt Jaeger (li...@opsec.eu):
> In 9.x this is sometimes a problem, if port X builds in variant 1
> and port Y depends/links on X, but builds in variant 2. So it's
> a temporary solution for 9.x and will be solved when 9.x is EOL'ed.
We have also seen that problem on 10.x:
https://lists.freebs
Hello,
> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold wrote:
>
> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein wrote:
> | Hello,
> |
> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
> |> Hi!
> |>
> |>> Actually, I just noticed (when compiling the port), that the Makefile
> |>> now says:
> |>>
> |>
+--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein wrote:
| Hello,
|
| On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> Hi!
|>
|>> Actually, I just noticed (when compiling the port), that the Makefile
|>> now says:
|>>
|>> WITH_OPENSSL_PORT=yes
|>
|> Yes, sorry, my fault. Fixed, and as suggested by mat:
On 2016/04/06 16:05, Jim Ohlstein wrote:
> Hello,
>
>> On Apr 6, 2016, at 10:47 AM, Kurt Jaeger wrote:
>>
>> Hi!
>>
>>> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
>>> for just this purpose and is used in many ports.
>>
>> In 9.x this is sometimes a problem, if port X
Hello,
> On Apr 6, 2016, at 10:47 AM, Kurt Jaeger wrote:
>
> Hi!
>
>> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
>> for just this purpose and is used in many ports.
>
> In 9.x this is sometimes a problem, if port X builds in variant 1
> and port Y depends/links on
Hi!
> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
> for just this purpose and is used in many ports.
In 9.x this is sometimes a problem, if port X builds in variant 1
and port Y depends/links on X, but builds in variant 2. So it's
a temporary solution for 9.x and will
Hello,
On 4/6/16 12:44 AM, Kurt Jaeger wrote:
Hi!
Actually, I just noticed (when compiling the port), that the Makefile now says:
WITH_OPENSSL_PORT=yes
Yes, sorry, my fault. Fixed, and as suggested by mat: It is
now as IGNORE with a message explaining how to do it for 9.x.
This is much a
+--On 6 avril 2016 07:33:50 +0200 Michelle Sullivan
wrote:
| Kurt Jaeger wrote:
|> Hi!
|>
|>> Actually, I just noticed (when compiling the port), that the Makefile
|>> now says:
|>>
|>> WITH_OPENSSL_PORT=yes
|> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> now as IGNORE with a
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
19 matches
Mail list logo