Re: OPTIONS handling doesn't seem to work fully in dependencies anymore

2008-09-18 Thread Alex Dupre 

John Baldwin ha scritto:

It used to work.


I was thinking the same thing, but actually it never worked in that way.

I was just guessing about how it might not be working now 
based on reading the existing logic.  I have not delved into the history to 
see what has changed.


The attached patch should solve this erratic behavior.

--
Alex Dupre
--- bsd.port.mk.orig2008-09-18 10:31:14.0 +0200
+++ bsd.port.mk 2008-09-18 10:46:02.0 +0200
@@ -3234,7 +3234,7 @@
 # target or not.
 #
 
-.if (!defined(OPTIONS) || defined(CONFIG_DONE) || \
+.if (!defined(OPTIONS) || defined(CONFIG_DONE_${UNIQUENAME:U}) || \
defined(PACKAGE_BUILDING) || defined(BATCH))
 _OPTIONS_OK=yes
 .endif
@@ -4169,7 +4169,7 @@
 ${target}: ${${target:U}_COOKIE}
 .elif !target(${target})
 ${target}: config-conditional
-   @cd ${.CURDIR} && ${MAKE} CONFIG_DONE=1 ${__softMAKEFLAGS} 
${${target:U}_COOKIE}
+   @cd ${.CURDIR} && ${MAKE} CONFIG_DONE_${UNIQUENAME:U}=1 
${__softMAKEFLAGS} ${${target:U}_COOKIE}
 .elif target(${target}) && defined(IGNORE)
 .endif
 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread David Booth 
On Wednesday 17 September 2008, Snopy Land wrote:
> Hi,
>
> My server version is freebsd6.2 amd64. I have installed clamav to
> scan my incoming mail. Everything works smoothly for several years.
> Recently, I need to upgrade clamav version from 0.92 to 0.94
> (latest version). Actually, I had done this upgrade clamav process
> before. My procedures is :
>
> 1. run "make deinstall" to deinstall the clamav version of 0.92
> 2. Modify /usr/ports-supfile  (to make sure security port can be
> download from a correct default host)
> *default host=ftp.tw.freebsd.org
> ports-security   <--- remark ports-all, and enable the
> ports-security only 3. cd /usr ; run "cvsup -g -L 2 ports-supfile
> 4. check /usr/port/security/clamav port is updated
> 5. cd /usr/port/security/clamav
> 6. run "make install clean"
>
> There is no error message found in the whole process, however, I
> cannot find the file of "clamd", "clamscan" & "freshclam".
> The previous version of these file can be found in /usr/local/sbin
> and /usr/local/bin
>
> Anyone have encoutered the same problem ? I am not sure whether my
> posting is put in the correct mailling list.
> Any comments are appreciated.
>
> Thanks.
They should still be in /usr/local/sbin and /usr/local/bin.  Does the 
new version of the port show as installed?  What does

ls /var/db/pkg | grep clam

show?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

teTeX/TeXLive: powerdot still missing ...

2008-09-18 Thread O. Hartmann 
Still using teTeX, but as we all know, development has been canceld by 
Thomas Esser. I'm looking for a working 'powerdot' which is part of 
TeXLive now, but there is no TeXLive-port available for FreeBSD. 
Searching for that matter brings up some informations released a year 
ago and I'm wondering about the fact that there is no support for FreeBSD.
Is there a workaround or 'master plan' how to bring TeXLive to a FreeBSD 
bx in a clean way? Can TeXLive coexists with teTeX.


Thank you very much for your patience ...

Regards,
Oliver
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[RELENG_6]apr-db configure warnings ... what the heck is this stuff?

2008-09-18 Thread Sean Bruno 
Updated my ports tree this morning to build freebsd-subversion and this 
popped up during my build:


===>  Configuring for apr-db42-1.3.3.1.3.4
cd /usr/ports/devel/apr-svn/work/apr-1.3.3 ;  /usr/bin/env 
PYTHON="/usr/local/bin/python2.4" SHELL=/bin/sh CONFIG_SHELL=/bin/sh 
MAKE=gmake ACLOCAL=/usr/local/bin/aclocal-1.9 
AUTOMAKE=/usr/local/bin/automake-1.9 AUTOMAKE_VERSION=19 
AUTOCONF=/usr/local/bin/autoconf-2.62 
AUTOHEADER=/usr/local/bin/autoheader-2.62 
AUTOIFNAMES=/usr/local/bin/ifnames-2.62 
AUTOM4TE=/usr/local/bin/autom4te-2.62 
AUTORECONF=/usr/local/bin/autoreconf-2.62 
AUTOSCAN=/usr/local/bin/autoscan-2.62 
AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262 
LIBTOOL=/usr/local/bin/libtool LIBTOOLIZE=/usr/local/bin/libtoolize 
LIBTOOL_M4=/usr/local/share/aclocal/libtool.m4 
lt_cv_sys_max_cmd_len=262144 /bin/sh ./buildconf

buildconf: checking installation...
buildconf: python version 2.4.3 (ok)
buildconf: autoconf version 2.62 (ok)
buildconf: libtool version 1.5.22 (ok)
Copying libtool helper files ...
buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4.
Creating include/arch/unix/apr_private.h.in ...
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, 
...): suspicious cache-id, must contain _cv_ to be cached

autoconf/general.m4:1987: AC_CACHE_VAL is expanded from...
autoconf/general.m4:2000: AC_CACHE_CHECK is expanded from...
build/libtool.m4:653: AC_LIBTOOL_COMPILER_OPTION is expanded from...
build/libtool.m4:5336: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
build/libtool.m4:2723: _LT_AC_LANG_C_CONFIG is expanded from...
build/libtool.m4:2650: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
build/libtool.m4:220: AC_LIBTOOL_SETUP is expanded from...
build/libtool.m4:75: _AC_PROG_LIBTOOL is expanded from...
build/libtool.m4:55: AC_PROG_LIBTOOL is expanded from...
configure.in:186: the top level
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_static_works, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:690: AC_LIBTOOL_LINKER_OPTION is expanded from...
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:3731: _LT_AC_LANG_CXX_CONFIG is expanded from...
build/libtool.m4:2731: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
build/libtool.m4:1886: _LT_AC_TAGCONFIG is expanded from...
configure.in:186: warning: 
AC_CACHE_VAL(lt_prog_compiler_static_works_CXX, ...): suspicious 
cache-id, must contain _cv_ to be cached
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_F77, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:3992: _LT_AC_LANG_F77_CONFIG is expanded from...
build/libtool.m4:3898: AC_LIBTOOL_LANG_F77_CONFIG is expanded from...
configure.in:186: warning: 
AC_CACHE_VAL(lt_prog_compiler_static_works_F77, ...): suspicious 
cache-id, must contain _cv_ to be cached
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_GCJ, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:4052: _LT_AC_LANG_GCJ_CONFIG is expanded from...
build/libtool.m4:4000: AC_LIBTOOL_LANG_GCJ_CONFIG is expanded from...
configure.in:186: warning: 
AC_CACHE_VAL(lt_prog_compiler_static_works_GCJ, ...): suspicious 
cache-id, must contain _cv_ to be cached

Creating configure ...
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, 
...): suspicious cache-id, must contain _cv_ to be cached

autoconf/general.m4:1987: AC_CACHE_VAL is expanded from...
autoconf/general.m4:2000: AC_CACHE_CHECK is expanded from...
build/libtool.m4:653: AC_LIBTOOL_COMPILER_OPTION is expanded from...
build/libtool.m4:5336: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
build/libtool.m4:2723: _LT_AC_LANG_C_CONFIG is expanded from...
build/libtool.m4:2650: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
build/libtool.m4:220: AC_LIBTOOL_SETUP is expanded from...
build/libtool.m4:75: _AC_PROG_LIBTOOL is expanded from...
build/libtool.m4:55: AC_PROG_LIBTOOL is expanded from...
configure.in:186: the top level
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_static_works, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:690: AC_LIBTOOL_LINKER_OPTION is expanded from...
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:3731: _LT_AC_LANG_CXX_CONFIG is expanded from...
build/libtool.m4:2731: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
build/libtool.m4:1886: _LT_AC_TAGCONFIG is expanded from...
configure.in:186: warning: 
AC_CACHE_VAL(lt_prog_compiler_static_works_CXX, ...): suspicious 
cache-id, must contain _cv_ to be cached
configure.in:186: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_F77, 
...): suspicious cache-id, must contain _cv_ to be cached

build/libtool.m4:3992: _LT_AC_LANG_F77_CONFIG is expanded from...
build/libtool.m4:3898: AC_LIBTOOL_LANG_F7

Error building print/ghostscript8

2008-09-18 Thread Doug Barton 
Anyone else seeing this?

cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr
./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm  -liconv
-lstdc++  -L/usr/local/lib -lfontconfig   -Wl,-export-dynamic -lm
if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \
XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \
FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \
DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \
DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \
DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \
DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \
DEVICE_DEVS_EXTRA= \
/bin/sh <./obj/../soobj/ldt.tr
./obj/../soobj/gdevl256.o(.text+0x7b0): In function `gs_shared_init':
./src/gdevl256.c:312: multiple definition of `gs_shared_init'
./obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
defined here
/usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150
in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o
./obj/../soobj/gdevvglb.o(.text+0xa10): In function `gs_shared_init':
./src/gdevvglb.c:379: multiple definition of `gs_shared_init'
./obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
defined here
gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1
gmake[1]: Leaving directory
`/usr/ports/print/ghostscript8/work/ghostscript-8.62'
gmake: *** [so] Error 2
*** Error code 2


-- 

This .signature sanitized for your protection

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: OPTIONS handling doesn't seem to work fully in dependencies anymore

2008-09-18 Thread John Baldwin 
On Thursday 18 September 2008 04:51:11 am Alex Dupre wrote:
> John Baldwin ha scritto:
> > It used to work.
> 
> I was thinking the same thing, but actually it never worked in that way.

Trust me, since I rebuild from scratch all the time, I quite remember when 
options were first added and I'd kick off a build of kde or some such 
overnight and check my screen session in the morning only find it hadn't 
build hardly anything b/c it had popped up the option screen for gettext. :)

> > I was just guessing about how it might not be working now 
> > based on reading the existing logic.  I have not delved into the history 
to 
> > see what has changed.
> 
> The attached patch should solve this erratic behavior.

I wonder why it has to be this hackish btw.  Could config-conditional simply 
be in the list of targets before 'fetch' or some such?

-- 
John Baldwin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Error building print/ghostscript8

2008-09-18 Thread Max Brazhnikov 
On Thu, 18 Sep 2008 11:04:06 -0700, Doug Barton wrote:
> Anyone else seeing this?
>
> cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr
> ../obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm  -liconv
> -lstdc++  -L/usr/local/lib -lfontconfig   -Wl,-export-dynamic -lm
> if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \
>   XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \
>   FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \
>   DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \
>   DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \
>   DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \
>   DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \
>   DEVICE_DEVS_EXTRA= \
>   /bin/sh <./obj/../soobj/ldt.tr
> ../obj/../soobj/gdevl256.o(.text+0x7b0): In function `gs_shared_init':
> ../src/gdevl256.c:312: multiple definition of `gs_shared_init'
> ../obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
> defined here
> /usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150
> in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o
> ../obj/../soobj/gdevvglb.o(.text+0xa10): In function `gs_shared_init':
> ../src/gdevvglb.c:379: multiple definition of `gs_shared_init'
> ../obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
> defined here
> gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1
> gmake[1]: Leaving directory
> `/usr/ports/print/ghostscript8/work/ghostscript-8.62'
> gmake: *** [so] Error 2
> *** Error code 2

Yes, see http://www.freebsd.org/cgi/query-pr.cgi?pr=115593 with similar 
problem.

Max
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: OPTIONS handling doesn't seem to work fully in dependencies anymore

2008-09-18 Thread Alex Dupre 

John Baldwin wrote:
Trust me, since I rebuild from scratch all the time, I quite remember when 
options were first added and I'd kick off a build of kde or some such 
overnight and check my screen session in the morning only find it hadn't 
build hardly anything b/c it had popped up the option screen for gettext. :)


Me, too, really :-) But kde3 meta-port doesn't use the OPTIONS 
framework, even if it displays the dialog box. And when the OPTIONS 
framework was added, very few ports actually used it, so it was very 
very rare to incur in *direct* dependencies between two OPTIONS-enabled 
ports. The kde4 meta-port now uses it, so it became obvious that 
something wasn't working as expected when you tried to build it.


I wonder why it has to be this hackish btw.  Could config-conditional simply 
be in the list of targets before 'fetch' or some such?


I thought the same thing, probably yes, but I dunno why it was added in 
such way from the beginning, so I tried to create the simplest and 
surely working patch maintaining the current workflow.


--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Error building print/ghostscript8

2008-09-18 Thread Doug Barton 
Max Brazhnikov wrote:
> On Thu, 18 Sep 2008 11:04:06 -0700, Doug Barton wrote:
>> Anyone else seeing this?
>>
>> cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr
>> ../obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm  -liconv
>> -lstdc++  -L/usr/local/lib -lfontconfig   -Wl,-export-dynamic -lm
>> if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \
>>  XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \
>>  FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \
>>  DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \
>>  DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \
>>  DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \
>>  DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \
>>  DEVICE_DEVS_EXTRA= \
>>  /bin/sh <./obj/../soobj/ldt.tr
>> ../obj/../soobj/gdevl256.o(.text+0x7b0): In function `gs_shared_init':
>> ../src/gdevl256.c:312: multiple definition of `gs_shared_init'
>> ../obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
>> defined here
>> /usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150
>> in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o
>> ../obj/../soobj/gdevvglb.o(.text+0xa10): In function `gs_shared_init':
>> ../src/gdevvglb.c:379: multiple definition of `gs_shared_init'
>> ../obj/../soobj/gdevxalt.o(.text+0x1830):./src/gdevxalt.c:851: first
>> defined here
>> gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1
>> gmake[1]: Leaving directory
>> `/usr/ports/print/ghostscript8/work/ghostscript-8.62'
>> gmake: *** [so] Error 2
>> *** Error code 2
> 
> Yes, see http://www.freebsd.org/cgi/query-pr.cgi?pr=115593 with similar 
> problem.

Removing svgalib from the config options got it building, thanks.

Doug

-- 

This .signature sanitized for your protection

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: port: security/cfs

2008-09-18 Thread Christopher Sean Hilton 

On Sep 17, 2008, at 7:52 PM, Edwin Groothuis wrote:

On Wed, Sep 17, 2008 at 06:38:56PM -0400, Christopher Sean Hilton  
wrote:
The port security/cfs, Matt Blaze's userland Cryptographic  
filesystem,

is marked as broken because it does not compile under FreeBSD-7.0 or
later.


ports/127457



Thanks for the patch once I recognized that it was against existing  
patches in the ports files directory it went smoothly.


-- Chris

--
Chris Hilton   chris-at-vindaloo-dot-com

   "All I was doing was trying to get home from work!"
-- Rosa Parks

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: OPTIONS handling doesn't seem to work fully in dependencies anymore

2008-09-18 Thread John Baldwin 
On Thursday 18 September 2008 03:18:17 pm Alex Dupre wrote:
> John Baldwin wrote:
> > Trust me, since I rebuild from scratch all the time, I quite remember when 
> > options were first added and I'd kick off a build of kde or some such 
> > overnight and check my screen session in the morning only find it hadn't 
> > build hardly anything b/c it had popped up the option screen for 
gettext. :)
> 
> Me, too, really :-) But kde3 meta-port doesn't use the OPTIONS 
> framework, even if it displays the dialog box. And when the OPTIONS 
> framework was added, very few ports actually used it, so it was very 
> very rare to incur in *direct* dependencies between two OPTIONS-enabled 
> ports. The kde4 meta-port now uses it, so it became obvious that 
> something wasn't working as expected when you tried to build it.

Ahh, I think I see now.  It requires one OPTIONS using port to mask the 
dependencies.

> > I wonder why it has to be this hackish btw.  Could config-conditional 
simply 
> > be in the list of targets before 'fetch' or some such?
> 
> I thought the same thing, probably yes, but I dunno why it was added in 
> such way from the beginning, so I tried to create the simplest and 
> surely working patch maintaining the current workflow.

Ok.

-- 
John Baldwin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail

2008-09-18 Thread Alexander Churanov 
2008/9/18 Mark Linimon <[EMAIL PROTECTED]>

> For future reference, the address to contact with issues with
> maintainers is [EMAIL PROTECTED]  I've already forwarded your email
> to [EMAIL PROTECTED]
>
> mcl
>
OK, Thank you
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread Eric L. Chen 
I am using cvsup3.tw.FreeBSD.org, no any problem.
> ls | grep clam
clamav-0.94_1
> which clamd
/usr/local/sbin/clamd

/Eric

On Thu, Sep 18, 2008 at 12:41 PM, Snopy Land <[EMAIL PROTECTED]> wrote:

> Hi,
>
> My server version is freebsd6.2 amd64. I have installed clamav to scan my
> incoming mail. Everything works smoothly for several years.
> Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest
> version). Actually, I had done this upgrade clamav process before.
> My procedures is :
>
> 1. run "make deinstall" to deinstall the clamav version of 0.92
> 2. Modify /usr/ports-supfile  (to make sure security port can be download
> from a correct default host)
> *default host=ftp.tw.freebsd.org
> ports-security   <--- remark ports-all, and enable the ports-security only
> 3. cd /usr ; run "cvsup -g -L 2 ports-supfile
> 4. check /usr/port/security/clamav port is updated
> 5. cd /usr/port/security/clamav
> 6. run "make install clean"
>
> There is no error message found in the whole process, however, I cannot
> find
> the file of "clamd", "clamscan" & "freshclam".
> The previous version of these file can be found in /usr/local/sbin and
> /usr/local/bin
>
> Anyone have encoutered the same problem ? I am not sure whether my posting
> is put in the correct mailling list.
> Any comments are appreciated.
>
> Thanks.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread Snopy Land 
Hi,

Thanks for your both reply.

I get clamav-0.94_1 when run "ls /var/db/pkg | grep clam"

Today, I have changed the default host to cvsup3.tw.FreeBSD.org and redo the
upgrade of clamav. I find the following message when I run "make install
clean"


Making install in clamscan
test -z "/usr/local/bin" || ../config/install-sh -c -d "/usr/local/bin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'clamscan' '/usr/local/bin/amd64-portbld-freebsd6.2-clamscan'
install -o root -g wheel -m 555 -s .libs/clamscan
/usr/local/bin/amd64-portbld-f
reebsd6.2-clamscan
Making install in clamd
test -z "/usr/local/sbin" || ../config/install-sh -c -d "/usr/local/sbin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'clamd' '/usr/local/sbin/amd64-portbld-freebsd6.2-clamd'
install -o root -g wheel -m 555 -s .libs/clamd
/usr/local/sbin/amd64-portbld-fre
ebsd6.2-clamd
Making install in clamdscan
test -z "/usr/local/bin" || ../config/install-sh -c -d "/usr/local/bin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'clamdscan' '/usr/local/bin/amd64-portbld-freebsd6.2-clamdscan'
install -o root -g wheel -m 555 -s clamdscan
/usr/local/bin/amd64-portbld-freebs
d6.2-clamdscan
Making install in freshclam
test -z "/usr/local/bin" || ../config/install-sh -c -d "/usr/local/bin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'freshclam' '/usr/local/bin/amd64-portbld-freebsd6.2-freshclam'
install -o root -g wheel -m 555 -s .libs/freshclam
/usr/local/bin/amd64-portbld-
freebsd6.2-freshclam
Making install in sigtool
test -z "/usr/local/bin" || ../config/install-sh -c -d "/usr/local/bin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'sigtool' '/usr/local/bin/amd64-portbld-freebsd6.2-sigtool'
install -o root -g wheel -m 555 -s .libs/sigtool
/usr/local/bin/amd64-portbld-fr
eebsd6.2-sigtool
Making install in clamconf
test -z "/usr/local/bin" || ../config/install-sh -c -d "/usr/local/bin"
  /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
wheel -
m 555 'clamconf' '/usr/local/bin/amd64-portbld-freebsd6.2-clamconf'
install -o root -g wheel -m 555 -s .libs/clamconf
/usr/local/bin/amd64-portbld-f
reebsd6.2-clamconf

And I find that there are some files under /usr/local/bin/ and
/usr/local/sbin

ls -ltr /usr/local/bin
-r-xr-xr-x  1 root  wheel80624 Sep 19 11:07
amd64-portbld-freebsd6.2-sigtool
-r-xr-xr-x  1 root  wheel87944 Sep 19 11:07
amd64-portbld-freebsd6.2-freshcl
am
-r-xr-xr-x  1 root  wheel51968 Sep 19 11:07
amd64-portbld-freebsd6.2-clamsca
n
-r-xr-xr-x  1 root  wheel52592 Sep 19 11:07
amd64-portbld-freebsd6.2-clamdsc
an
-r-xr-xr-x  1 root  wheel28272 Sep 19 11:07
amd64-portbld-freebsd6.2-clamcon
f
-r-xr-xr-x  1 root  wheel 1103 Sep 19 11:07
amd64-portbld-freebsd6.2-clamav-
config

ls -ltr /usr/local/sbin

-r-xr-xr-x  1 root  wheel67536 Sep 19 11:07
amd64-portbld-freebsd6.2-clamd

So I am not sure whether the file name has been changed.
It seems that this version of clamav can only provide the above files.
I have double checked that there is no clamd, clamscan & freshclam in
/usr/local/bin and /usr/local/sbin.

How can I know the ans. of these question ?

Any comment are appreciated.




On Fri, Sep 19, 2008 at 8:17 AM, Eric L. Chen <[EMAIL PROTECTED]> wrote:

> I am using cvsup3.tw.FreeBSD.org , no any
> problem.
> > ls | grep clam
> clamav-0.94_1
> > which clamd
> /usr/local/sbin/clamd
>
> /Eric
>
>   On Thu, Sep 18, 2008 at 12:41 PM, Snopy Land <[EMAIL PROTECTED]>wrote:
>
>>  Hi,
>>
>> My server version is freebsd6.2 amd64. I have installed clamav to scan my
>> incoming mail. Everything works smoothly for several years.
>> Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest
>> version). Actually, I had done this upgrade clamav process before.
>> My procedures is :
>>
>> 1. run "make deinstall" to deinstall the clamav version of 0.92
>> 2. Modify /usr/ports-supfile  (to make sure security port can be download
>> from a correct default host)
>> *default host=ftp.tw.freebsd.org
>> ports-security   <--- remark ports-all, and enable the ports-security only
>> 3. cd /usr ; run "cvsup -g -L 2 ports-supfile
>> 4. check /usr/port/security/clamav port is updated
>> 5. cd /usr/port/security/clamav
>> 6. run "make install clean"
>>
>> There is no error message found in the whole process, however, I cannot
>> find
>> the file of "clamd", "clamscan" & "freshclam".
>> The previous version of these file can be found in /usr/local/sbin and
>> /usr/local/bin
>>
>> Anyone have encoutered the same problem ? I am not sure whether my posting
>> is put in the correct mailling list.
>> Any comments are appreciated.
>>
>> Thanks.
>> ___
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-po

two ptmalloc ports

2008-09-18 Thread Stephen Montgomery-Smith 

There are two ports:

devel/ptmalloc
devel/ptmalloc2

They are identical!

Which one is the "true" port?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread David Booth 
On Thursday 18 September 2008, Snopy Land wrote:
> Hi,
>
> Thanks for your both reply.
>
> I get clamav-0.94_1 when run "ls /var/db/pkg | grep clam"
>
> Today, I have changed the default host to cvsup3.tw.FreeBSD.org and
> redo the upgrade of clamav. I find the following message when I run
> "make install clean"
>
>
> Making install in clamscan
> test -z "/usr/local/bin" || ../config/install-sh -c -d
> "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'clamscan' '/usr/local/bin/amd64-portbld-freebsd6.2-clamscan'
> install -o root -g wheel -m 555 -s .libs/clamscan
> /usr/local/bin/amd64-portbld-f
> reebsd6.2-clamscan
> Making install in clamd
> test -z "/usr/local/sbin" || ../config/install-sh -c -d
> "/usr/local/sbin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'clamd' '/usr/local/sbin/amd64-portbld-freebsd6.2-clamd'
> install -o root -g wheel -m 555 -s .libs/clamd
> /usr/local/sbin/amd64-portbld-fre
> ebsd6.2-clamd
> Making install in clamdscan
> test -z "/usr/local/bin" || ../config/install-sh -c -d
> "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'clamdscan'
> '/usr/local/bin/amd64-portbld-freebsd6.2-clamdscan' install -o root
> -g wheel -m 555 -s clamdscan
> /usr/local/bin/amd64-portbld-freebs
> d6.2-clamdscan
> Making install in freshclam
> test -z "/usr/local/bin" || ../config/install-sh -c -d
> "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'freshclam'
> '/usr/local/bin/amd64-portbld-freebsd6.2-freshclam' install -o root
> -g wheel -m 555 -s .libs/freshclam
> /usr/local/bin/amd64-portbld-
> freebsd6.2-freshclam
> Making install in sigtool
> test -z "/usr/local/bin" || ../config/install-sh -c -d
> "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'sigtool' '/usr/local/bin/amd64-portbld-freebsd6.2-sigtool'
> install -o root -g wheel -m 555 -s .libs/sigtool
> /usr/local/bin/amd64-portbld-fr
> eebsd6.2-sigtool
> Making install in clamconf
> test -z "/usr/local/bin" || ../config/install-sh -c -d
> "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> install  -s -o root -g wheel -
> m 555 'clamconf' '/usr/local/bin/amd64-portbld-freebsd6.2-clamconf'
> install -o root -g wheel -m 555 -s .libs/clamconf
> /usr/local/bin/amd64-portbld-f
> reebsd6.2-clamconf
>
> And I find that there are some files under /usr/local/bin/ and
> /usr/local/sbin
>
> ls -ltr /usr/local/bin
> -r-xr-xr-x  1 root  wheel80624 Sep 19 11:07
> amd64-portbld-freebsd6.2-sigtool
> -r-xr-xr-x  1 root  wheel87944 Sep 19 11:07
> amd64-portbld-freebsd6.2-freshcl
> am
> -r-xr-xr-x  1 root  wheel51968 Sep 19 11:07
> amd64-portbld-freebsd6.2-clamsca
> n
> -r-xr-xr-x  1 root  wheel52592 Sep 19 11:07
> amd64-portbld-freebsd6.2-clamdsc
> an
> -r-xr-xr-x  1 root  wheel28272 Sep 19 11:07
> amd64-portbld-freebsd6.2-clamcon
> f
> -r-xr-xr-x  1 root  wheel 1103 Sep 19 11:07
> amd64-portbld-freebsd6.2-clamav-
> config
>
> ls -ltr /usr/local/sbin
>
> -r-xr-xr-x  1 root  wheel67536 Sep 19 11:07
> amd64-portbld-freebsd6.2-clamd
>
> So I am not sure whether the file name has been changed.
> It seems that this version of clamav can only provide the above
> files. I have double checked that there is no clamd, clamscan &
> freshclam in /usr/local/bin and /usr/local/sbin.
>
> How can I know the ans. of these question ?
>
> Any comment are appreciated.
>
I do not have an amd64 system, so I cannot tell from my system if the 
names are changed, but looking at the port install log, it looks as 
if they are.  
There are a couple of things to check.

(1) is there a file in /usr/local/etc/rc.d/ called clamav-clamd ?

(2) If so, or you can identify what the equivalent file is on your 
system, what is on the 'command' line in the file.  Mine says

command=/usr/local/sbin/clamd


Does yours say

command=/usr/local/sbin/amd64-portbld-freebsd6.2-clamd

?

If so, then I would venture that that is the equivalent executable.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread Snopy Land 
Hi David,

Thanks for your prompt reply.

I have checked the files of "clamav-clamd" and "clamav-freshclam" under
/usr/local/etc/rc.d.

-r-xr-xr-x  1 root  wheel   722 Sep 19 11:07 clamav-freshclam
-r-xr-xr-x  1 root  wheel   974 Sep 19 11:07 clamav-clamd

The file date has been updated by today's upgrade process. However, the
command is still using clamd and freshclam

i.e. command=/usr/local/sbin/clamd<---clamav-clamd file
command=/usr/local/bin/freshclam<--clamav-freshclam file

So I worry that there may be some hidden problems if I run the
"amd64-portbid-freebsd6.2-clamd" instead of "clamd"

I will report this case to the admin of freebsd.org. Have you tried to send
mail to them before? I find that
[EMAIL PROTECTED]<[EMAIL 
PROTECTED]@FreeBSD.org&subject=FreeBSD%20Port:%20clamav-0.94_1>
maintains
the port of clamav from the port search of freebsd.org.

Any other suggestions ?

Thanks.




On Fri, Sep 19, 2008 at 12:29 PM, David Booth <[EMAIL PROTECTED]>wrote:

>  On Thursday 18 September 2008, Snopy Land wrote:
> > Hi,
> >
> > Thanks for your both reply.
> >
> > I get clamav-0.94_1 when run "ls /var/db/pkg | grep clam"
> >
> > Today, I have changed the default host to 
> > cvsup3.tw.FreeBSD.organd
> > redo the upgrade of clamav. I find the following message when I run
> > "make install clean"
> >
> >
> > Making install in clamscan
> > test -z "/usr/local/bin" || ../config/install-sh -c -d
> > "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'clamscan' '/usr/local/bin/amd64-portbld-freebsd6.2-clamscan'
> > install -o root -g wheel -m 555 -s .libs/clamscan
> > /usr/local/bin/amd64-portbld-f
> > reebsd6.2-clamscan
> > Making install in clamd
> > test -z "/usr/local/sbin" || ../config/install-sh -c -d
> > "/usr/local/sbin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'clamd' '/usr/local/sbin/amd64-portbld-freebsd6.2-clamd'
> > install -o root -g wheel -m 555 -s .libs/clamd
> > /usr/local/sbin/amd64-portbld-fre
> > ebsd6.2-clamd
> > Making install in clamdscan
> > test -z "/usr/local/bin" || ../config/install-sh -c -d
> > "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'clamdscan'
> > '/usr/local/bin/amd64-portbld-freebsd6.2-clamdscan' install -o root
> > -g wheel -m 555 -s clamdscan
> > /usr/local/bin/amd64-portbld-freebs
> > d6.2-clamdscan
> > Making install in freshclam
> > test -z "/usr/local/bin" || ../config/install-sh -c -d
> > "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'freshclam'
> > '/usr/local/bin/amd64-portbld-freebsd6.2-freshclam' install -o root
> > -g wheel -m 555 -s .libs/freshclam
> > /usr/local/bin/amd64-portbld-
> > freebsd6.2-freshclam
> > Making install in sigtool
> > test -z "/usr/local/bin" || ../config/install-sh -c -d
> > "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'sigtool' '/usr/local/bin/amd64-portbld-freebsd6.2-sigtool'
> > install -o root -g wheel -m 555 -s .libs/sigtool
> > /usr/local/bin/amd64-portbld-fr
> > eebsd6.2-sigtool
> > Making install in clamconf
> > test -z "/usr/local/bin" || ../config/install-sh -c -d
> > "/usr/local/bin" /bin/sh /usr/local/bin/libtool   --mode=install
> > install  -s -o root -g wheel -
> > m 555 'clamconf' '/usr/local/bin/amd64-portbld-freebsd6.2-clamconf'
> > install -o root -g wheel -m 555 -s .libs/clamconf
> > /usr/local/bin/amd64-portbld-f
> > reebsd6.2-clamconf
> >
> > And I find that there are some files under /usr/local/bin/ and
> > /usr/local/sbin
> >
> > ls -ltr /usr/local/bin
> > -r-xr-xr-x  1 root  wheel80624 Sep 19 11:07
> > amd64-portbld-freebsd6.2-sigtool
> > -r-xr-xr-x  1 root  wheel87944 Sep 19 11:07
> > amd64-portbld-freebsd6.2-freshcl
> > am
> > -r-xr-xr-x  1 root  wheel51968 Sep 19 11:07
> > amd64-portbld-freebsd6.2-clamsca
> > n
> > -r-xr-xr-x  1 root  wheel52592 Sep 19 11:07
> > amd64-portbld-freebsd6.2-clamdsc
> > an
> > -r-xr-xr-x  1 root  wheel28272 Sep 19 11:07
> > amd64-portbld-freebsd6.2-clamcon
> > f
> > -r-xr-xr-x  1 root  wheel 1103 Sep 19 11:07
> > amd64-portbld-freebsd6.2-clamav-
> > config
> >
> > ls -ltr /usr/local/sbin
> >
> > -r-xr-xr-x  1 root  wheel67536 Sep 19 11:07
> > amd64-portbld-freebsd6.2-clamd
> >
> > So I am not sure whether the file name has been changed.
> > It seems that this version of clamav can only provide the above
> > files. I have double checked that there is no clamd, clamscan &
> > freshclam in /usr/local/bin and /usr/local/sbin.
> >
> > How can I know the ans. of these question ?
> >
> > Any comment are appreciated.
> >
> I do not have an amd64 system, so I cannot tell from my system if the
> names are changed, but looking at the port install log, it looks as
> if they are.
> There are a couple of things to check.
>
> (1) i

Re: clamav port for 0.94 version , pls help

2008-09-18 Thread David Booth 
On Thursday 18 September 2008, Snopy Land wrote:
> Hi David,
>
> Thanks for your prompt reply.
>
> I have checked the files of "clamav-clamd" and "clamav-freshclam"
> under /usr/local/etc/rc.d.
>
> -r-xr-xr-x  1 root  wheel   722 Sep 19 11:07 clamav-freshclam
> -r-xr-xr-x  1 root  wheel   974 Sep 19 11:07 clamav-clamd
>
> The file date has been updated by today's upgrade process. However,
> the command is still using clamd and freshclam
>
> i.e. command=/usr/local/sbin/clamd<---clamav-clamd file
> command=/usr/local/bin/freshclam<--clamav-freshclam file
>
> So I worry that there may be some hidden problems if I run the
> "amd64-portbid-freebsd6.2-clamd" instead of "clamd"
>
> I will report this case to the admin of freebsd.org. Have you tried
> to send mail to them before? I find that
> [EMAIL PROTECTED]<[EMAIL PROTECTED]@FreeBSD.org&subject=Fr
>eeBSD%20Port:%20clamav-0.94_1> maintains
> the port of clamav from the port search of freebsd.org.
>
> Any other suggestions ?
>
> Thanks.
>

I would just rename the amd64-borbfld-freebsd6.2- to 
 and see clamav works after that.  If it does then it is 
just a problem in the install part of the port which the maintainer 
will probably fix after the port freeze is over. You could either 
submit a pr (see http://www.freebsd.org/send-pr.html ) or shoot an 
email to the maintainer.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD Port: clamav-0.94_1

2008-09-18 Thread Snopy Land 
Hi,

My server version is freebsd6.2 amd64. I have installed clamav to scan my
incoming mail. Everything works smoothly for several years.
Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest
version).

There is no error message found in the whole process, however, I cannot find
the file of "clamd", "clamscan" & "freshclam".
The previous version of these file can be found in /usr/local/sbin and
/usr/local/bin

I have posted my problem in the mailling list of freebsd-ports, however, I
cannot get any hints.

After redo the upgrade process, I find there are some files under
/usr/local/bin and /usr/local/sbin but the file name is differenet.

ls -ltr /usr/local/bin
-r-xr-xr-x  1 root  wheel80624 Sep 19 11:07
amd64-portbld-freebsd6.2-sigtool
-r-xr-xr-x  1 root  wheel87944 Sep 19 11:07
amd64-portbld-freebsd6.2-freshclam
-r-xr-xr-x  1 root  wheel51968 Sep 19 11:07
amd64-portbld-freebsd6.2-clamscan
-r-xr-xr-x  1 root  wheel52592 Sep 19 11:07
amd64-portbld-freebsd6.2-clamdscan
-r-xr-xr-x  1 root  wheel28272 Sep 19 11:07
amd64-portbld-freebsd6.2-clamconf
-r-xr-xr-x  1 root  wheel 1103 Sep 19 11:07
amd64-portbld-freebsd6.2-clamav-config

ls -ltr /usr/local/sbin
-r-xr-xr-x  1 root  wheel67536 Sep 19 11:07
amd64-portbld-freebsd6.2-clamd
Are these files are the same as the file of "clamd", "freshclam" and
"clamscan". If yes, can I create symbolic link for these file so that I can
keep my old setting? (i.e run "/usr/local/sbin/clamd -c
/usr/local/etc/clamd.conf",   and run "/usr/local/bin/freshclam --quiet" in
the cronjob). How many configuration files location should I change ?

Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how to upgrade ports that depend on openssl-stable?

2008-09-18 Thread David J Brooks 
I keep running into this error:

===>  openssl-stable-0.9.7m_1 Conflicts with version in the base.
*** Error code 1

Stop in /usr/ports/security/openssl-stable.

===>>> make failed for security/openssl-stable
===>>> Aborting update

===>>> Update for /usr/ports/security/openssl-stable failed
===>>> Aborting update

===>>> Update for qt4-network-4.3.4_1 failed
===>>> Aborting update

-- 
Smell-O-Vision users insert nostril tubes now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: two ptmalloc ports

2008-09-18 Thread Edwin Groothuis 
On Thu, Sep 18, 2008 at 11:16:53PM -0500, Stephen Montgomery-Smith wrote:
> There are two ports:
> 
> devel/ptmalloc
> devel/ptmalloc2
> 
> They are identical!
> 
> Which one is the "true" port?

See http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127012

ports/127012: Update devel/ptmalloc to version 3

But the assignee is wrong, I'll fix it.

Edwin
-- 
Edwin Groothuis  |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]|  Weblog: http://www.mavetju.org/weblog/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: OPTIONS handling doesn't seem to work fully in dependencies anymore

2008-09-18 Thread Alex Dupre 

John Baldwin wrote:
Ahh, I think I see now.  It requires one OPTIONS using port to mask the 
dependencies.


Exactly.

I thought the same thing, probably yes, but I dunno why it was added in 
such way from the beginning, so I tried to create the simplest and 
surely working patch maintaining the current workflow.


Ok.


Probably it was added in such way because at the beginning there wasn't 
the config-conditional target and runing the config target for every 
port (re)build was not a bright idea. If I have time I'll try to make a 
patch following this rationale, but in the meanwhile my previous patch 
seems good enough.


--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to upgrade ports that depend on openssl-stable?

2008-09-18 Thread Jeremy Chadwick 
On Fri, Sep 19, 2008 at 12:08:15AM -0500, David J Brooks wrote:
> I keep running into this error:
> 
> ===>  openssl-stable-0.9.7m_1 Conflicts with version in the base.
> *** Error code 1

OpenSSL is included in FreeBSD in the base system.  The port you're
trying to install requires a newer version of OpenSSL than what's in the
base system.

You need to define WITH_OPENSSL_BASE=yes in your /etc/make.conf.  This
should make the port build/install successfully, and will overwrite
the OpenSSL installation in the base system.

You will also need to set WITHOUT_OPENSSL=true in /etc/src.conf
(assuming this is FreeBSD 7.x), to ensure the next time you
build/install world, that you do not bother building the "base version"
of OpenSSL, and instead continue to rely on the port version.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to upgrade ports that depend on openssl-stable?

2008-09-18 Thread Jeremy Chadwick 
On Thu, Sep 18, 2008 at 11:27:32PM -0700, Jeremy Chadwick wrote:
> On Fri, Sep 19, 2008 at 12:08:15AM -0500, David J Brooks wrote:
> > I keep running into this error:
> > 
> > ===>  openssl-stable-0.9.7m_1 Conflicts with version in the base.
> > *** Error code 1
> 
> OpenSSL is included in FreeBSD in the base system.  The port you're
> trying to install requires a newer version of OpenSSL than what's in the
> base system.
> 
> You need to define WITH_OPENSSL_BASE=yes in your /etc/make.conf.  This
> should make the port build/install successfully, and will overwrite
> the OpenSSL installation in the base system.
> 
> You will also need to set WITHOUT_OPENSSL=true in /etc/src.conf
> (assuming this is FreeBSD 7.x), to ensure the next time you
> build/install world, that you do not bother building the "base version"
> of OpenSSL, and instead continue to rely on the port version.

One other thing I forgot to mention:

You will need to rebuild all ports reliant on SSL (this may be hard to
determine reliably), as well as all base system utilities reliant on SSL
(make world will suffice for this), as there will very likely be a
library version mismatch between the old base OpenSSL and the port
version of OpenSSL.

There's a chance you won't have to do this ("I installed the port like
you said and everything still works"), but I would recommend you not
take any chances.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"