Re: OO 3.3.0 fails to build connectivity module on amd64 9-STABLE
Hi
I also reproduced, and pointy hat, either.
It looks like ooo port is broken again...
Thanks
Nakata Maho
From: Lawrence Stewart lstew...@freebsd.org
Subject: OO 3.3.0 fails to build connectivity module on amd64 9-STABLE
Date: Thu, 09 Feb 2012 16:42:30 +1100
Hi,
The OO 3.3.0 build fails in the connectivity module with the
following error:
Compiling: connectivity/source/parse/wrap_sqlbison.cxx
c++ -fmessage-length=0 -c -O2 -fno-strict-aliasing -DENABLE_LAYOUT=0
-DENABLE_LAYOUT_EXPERIMENTAL=0 -fvisibility=hidden
-I. -I../../unxfbsdx.pro/misc -I../../unxfbsdx.pro/inc/sql -I../inc
-I../../inc/pch -I../../inc -I../../unx/inc -I../../unxfbsdx.pro/inc
-I.
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/stl
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/external
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/unxfbsdx/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/inc
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/res
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/stl
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solenv/inc/Xp31
-I/usr/local/diablo-jdk1.6.0/include
-I/usr/local/diablo-jdk1.6.0/include/freebsd
-I/usr/local/diablo-jdk1.6.0/i
nclude/bs
d -I/usr/local/diablo-jdk1.6.0/include/linux
-I/usr/local/diablo-jdk1.6.0/include/native_threads/include
-I/usr/local/include
-I/usr/ports/editors/openoffice.org-3/work/OOO330_m20/solver/330/unxfbsdx.pro/inc/offuh
-I. -I../../res -I. -pipe -fvisibility-inlines-hidden -g1 -Wall
-Wextra -Wendif-labels -Wshadow -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -fpic -DFREEBSD -DUNX -DVCL -DGCC -DC341
-DX86_64 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1
-DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -DX86_64 -D__DMAKE
-DUNIX -DCPPU_ENV=gcc3 -DGXX_INCLUDE_PATH=/usr/include/c++/4.2
-DSUPD=330 -DPRODUCT -DNDEBUG -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DCUI
-DSOLAR_JAVA -DOOO_DLLIMPLEMENTATION_DBTOOLS -DSHAREDLIB -D_DLL_
-fexceptions -fno-enforce-eh-specs -DEXCEPTIONS_ON -o
../../unxfbsdx.pro/slo/wrap_sqlbison.o
/usr/ports/editors/openoffice.org-3/work/OOO330_m20/connectivity/source/parse/wrap_sqlbison.cxx
In file included from
/usr/ports/editors/openoffice.org-3/work/OOO330_m20/connectivity/source/parse/wrap_sqlbison.cxx:31:
../../unxfbsdx.pro/misc/sqlbison.cxx: In function 'int SQLyyparse()':
../../unxfbsdx.pro/misc/sqlbison.cxx:7813: error: invalid conversion
from 'const char*' to 'sal_Char*'
../../unxfbsdx.pro/misc/sqlbison.cxx:7813: error: initializing
argument 1 of 'void connectivity::OSQLParser::error(sal_Char*)'
dmake: Error code 1, while making
'../../unxfbsdx.pro/slo/wrap_sqlbison.obj'
Ports tree was csuped yesterday and all installed ports are up to
date.
System info that might be useful...
lstewart@lstewart uname -a
FreeBSD lstewart 9.0-STABLE FreeBSD 9.0-STABLE #1 r231173M: Wed Feb 8
16:14:51 EST 2012 lstewart@lstewart:/usr/obj/usr/src/sys/DESKTOP amd64
lstewart@lstewart pkg_info -x bison
Information for bison-2.5,1:
Relevant lines from /etc/make.conf:
.if ${.CURDIR:M*/editors/openoffice.org-3}
WITH_KDE4=1
LOCALIZED_LANG=en-GB
.endif
I'm running KDE 4.7.4.
Any thoughts on how to fix?
Cheers,
Lawrence
___
freebsd-openoff...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice
To unsubscribe, send any mail to
freebsd-openoffice-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1 is out
On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are 400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep gcc needs updating (port has 4.7.0.20120128) # pkg_version -v |grep gcc-4.7.0.20120107 needs updating (port has 4.7.0.20120128) libXaw-1.0.8,1 needs updating (port has 1.0.8,2) libXt-1.0.9needs updating (port has 1.0.9,1) xorg-macros-1.15.0 needs updating (port has 1.16.1) # pkg info libXaw libXt xorg-macros libXaw-1.0.8,2: X Athena Widgets library libXt-1.0.9,1: X Toolkit library xorg-macros-1.16.1: X.Org development aclocal macros that pkg_info and pkg_version can no longer be trusted, and pkg info and pkg version must be used instead. It makes sense, but just to check. Sorry to be so slow. Anyway, the new tools are great, working fine on ia64 r231193. Thanks for your hard work! -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1 is out
On 02/10/2012 10:24 AM, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep gccneeds updating (port has 4.7.0.20120128) # pkg_version -v |grep gcc-4.7.0.20120107needs updating (port has 4.7.0.20120128) libXaw-1.0.8,1needs updating (port has 1.0.8,2) libXt-1.0.9needs updating (port has 1.0.9,1) xorg-macros-1.15.0needs updating (port has 1.16.1) # pkg info libXaw libXt xorg-macros libXaw-1.0.8,2: X Athena Widgets library libXt-1.0.9,1: X Toolkit library xorg-macros-1.16.1: X.Org development aclocal macros that pkg_info and pkg_version can no longer be trusted, and pkg info and pkg version must be used instead. That's right. It makes sense, but just to check. Sorry to be so slow. Anyway, the new tools are great, working fine on ia64 r231193. Thanks for your hard work! And thank you for your feedback! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
mysql 5.5 fails to build.
Hi, I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated [ 96%] Building CXX object sql/CMakeFiles/sql.dir/datadict.cc.o [ 96%] Building CXX object sql/CMakeFiles/sql.dir/sql_reload.cc.o [ 96%] Building CXX object sql/CMakeFiles/sql.dir/sql_truncate.cc.o In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/mysqld.h:19, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/handler.h:29, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/datadict.h:18, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/datadict.cc:16: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/debug_sync.h:29, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/sql_truncate.cc:16: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/mysqld.h:19, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/sql_reload.cc:18: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated [ 96%] Building CXX object sql/CMakeFiles/sql.dir/sql_yacc.cc.o [ 96%] Building CXX object sql/CMakeFiles/sql.dir/sql_builtin.cc.o In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/unireg.h:20, from /export/home/pb2/build/sb_0-4575772-1324064860.06/mysql-5.5.20-release-basket-export_GPL-2891819/sql/sql_yacc.yy:41: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated [ 96%] Building C object sql/CMakeFiles/sql.dir/__/mysys/my_libwrap.c.o In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/mysys/my_libwrap.c:21: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated [ 96%] Building CXX object sql/CMakeFiles/sql.dir/sql_lex.cc.o In file included from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/include/my_global.h:351, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/unireg.h:20, from /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/sql/sql_lex.cc:21: /usr/include/sys/timeb.h:42:2: warning: #warning this file includes sys/timeb.h which is deprecated Linking CXX static library libsql_embedded.a [ 96%] Built target sql_embedded [ 96%] Generating mysqlserver_depends.c Scanning dependencies of target mysqlserver [ 97%] Building C object libmysqld/CMakeFiles/mysqlserver.dir/mysqlserver_depends.c.o Linking C static library libmysqld.a ar: warning: creating /var/ports/usr/ports/databases/mysql55-server/work/mysql-5.5.20/libmysqld/libmysqld.a [ 97%] Built target mysqlserver Linking CXX static library libsql.a [ 97%] Built target sql Scanning dependencies of target mysqld [ 97%] Building CXX object sql/CMakeFiles/mysqld.dir/main.cc.o Linking CXX executable mysqld ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_write': row0merge.c:(.text+0x571): undefined reference to `posix_fadvise' ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_read': row0merge.c:(.text+0x968): undefined reference to `posix_fadvise' ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_build_indexes': row0merge.c:(.text+0x1f08): undefined reference to `posix_fadvise' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/databases/mysql55-server. *** Error code 1 In the tinderbox builds fine. Some infos about the system FreeBSD 9.0-STABLE #1 r229835: Mon Jan 9 04:11:49 CET 2012, Filesystem is ZFS, and all mysql servers running in a jail. Any idea? - Martin +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest
Re: mysql 5.5 fails to build.
Martin Wilke wrote: I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, Nope, sorry. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.5 fails to build.
Thanks Alex, Just to update the Error is comes only in the Jail, without jail it builds fine. Maybe someone else any idea? - Martin +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest On Feb 10, 2012, at 5:58 PM, Alex Dupre wrote: Martin Wilke wrote: I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, Nope, sorry. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.5 fails to build.
Quoting Martin Wilke m...@freebsd.org (from Fri, 10 Feb 2012 17:44:01 +0800): Linking CXX executable mysqld ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_write': row0merge.c:(.text+0x571): undefined reference to `posix_fadvise' ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_read': row0merge.c:(.text+0x968): undefined reference to `posix_fadvise' ../storage/innobase/libinnobase.a(row0merge.c.o): In function `row_merge_build_indexes': row0merge.c:(.text+0x1f08): undefined reference to `posix_fadvise' In the tinderbox builds fine. Some infos about the system FreeBSD 9.0-STABLE #1 r229835: Mon Jan 9 04:11:49 CET 2012, Filesystem is ZFS, and all mysql servers running in a jail. Any idea? Did you update the jails recently from a FreeBSD version without posix_fadvise? I noticed in my ezjail-update logs that the update of files with file flags fails without aborting the installation/update. So maybe you have some old libs around. I recursively removed the flags from my basejails and did the update again. A quick look at ezjail suggests that the removal of the flags should happen automatically, but I didn't had the time to dig deeper. Bye, Alexander. -- Youth is when you blame all your troubles on your parents; maturity is when you learn that everything is the fault of the younger generation. http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.5 fails to build.
On Fri, 10 Feb 2012 18:41:15 +0800 Martin Wilke m...@freebsd.org wrote: Thanks Alex, Just to update the Error is comes only in the Jail, without jail it builds fine. Maybe someone else any idea? database# pkg_info -xI mysql-s mysql-server-5.5.20 Multithreaded SQL database (server) database# uname -rms FreeBSD 10.0-CURRENT amd64 database# sysctl security.jail.jailed security.jail.jailed: 1 current# mount |grep data tank/usr/jails/database on /usr/jails/database (zfs, local, noatime, nfsv4acls) devfs on /usr/jails/database/dev (devfs, local, multilabel) - Martin +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest On Feb 10, 2012, at 5:58 PM, Alex Dupre wrote: Martin Wilke wrote: I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, Nope, sorry. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1 is out
On Fri, Feb 10, 2012 at 4:24 AM, Anton Shterenlikht me...@bristol.ac.uk wrote: On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are 400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep gcc needs updating (port has 4.7.0.20120128) # pkg_version -v |grep FYI pkg version -vl\ pkg_version -vl\ -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1 is out
On Fri, Feb 10, 2012 at 09:07:02AM -0500, Eitan Adler wrote: On Fri, Feb 10, 2012 at 4:24 AM, Anton Shterenlikht me...@bristol.ac.uk wrote: On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are 400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep gcc needs updating (port has 4.7.0.20120128) # pkg_version -v |grep FYI pkg version -vl\ pkg_version -vl\ Cool! Thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1 is out
Anton Shterenlikht wrote: On Fri, Feb 10, 2012 at 09:07:02AM -0500, Eitan Adler wrote: On Fri, Feb 10, 2012 at 4:24 AM, Anton Shterenlikhtme...@bristol.ac.uk wrote: On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep gcc needs updating (port has 4.7.0.20120128) # pkg_version -v |grep FYI pkg version -vl\ pkg_version -vl\ Cool! I think that better is pkg_version -vL = This way you get notified about moved / deleted ports as well: e.g.: proftpd-mysql-1.3.3g_2 ! Comparison failed Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql 5.5 fails to build.
Martin, check your make patch stage. Be sure you're got a clean setup in both the -server and the -client port. I hit this one and that was it I had run a make makepatch which duplicated some files. That said it works fine for me on i386/amd64 in tb and outside of it. On 02/10/12 10:48, Sergey V. Dyatko wrote: On Fri, 10 Feb 2012 18:41:15 +0800 Martin Wilke m...@freebsd.org wrote: Thanks Alex, Just to update the Error is comes only in the Jail, without jail it builds fine. Maybe someone else any idea? database# pkg_info -xI mysql-s mysql-server-5.5.20 Multithreaded SQL database (server) database# uname -rms FreeBSD 10.0-CURRENT amd64 database# sysctl security.jail.jailed security.jail.jailed: 1 current# mount |grep data tank/usr/jails/database on /usr/jails/database (zfs, local, noatime, nfsv4acls) devfs on /usr/jails/database/dev (devfs, local, multilabel) - Martin +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest On Feb 10, 2012, at 5:58 PM, Alex Dupre wrote: Martin Wilke wrote: I facing since a while on all my servers that mysql 5.5.20 fails to build. Have anyone of you seen something like that, Nope, sorry. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
[PATCH] ports-mgmt/porttools: add submit -P to print PR
Submitter-Id: current-users
Originator:John Hein
Organization:
Confidential: no
Synopsis: [PATCH] ports-mgmt/porttools: add submit -P to print PR
Severity: non-critical
Priority: low
Category: ports
Class: change-request
Release:
Environment:
Description:
Add -P to print PR to stdout instead of submitting. This allows the
sender to verify the PR before sending and possibly save the output to
paste into a mail client when an automated mailer (sendmail or some
other mailer to stuff in MAIL_AGENT) is unavailable or impractical to
use.
Also fix the comment in patch-cmd_submit.in that said support for
PORTEPOCH was added (looks like all of ports/154809 was not applied).
However it would probably be simpler to just remove the
PORTREVISION/PORTVERSION/PORTEPOCH logic used in port/154809 and just
use PKGNAME instead.
I'm ignoring the whitespace style mistakes in the PORTREVISION change
in patch-cmd_submit.in, but the committer could fix that if she feels
so inclined (and doesn't just refactor to use PKGNAME).
Added file(s):
- files/patch-port.1
Generated with FreeBSD Port Tools 0.99
How-To-Repeat:
Fix:
--- porttools-0.99_3.patch begins here ---
Index: Makefile
===
RCS file: /base/FreeBSD-CVS/ports/ports-mgmt/porttools/Makefile,v
retrieving revision 1.28
diff -u -p -u -r1.28 Makefile
--- Makefile30 Oct 2011 20:29:53 - 1.28
+++ Makefile10 Feb 2012 16:09:21 -
@@ -7,7 +7,7 @@
PORTNAME= porttools
PORTVERSION= 0.99
-PORTREVISION= 2
+PORTREVISION= 3
CATEGORIES=ports-mgmt
MASTER_SITES= SF
Index: files/patch-cmd_submit.in
===
RCS file:
/base/FreeBSD-CVS/ports/ports-mgmt/porttools/files/patch-cmd_submit.in,v
retrieving revision 1.1
diff -u -p -u -r1.1 patch-cmd_submit.in
--- files/patch-cmd_submit.in 30 Oct 2011 20:29:53 - 1.1
+++ files/patch-cmd_submit.in 7 Feb 2012 19:36:05 -
@@ -1,12 +1,43 @@
$FreeBSD: ports/ports-mgmt/porttools/files/patch-cmd_submit.in,v 1.1
2011/10/30 20:29:53 crees Exp $
-From bugs.freebsd.org/154809
+Porttools will now include PORTREVISION in PRs sent (bugs.freebsd.org/154809).
-Porttools will now include PORTREVISION and PORTEPOCH in PRs sent
+Add -P to print PR to stdout instead of submitting.
cmd_submit.in.old 2011-02-15 12:55:54.0 -0800
-+++ cmd_submit.in 2011-02-15 12:59:51.0 -0800
-@@ -146,6 +146,7 @@
+
+--- cmd_submit.in.orig 2009-09-09 13:59:59.0 -0600
cmd_submit.in 2012-02-07 11:55:39.0 -0700
+@@ -30,6 +30,7 @@
+ pattern - against original port in pwdpattern
+ -s severity - Set PR's severity to severity
+ -p priority - Set PR's priority to priority
++ -P - Don't send the PR; print to stdout (see -P in send-pr(1))
+ -c - committer mode: more portlint(1) checks
+ -L - Skip running portlint(1)
+ EOF
+@@ -41,9 +42,10 @@
+ PRIORITY=low
+ COMMITTER=no
+ RUN_PORTLINT=yes
++SENDPR_ARGS=
+
+ # Parse command line arguments
+-ARGS=`/usr/bin/getopt hm:d:s:p:cL $*`
++ARGS=`/usr/bin/getopt hm:d:s:p:cLP $*`
+ if [ $? != 0 ]
+ then
+ echo Error: invalid arguments
+@@ -116,6 +118,9 @@
+ -L)
+ RUN_PORTLINT=no
+ ;;
++ -P)
++ SENDPR_ARGS=$SENDPR_ARGS -P
++ ;;
+ esac
+ shift
+ done
+@@ -146,6 +151,7 @@
# Collect information about the port
PORTNAME=`make -V PKGNAMEPREFIX``make -V PORTNAME``make -V PKGNAMESUFFIX`
PORTVERSION=`make -V PORTVERSION`
@@ -14,7 +45,7 @@ Porttools will now include PORTREVISION
PKGNAME=`make -V PKGNAME`
CATEGORY=`make -V CATEGORIES | sed -E 's/^([^ ]+).*$/\1/'`
MAINTAINER=`make -V MAINTAINER`
-@@ -194,8 +195,14 @@
+@@ -194,8 +200,14 @@
# Override some parameters if submitting an update to a newer
# version of an existing port
CLASS=update
@@ -29,3 +60,12 @@ Porttools will now include PORTREVISION
fi
# Check to see if maintainership was requested
+@@ -333,7 +345,7 @@
+
+ # Invoke send-pr(1)
+ echo === Invoking send-pr(1) to submit a PR
+-PR_FORM=${PR_FORM} /usr/bin/send-pr -a ${PATCH}
++PR_FORM=${PR_FORM} /usr/bin/send-pr -a ${PATCH} ${SENDPR_ARGS}
+ if [ $? -ne 0 ]
+ then
+ echo Error submitting PR
Index: files/patch-port.1
===
RCS file: files/patch-port.1
diff -N files/patch-port.1
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/patch-port.1 10 Feb 2012 15:22:24 -
@@ -0,0 +1,15 @@
+$FreeBSD$
+
+--- port.1.orig2009-09-09 13:59:59.0 -0600
port.1 2012-02-10 08:19:49.0 -0700
+@@ -245,6 +245,10 @@
+ Skips running
+ .Xr portlint 1 .
+ Using this option will generate a warning and it strongly discouraged.
++.It Fl P
++Don't send the PR.
++Just print to stdout (see
Requested changes to lang/php5 port
Hello, I'd like to request two minor changes to the lang/php5 port: 1. Change 'CONFIGURE_ARGS=' line to 'CONFIGURE_ARGS+=' to allow customizations to the arguments. One reason for this is that some extensions, like security/php5-hash, have to be compiled into the core. Otherwise, 'session.hash_function' option cannot use hash algorithms offered by that extension. See the following bug report for more info: https://bugs.php.net/bug.php?id=53789 2. Unless there is a very good reason for keeping them, I think '--enable-libxml' and especially '--enable-mysqlnd' should be removed from the default set of arguments. Make these two part of the options dialog, if you want, but there are plenty of installations that have no need for any MySQL or XML functionality. Why compile these into the core by default? Thanks, Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1^Wbeta2 is out
As said in the first announcement there will be lots of beta release before rc and then stable the second one is now out with the following changes: * update bundled sqlite to 3.7.10 * add -n to pkg create to avoid packing already packed packages * Fix rc script handling * safer sbuf usage (this fix ia64 support) * report a list of failing packages if any with pkg add * allow category/port pattern in pkg search * add support for syslog (through a pkg.conf option) * the portmaster patch in the git is now up to date with 3.11 and feature complete (thanks avilla) * add -R to pkg info to print out the raw manifest of a given package * fix pkg query %a * more robust to errors when creating packages * fix duplication output in pkg check * fix pkg which: retreive the absolute path of the arguments not the realpath (aka do not resolv symlinks) * some man pages fixes/improvements Thanks to every one who contributed codes, patches, fixes, ideas regards, Bapt pgpwHIiVLAMmQ.pgp Description: PGP signature
Re: mysql 5.5 fails to build.
On Fri, 10 Feb 2012 11:46:15 +0100 Alexander Leidinger alexan...@leidinger.net wrote: Did you update the jails recently from a FreeBSD version without posix_fadvise? I noticed in my ezjail-update logs that the update of files with file flags fails without aborting the installation/update. So maybe you have some old libs around. I recursively removed the flags from my basejails and did the update again. A quick look at ezjail suggests that the removal of the flags should happen automatically, but I didn't had the time to dig deeper. Bye, Alexander. Hi, Thanks Alex that was it. Everything works now fine. - Martin -- +--oOO--(_)--OOo+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Requested changes to lang/php5 port
On Fri, Feb 10, 2012 at 12:41 PM, Maxim Khitrov m...@mxcrypt.com wrote: Hello, I'd like to request two minor changes to the lang/php5 port: 1. Change 'CONFIGURE_ARGS=' line to 'CONFIGURE_ARGS+=' to allow customizations to the arguments. One reason for this is that some extensions, like security/php5-hash, have to be compiled into the core. Otherwise, 'session.hash_function' option cannot use hash algorithms offered by that extension. See the following bug report for more info: https://bugs.php.net/bug.php?id=53789 2. Unless there is a very good reason for keeping them, I think '--enable-libxml' and especially '--enable-mysqlnd' should be removed from the default set of arguments. Make these two part of the options dialog, if you want, but there are plenty of installations that have no need for any MySQL or XML functionality. Why compile these into the core by default? Actually, I now realize that changing 'CONFIGURE_ARGS=' to 'CONFIGURE_ARGS+=' wouldn't help me, because --disable-all would negate --enable-hash, which I was planning to specify. What would be the best way of passing custom --enable-X arguments to CONFIGURE_ARGS after --disable-all is set? As for removing --enable-libxml, it seems to be required when building the port (maybe for fpm?), but --enable-mysqlnd should definitely be removed by default. - Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: need 10. exp run? kusefs-kmod?
I've got a 10-CURRENT build in my tinderbox. I'll kick off building it and everything that depends on it there, on both 10-CURRENT and 7.x, 8.x and 9.x. I think exp-run is overkill for something non-infrastructure like this. Assuming no build breakage, I'd say it's fine to commit. Steve Tested on 8.2, and 9.0, tinderbox logs fine (you will notice scons tries to delete an extra egg... I will that, but that is a different pr) submitter has 10.0, maintainer has 8.2. Can I get some testing on 10.0 for this? pr has specific code looking for 10.x: +#if __FreeBSD_version= 105 ++if (checkpath(dir, mntpath) != 0) ++err(1, %s, mntpath); ++#else + (void)checkpath(dir, mntpath); ++#endif pr is http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164218 patch (with portsrevision added): http://people.freebsd.org/~scheidell/pr_164218_sysutils_fusefs-kmod.patch -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Headsup for users of ports-mgmt/porttools
Thanks for the heads up, I use porttools a great deal these days. I've updated my local install with the version from the PR and will let you know if I have any trouble with it. Steve Hey all, A new maintainer stepped up for ports-mgmt/porttools, and to my shame I've not got around to committing his changes. Since this is widely used, and we are the upstream as it were, anyone who uses porttools should take a look at the changes in the PR [1], and let us know if you have any problems with it. If we get no negative feedback I'll commit it in a week :) Chris [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/139872 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Headsup for users of ports-mgmt/porttools
Yes me, I'll update next week. I don't function without this port. On 02/10/12 18:42, Steve Wills wrote: Thanks for the heads up, I use porttools a great deal these days. I've updated my local install with the version from the PR and will let you know if I have any trouble with it. Steve Hey all, A new maintainer stepped up for ports-mgmt/porttools, and to my shame I've not got around to committing his changes. Since this is widely used, and we are the upstream as it were, anyone who uses porttools should take a look at the changes in the PR [1], and let us know if you have any problems with it. If we get no negative feedback I'll commit it in a week :) Chris [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/139872 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
Portmaster binary package upgrade question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, I'm in the midst of building a system to use Tinderbox and FreeBSD jails to keep them up to date as new port updates are committed to the tree. I created some meta-ports in /usr/ports/local/misc to record dependencies and be able to install one top-level port that pulls in all other required ports. I'm now testing the ability to run an upgrade with portmaster once a new package set is built, and I'm using this command: pkgtester# env INDEXDIR=/tmp MASTER_SITE_INDEX=http://pkgbuilder.shn.prv/tb/packages/8.2-FreeBSD-SHN-201202101009/Latest/ PACKAGESITE=http://pkgbuilder.shn.prv/tb/packages/8.2-FreeBSD-SHN-201202101009/Latest/ portmaster -PP -v --update-if-newer --index-only server-web\* === Currently installed version: server-web-0.201202071358 === Port directory: /usr/ports/local/misc/server-web === Gathering dependency list for local/misc/server-web from INDEX-8 === Starting dependency check === Checking dependency: www/apache22 === Update failed === Aborting update Terminated pkgtester# As you can see, there's not a lot to go on. My INDEX-8 file has my local ports included in it, so I think the dependency list is OK: pkgtester# grep ^server-web INDEX-8 | cut -f1 -d\| server-web-0.201202101009 If I change the package name above from server-web\* to apache\*, it works fine, so it seems to be an issue with my local meta-ports. Does anyone have an idea where to look to troubleshoot the problem? Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk81nhkACgkQ0sRouByUApAO4wCgx4CZ8pcuSlll8BBFLlyO5Lqq U30An221nkq0Ajdp0fqye9PcMuipw2OY =qY4M -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portmaster binary package upgrade question
On 02/10/2012 14:45, Greg Larkin wrote: Hi folks, I'm in the midst of building a system to use Tinderbox and FreeBSD jails to keep them up to date as new port updates are committed to the tree. I created some meta-ports in /usr/ports/local/misc to record dependencies and be able to install one top-level port that pulls in all other required ports. I'm now testing the ability to run an upgrade with portmaster once a new package set is built, and I'm using this command: pkgtester# env INDEXDIR=/tmp MASTER_SITE_INDEX=http://pkgbuilder.shn.prv/tb/packages/8.2-FreeBSD-SHN-201202101009/Latest/ PACKAGESITE=http://pkgbuilder.shn.prv/tb/packages/8.2-FreeBSD-SHN-201202101009/Latest/ You probably want to put these in a portmaster rc file. Also to avoid code duplication you can set the first then use PACKAGESITE=$MASTER_SITE_INDEX. The /Latest is going to get stripped off anyway. And are you really putting your INDEX file in /Latest/ ?? portmaster -PP -v --update-if-newer The --update-if-newer flag is only useful if you're feeding portmaster a list of ports, some of which are already up to date. --index-only server-web\* === Currently installed version: server-web-0.201202071358 === Port directory: /usr/ports/local/misc/server-web You can't do 5 levels of port directories. Either leave out the category below local, or name the categories local-misc, local-foo, local-bar, etc. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ signature.asc Description: OpenPGP digital signature
Re: [HEADSUP][CFT] pkgng beta1^Wbeta2^W3 is out
Sorry pkg add was broken in beta2 this release fixes it. Changes: * fix pkg add (it is been broken during beta2 sorry about that) * fix manifest emitter: now really emit the pkg-message in message no more description * add %M to pkg query to show messages * concat all pkg-messages and show it once at the end of operations * print messages about missing dependency during pkg add regards, Bapt pgpRRwa14wBzh.pgp Description: PGP signature
Re: What use is WWWDIR_REL?
On 02/08/2012 20:18, Scot Hetzel wrote:
On Tue, Feb 7, 2012 at 9:28 PM, Doug Barton do...@freebsd.org wrote:
Following up to my previous post about Why isn't WWWDIR_REL in the
default PLIST_SUB I broke open bsd.port.mk and found this:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \***!!!
ETCDIR=${ETCDIR_REL}
So this leads me to many questions, the first and most obvious of which
is, what the heck good is WWWDIR_REL in the first place? I searched the
ports tree and found 1,063 uses of it (outside of bpm itself). 1,035 of
them are literals in a pkg-plist, which at this point looks completely
useless. Of the 28 others 13 of them are PLIST_SUB related, which
apparently can also be removed. Most of the other 15 look like mistakes,
and all of them look like they can be fixed with little difficulty.
Those 1035 ports that are using WWWDIR_REL in their pkg-plist are
wrong and should be changed to use WWWDIR. Since PLIST_SUB will
automatically replace %%WWWDIR%% with ${WWWDIR_REL} in the pkg-plist.
Ok, glad we're in agreement on that.
So I'd like to propose the attached, not to be included until the
existing uses of WWWDIR_REL are updated of course. Can anyone tell me
why this would be a bad idea? I think being able to just use %%WWWDIR%%
in the plist would be a lot less confusing.
I believe the original purpose of the *_REL variables in bsd.port.mk
was to make maintaining bsd.port.mk easier.
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1^Wbeta2 is out
On 10 February 2012 09:51, Baptiste Daroussin b...@freebsd.org wrote: As said in the first announcement there will be lots of beta release before rc and then stable the second one is now out with the following changes: * update bundled sqlite to 3.7.10 Hm, are there plans to just expose the system sqlite version for other system tools that may wish to take advantage of this? Adrian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
On Fri, Feb 10, 2012 at 04:13:32PM -0800, Doug Barton thus spake:
On 02/08/2012 20:18, Scot Hetzel wrote:
On Tue, Feb 7, 2012 at 9:28 PM, Doug Barton do...@freebsd.org wrote:
Following up to my previous post about Why isn't WWWDIR_REL in the
default PLIST_SUB I broke open bsd.port.mk and found this:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \***!!!
ETCDIR=${ETCDIR_REL}
So this leads me to many questions, the first and most obvious of which
is, what the heck good is WWWDIR_REL in the first place? I searched the
ports tree and found 1,063 uses of it (outside of bpm itself). 1,035 of
them are literals in a pkg-plist, which at this point looks completely
useless. Of the 28 others 13 of them are PLIST_SUB related, which
apparently can also be removed. Most of the other 15 look like mistakes,
and all of them look like they can be fixed with little difficulty.
Those 1035 ports that are using WWWDIR_REL in their pkg-plist are
wrong and should be changed to use WWWDIR. Since PLIST_SUB will
automatically replace %%WWWDIR%% with ${WWWDIR_REL} in the pkg-plist.
Ok, glad we're in agreement on that.
So I'd like to propose the attached, not to be included until the
existing uses of WWWDIR_REL are updated of course. Can anyone tell me
why this would be a bad idea? I think being able to just use %%WWWDIR%%
in the plist would be a lot less confusing.
I believe the original purpose of the *_REL variables in bsd.port.mk
was to make maintaining bsd.port.mk easier.
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
Doug
Interesting bit here:
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#INSTALL-DOCUMENTATION
snip
DATADIR gets expanded to PREFIX/share/PORTNAME.
-- DATADIR_REL gets expanded to share/PORTNAME.
DOCSDIR gets expanded to PREFIX/share/doc/PORTNAME.
-- DOCSDIR_REL gets expanded to share/doc/PORTNAME.
EXAMPLESDIR gets expanded to PREFIX/share/examples/PORTNAME.
-- EXAMPLESDIR_REL gets expanded to share/examples/PORTNAME.
-jgh
--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
On 02/10/2012 16:17, Jason Helfman wrote:
On Fri, Feb 10, 2012 at 04:13:32PM -0800, Doug Barton thus spake:
On 02/08/2012 20:18, Scot Hetzel wrote:
On Tue, Feb 7, 2012 at 9:28 PM, Doug Barton do...@freebsd.org wrote:
Following up to my previous post about Why isn't WWWDIR_REL in the
default PLIST_SUB I broke open bsd.port.mk and found this:
PLIST_SUB+= DOCSDIR=${DOCSDIR_REL} \
EXAMPLESDIR=${EXAMPLESDIR_REL} \
DATADIR=${DATADIR_REL} \
WWWDIR=${WWWDIR_REL} \***!!!
ETCDIR=${ETCDIR_REL}
So this leads me to many questions, the first and most obvious of which
is, what the heck good is WWWDIR_REL in the first place? I searched the
ports tree and found 1,063 uses of it (outside of bpm itself). 1,035 of
them are literals in a pkg-plist, which at this point looks completely
useless. Of the 28 others 13 of them are PLIST_SUB related, which
apparently can also be removed. Most of the other 15 look like
mistakes,
and all of them look like they can be fixed with little difficulty.
Those 1035 ports that are using WWWDIR_REL in their pkg-plist are
wrong and should be changed to use WWWDIR. Since PLIST_SUB will
automatically replace %%WWWDIR%% with ${WWWDIR_REL} in the pkg-plist.
Ok, glad we're in agreement on that.
So I'd like to propose the attached, not to be included until the
existing uses of WWWDIR_REL are updated of course. Can anyone tell me
why this would be a bad idea? I think being able to just use %%WWWDIR%%
in the plist would be a lot less confusing.
I believe the original purpose of the *_REL variables in bsd.port.mk
was to make maintaining bsd.port.mk easier.
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
Doug
Interesting bit here:
Have you actually read the thread at all? I understand how they get
expanded, my point is that the *_REL variables are (apparently) only
useful in a plist, and they are not needed there because of how the
default PLIST_SUB is expanded. I've already pasted that bit into this
thread twice, I'm not going to do it again. :)
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP][CFT] pkgng beta1^Wbeta2 is out
On Fri, Feb 10, 2012 at 04:15:34PM -0800, Adrian Chadd wrote: On 10 February 2012 09:51, Baptiste Daroussin b...@freebsd.org wrote: As said in the first announcement there will be lots of beta release before rc and then stable the second one is now out with the following changes: * update bundled sqlite to 3.7.10 Hm, are there plans to just expose the system sqlite version for other system tools that may wish to take advantage of this? Adrian Nope but that is a good idea can you add and issue on github for that please so that we don't forget about it ? regards, Bapt pgpyan7fzNklt.pgp Description: PGP signature
Beta 3 still not OK
Seems that the sqlite database has changed from beta1 to beta3??? I have all the system running exclusive on pkg there is no more old pkg How can I upgrade the sqlite database from beta1 to beta3??? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Beta 3 still not OK
Em Sáb, 2012-02-11 às 00:38 +0100, Baptiste Daroussin escreveu: Sorry pkg add was broken in beta2 this release fixes it. Changes: * fix pkg add (it is been broken during beta2 sorry about that) * fix manifest emitter: now really emit the pkg-message in message no more description * add %M to pkg query to show messages * concat all pkg-messages and show it once at the end of operations * print messages about missing dependency during pkg add regards, Bapt Hello, Baptiste, Beta 3 still not ok... = pkg upgrade Assertion failed: ((buf-s_flags SBUF_FINISHED) == SBUF_FINISHED), function sbuf_get, file pkg_util.c, line 36. Abort trap: 6 (imagem do núcleo gravada) == the sequence was: pkg update OK pkg upgrade = error... the error comes before a query to the sql database at pkgdb.c line 2133 seems that buf-flags is missing SBUF_FINISHED... data at buf is s_buf = 0x80081d200 INSERT OR IGNORE INTO pkgjobs (pkgid, origin, name, version, comment, desc, arch, osversion, maintainer, www, prefix, flatsize, pkgsize, cksum, repopath, automatic) SELECT id, origin, name, version, c..., s_unused = 0x0, s_size = 512, s_len = 363, s_flags = 589825} on downgrade to beta 1, it works ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Requested changes to lang/php5 port
On Fri, Feb 10, 2012 at 12:41 PM, Maxim Khitrov m...@mxcrypt.com wrote: Hello, I'd like to request two minor changes to the lang/php5 port: 1. Change 'CONFIGURE_ARGS=' line to 'CONFIGURE_ARGS+=' to allow customizations to the arguments. One reason for this is that some extensions, like security/php5-hash, have to be compiled into the core. Otherwise, 'session.hash_function' option cannot use hash algorithms offered by that extension. See the following bug report for more info: https://bugs.php.net/bug.php?id=53789 2. Unless there is a very good reason for keeping them, I think '--enable-libxml' and especially '--enable-mysqlnd' should be removed from the default set of arguments. Make these two part of the options dialog, if you want, but there are plenty of installations that have no need for any MySQL or XML functionality. Why compile these into the core by default? Actually, I now realize that changing 'CONFIGURE_ARGS=' to 'CONFIGURE_ARGS+=' wouldn't help me, because --disable-all would negate --enable-hash, which I was planning to specify. No, it won't negate it. --disable-all means start with an empty set and for each --enable-foo add foo to the set. You can add to CONFIGURE_ARGS using a Makefile.local which is included at bsd.port.pre.mk time. As for removing --enable-libxml, it seems to be required when building the port (maybe for fpm?), but --enable-mysqlnd should definitely be removed by default. As far as I can tell, --enable-mysqlnd does not add to dependencies, as: make -C /usr/ports/lang/php5 all-depends-list shows me as does: % ls /var/db/pkg|egrep 'php|mysql' php5-5.3.9 -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
Hi,
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
In theory they're useful for:
post-install:
@(cd ${PREFIX} foo-magic ${WWWDIR_REL} ${DATADIR_REL})
But if this only happens in theory, there's no use in keeping it around.
-- Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
On 02/10/2012 17:57, rfl...@acsalaska.net wrote:
Hi,
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
In theory they're useful for:
post-install:
@(cd ${PREFIX} foo-magic ${WWWDIR_REL} ${DATADIR_REL})
But if this only happens in theory, there's no use in keeping it around.
Did you see my original post in this thread?
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What use is WWWDIR_REL?
On 02/10/2012 17:57, rfl...@acsalaska.net wrote:
Hi,
Clearly I'm missing something then, because I don't see how they
accomplish anything useful. Perhaps you can enlighten me? There is
nothing in the CVS log that even mentions them, never mind why they were
added (bad portmgr, no cookie!).
In theory they're useful for:
post-install:
@(cd ${PREFIX} foo-magic ${WWWDIR_REL} ${DATADIR_REL})
But if this only happens in theory, there's no use in keeping it around.
Did you see my original post in this thread?
Yep, easily fixable with substitution, as long as people use $PREFIX and not
$LOCALBASE - in other words doc problem and I agree with your original post.
-- Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Requested changes to lang/php5 port
On Fri, Feb 10, 2012 at 8:43 PM, rfl...@acsalaska.net wrote: On Fri, Feb 10, 2012 at 12:41 PM, Maxim Khitrov m...@mxcrypt.com wrote: Hello, I'd like to request two minor changes to the lang/php5 port: 1. Change 'CONFIGURE_ARGS=' line to 'CONFIGURE_ARGS+=' to allow customizations to the arguments. One reason for this is that some extensions, like security/php5-hash, have to be compiled into the core. Otherwise, 'session.hash_function' option cannot use hash algorithms offered by that extension. See the following bug report for more info: https://bugs.php.net/bug.php?id=53789 2. Unless there is a very good reason for keeping them, I think '--enable-libxml' and especially '--enable-mysqlnd' should be removed from the default set of arguments. Make these two part of the options dialog, if you want, but there are plenty of installations that have no need for any MySQL or XML functionality. Why compile these into the core by default? Actually, I now realize that changing 'CONFIGURE_ARGS=' to 'CONFIGURE_ARGS+=' wouldn't help me, because --disable-all would negate --enable-hash, which I was planning to specify. No, it won't negate it. --disable-all means start with an empty set and for each --enable-foo add foo to the set. You can add to CONFIGURE_ARGS using a Makefile.local which is included at bsd.port.pre.mk time. Didn't know about Makefile.local, thanks! I tested the 'CONFIGURE_ARGS+=' solution and it does work. I was under the impression that order mattered. That method is slightly better than Makefile.local, because I try to manage all port customizations with portconf. Otherwise, it's easy to forget all the changes you made to get things working exactly right. I also exclude /usr/ports from backups, so all settings would revert to their defaults if I ever had to re-extract the entire tree. As for removing --enable-libxml, it seems to be required when building the port (maybe for fpm?), but --enable-mysqlnd should definitely be removed by default. As far as I can tell, --enable-mysqlnd does not add to dependencies, as: make -C /usr/ports/lang/php5 all-depends-list shows me as does: % ls /var/db/pkg|egrep 'php|mysql' php5-5.3.9 True, but it's still unnecessary. It increases the size of all binaries (php, php-cgi, php-fpm) and adds a ton of useless information to phpinfo() output. I think that making it an option that is enabled by default is perfectly reasonable. I've attached a patch that does this. Tested it on FreeBSD 9.0-RELEASE amd64. - Max php5-mysqlnd.patch Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
