Is there any reason to keep sysutils/rc_subr?
I'm wondering if there is any reason to keep sysutils/rc_subr around? In bsd.port.mk the default sub for %%RC_SUBR%% is already /etc/rc.subr, and all supported platforms have always had that file. After the release of 8.0 I'd like to do the following: 1. Deprecate sysutils/rc_subr 2. Update all ports rc.d scripts that currently use %%RC_SUBR%% to use /etc/rc.subr instead. 3. Simplify any ports Makefiles that depend on sysutils/rc_subr 4. Simplify bsd.port.mk I also think it would be reasonable to update the Handbook section on ports rc.d scripts to use /etc/rc.subr now. Any objections? Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!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: Issues with devel/boost-* on Sparc64
Alexander, good day.
Wed, Nov 11, 2009 at 11:04:59PM +0300, Alexander Churanov wrote:
It seems that I have found a workaround. It is to store the address of
the variable in a register and then issue the CAS instruction, which
only accepts register for an address. I am currently testing it.
I hadn't seen the code you're testing, but it seems to me that the
attached patch should automatically take care of making the address to
be in some register (if it isn't already in the register). It compiles
well, and even works as a stand-alone function, but I hadn't yet tested
if boost built with such a atomic primitive really works fine. Have
some $JOB to do prior to the testing.
If you're storing the address in the register manually -- there is no
need for it: you can use assembly constraints; this also makes less
headache, because compiler decides what register should be allocated by
its own and typically it is doing this job well. Anyway, I hadn't seen
your patch, so may be you already doing this.
--
Eygene
____ _.--. #
\`.|\.....-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual
)/' _/ \ `-_, /# while single-stepping the kernel.
`-' `\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / #-- FreeBSD Developers handbook
{_.-``-' {_/#
--- boost/smart_ptr/detail/sp_counted_base_gcc_sparc.hpp.orig 2009-03-02 11:22:16.0 -0500
+++ boost/smart_ptr/detail/sp_counted_base_gcc_sparc.hpp 2009-11-12 09:51:25.0 -0500
@@ -30,10 +30,10 @@
inline int32_t compare_and_swap( int32_t * dest_, int32_t compare_, int32_t swap_ )
{
-__asm__ __volatile__( cas %0, %2, %1
-: +m (*dest_), +r (swap_)
-: r (compare_)
-: memory );
+__asm__ __volatile__( casa [%3] 0x80, %2, %1
+ : =m (*dest_), =r (swap_)
+ : r (compare_), r (dest_), 1 (swap_), m (*dest_)
+ : memory );
return swap_;
}
___
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: Issues with devel/boost-* on Sparc64
Eygene, Your solution is clearly more appropriate. I'll test it. Mine is attached. Alexander Churanov patch-boost_smart_ptr_detail_sp_counted_base_gcc_sparc.hpp 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
devel/pear1.9.0 build problems
Ok seems like I had a memcache problem but after rebuilding pecl-memcache that is gone now. can someone give me an idea where or how to look for the errors in this build? It seems to only happen with pear. The is needed to keep mail/horde-imp working /usr/ports/devel/pear pkgdb -F --- Checking the package registry database [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 328 packages found (-1 +3) (...)... done] Stale dependency: horde-base-3.3.5 - pear-1.8.1 (devel/pear): pear-XML_Util-1.2.1 (score:25%) ? ([y]es/[n]o/[a]ll) [no] Install stale dependency? ([y]es/[n]o/[a]ll) [yes] ** Stale lock file was found. Removed. ** Stale lock file was found. Removed. [Gathering depends for devel/pear done] --- Installing 'pear-1.9.0' from a port (devel/pear) --- Building '/usr/ports/devel/pear' === Cleaning for pear-1.9.0 === Extracting for pear-1.9.0 = MD5 Checksum OK for pear-1.9.0.tar.bz2. = SHA256 Checksum OK for pear-1.9.0.tar.bz2. === Patching for pear-1.9.0 === Applying FreeBSD patches for pear-1.9.0 === Configuring for pear-1.9.0 --- Installing the new version via the port === Installing for pear-1.9.0 === pear-1.9.0 depends on file: /usr/local/include/php/main/php.h - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/pcre.so - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/xml.so - found === Generating temporary packing list === Checking if devel/pear already installed Bootstrapping Installer... Using previously install ... ok Extracting installer.. Using previously installed installer ... ok Preparing installer.. Updating channel doc.php.net Channel doc.php.net is up to date Updating channel pear.php.net Channel pear.php.net is up to date Updating channel pecl.php.net Channel pecl.php.net is up to date Installing selected packages.. Package: PEAR-stable.. already installed ... ok Package: Structures_Graph-stable.. already installed ... ok Package: Archive_Tar-stable... already installed ... ok Package: Console_Getopt-stable already installed ... ok *** Signal 11 Stop in /usr/ports/devel/pear. *** Error code 1 Stop in /usr/ports/devel/pear. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20091112-89890-wbklq1-0 env make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/pear(install error) Command failed [exit code 1]: /usr/local/sbin/portinstall devel/pear I don't know what could be causing this segmentation fault or what is causing it either. ___ 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: RFC: svn for make fetch
Any problems with something like this in bsd.svn.mk
Comments and suggestions welcome...
x-svn-export:
svn export -r${SVN_REV} ${SVN_URL} ${WRKSRC}
x-svn-tar:
${TAR} -cjvf ${DISTNAME}.tar.bz2 ${WRKSRC}
${RM} -rf ${WRKSRC}
x-svn-head:
SVN_REV != svn info ${SVN_URL} | grep ^Last Changed Rev:|awk
'${print $$4}'
x-svn-all: .ORDER x-svn-head x-svn-export x-svn-tar makesum
x-svn-prebuild: x-svn-export x-svn-tar checksum
___
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: Is there any reason to keep sysutils/rc_subr?
I probably should have added to my first post the fact that sysutils/rc_subr was originally added during the introduction of the rc.d system in the base as a mechanism for ports on older systems (to which rc.d would not be backported) to use it. Now that rc.d exists on all supported versions it is obsolete. (I mention this because I received a question about it in private mail.) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!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: devel/pear1.9.0 build problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rebuild php5 and try again. On Thu, Nov 12, 2009 at 09:59:26AM -0700, Agrapha wrote: Ok seems like I had a memcache problem but after rebuilding pecl-memcache that is gone now. can someone give me an idea where or how to look for the errors in this build? It seems to only happen with pear. The is needed to keep mail/horde-imp working /usr/ports/devel/pear pkgdb -F --- Checking the package registry database [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 328 packages found (-1 +3) (...)... done] Stale dependency: horde-base-3.3.5 - pear-1.8.1 (devel/pear): pear-XML_Util-1.2.1 (score:25%) ? ([y]es/[n]o/[a]ll) [no] Install stale dependency? ([y]es/[n]o/[a]ll) [yes] ** Stale lock file was found. Removed. ** Stale lock file was found. Removed. [Gathering depends for devel/pear done] --- Installing 'pear-1.9.0' from a port (devel/pear) --- Building '/usr/ports/devel/pear' === Cleaning for pear-1.9.0 === Extracting for pear-1.9.0 = MD5 Checksum OK for pear-1.9.0.tar.bz2. = SHA256 Checksum OK for pear-1.9.0.tar.bz2. === Patching for pear-1.9.0 === Applying FreeBSD patches for pear-1.9.0 === Configuring for pear-1.9.0 --- Installing the new version via the port === Installing for pear-1.9.0 === pear-1.9.0 depends on file: /usr/local/include/php/main/php.h - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/pcre.so - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/xml.so - found === Generating temporary packing list === Checking if devel/pear already installed Bootstrapping Installer... Using previously install ... ok Extracting installer.. Using previously installed installer ... ok Preparing installer.. Updating channel doc.php.net Channel doc.php.net is up to date Updating channel pear.php.net Channel pear.php.net is up to date Updating channel pecl.php.net Channel pecl.php.net is up to date Installing selected packages.. Package: PEAR-stable.. already installed ... ok Package: Structures_Graph-stable.. already installed ... ok Package: Archive_Tar-stable... already installed ... ok Package: Console_Getopt-stable already installed ... ok *** Signal 11 Stop in /usr/ports/devel/pear. *** Error code 1 Stop in /usr/ports/devel/pear. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20091112-89890-wbklq1-0 env make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/pear(install error) Command failed [exit code 1]: /usr/local/sbin/portinstall devel/pear I don't know what could be causing this segmentation fault or what is causing it either. ___ 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 - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkr8f1sACgkQdLJIhLHm/Ol1wwCgxK4wdhMxb5UWxuVOgBUelNN2 SwwAn0OySdckPMMI7O2cSnpYQZ3oHSO0 =BwjB -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: New port: sysutils/megacli waiting to commit
Doug Ambrisko wrote: Miroslav Lachman writes: | Doug Ambrisko wrote: [...] | Hi, | I am little confused by all these MegaRAID utilities available in ports. | (I am new to LSI MegaRAID). | | I have new Dell R610 with PERC6 identified as: | | mfi0:Dell PERC 6 port 0xfc00-0xfcff mem | 0xdf18-0xdf1b,0xdf1c-0xdf1f irq 16 at device 0.0 on pci3 | mfi0: Megaraid SAS driver Ver 3.00 | | What is the recommended tool to monitor (and manage) the state of the | PERC6 array? To monitor, I use syslog :-). I set in loader.conf hw.mfi.event_class=-2 so I see everything logged to dmesg/syslog of all events. To manage it I use a custom tool but MegaCli should work. There is a new tool that was added to freebsd mfiutil from Yahoo. Thank you for tip to mfiutil. I upgraded to 7-STABLE where mfiutil is also included and it seems simpler than MegaCli. I hope it will work without problems ;) | I also found on LSI website, that newer FreeBSD MegaCli is available: | 5.00.15 | | But I don't know if it supports previous HW or not. I have yet to see a MegaCli that isn't a super set of the prior. The API to the firmware has been stable. [...] 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: security/gnupg installing pth-2.0.7 causing problems
2009/11/9 David Southwell da...@vizion2000.net: 2009/11/8 David Southwell da...@vizion2000.net: What puzzles me is why the gnupg maintainer is so reluctant to provide alternative options to using pth when there are both system libraries and libpthread-stubs-0.1 available as an alternative. Dependencuy upon libpthread-stubs-0.1 enables gnupg to function without causing unnecessary problems. My understand is the pth was written for those systems which do not have alternative libraries for handling threads. My understanding is, stock gnupg dist depends on pth (even if described as optional). It seems using libpthread-stubs needs to modify configure script. Do you have a patch for this? -- Jun Kuriyama kuriy...@freebsd.org // FreeBSD Project kuriy...@s2factory.co.jp // S2 Factory, Inc. ___ 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: RFC: svn for make fetch
On Tue, Nov 10, 2009 at 10:28:17PM +0200, Eitan Adler wrote: Alright - I updated the wiki page to summarize the thread so far. I'd appreciate if people could comment on the spec part specifically. I'd like to see that section become much more specific (so that I could use it to unambiguously write something based off of it) I'm holding off on writing any new implementations at the moment to see where things head in terms of how things should be done. http://wiki.freebsd.org/EitanAdler/ports-svn Why only SVN? I'm not trying to be picky but if we start supporting this for SVN it's very easy to argue we should support it for some other VCS. Personally I think this kind of thing is best left up to the maintainer to use his/her custom scripts and not stuff support for it into the ports infrastructure. -- WXS ___ 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
