Re: cpuminer mines only on one core regardless of "--threads" option

On 2014-02-18 15:24, Andrey Chernov wrote: > On 14.01.2014 17:55, Volodymyr Kostyrko wrote: >> 14.01.2014 15:01, Alexander: >>> on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer >>> from ports and by "pkg install" - result is the same - minerd mines >>> only on one core regardless

Re: Dovecot

On 02/18/14 18:54, Jos Chrispijn wrote: Hi Andrei, Andrei Brezan: You can check /var/db/ports/postfix/options to see what options you have for postfix. I think it's easier if you can tell us the output of "uname -a" plus the exact command you try when you get this error. I'm not sure what you

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

RFC: bsd.port.mk needs some changes around plist processing

Greetings, we've recently seen that the docbook ports were broken, and while the ports now build, they still cause leftover directories; Details in PR 186882: Sample log from Tinderbox:

Re: cpuminer mines only on one core regardless of "--threads" option

On 19.02.2014 12:42, Martin Matuska wrote: > Patch committed. Thanx. BTW, it is accepted in the upstream too. > It would be cool if cpuminer was compilable with clang, too. Running included in the sources ./nomacro.pl before ./configure supposed to fix clang, but I don't check it. -- http://ac

Re: Error build the port devel/glib20

On Fri, 14 Feb 2014 16:47:55 + Mark Knight wrote: > Ah, okay thanks. I just tried that but cups-base still blew up. I'll > wait patiently for the PRs to be actioned since I have a workaround. > Thanks for all of your help! I had another look at it and it turns out to be problem during installa

Re: [patch] sysutils/beadm

On 2/13/2014 4:19 PM, Andrew Hotlab wrote: > First of all, thank you very much for the good work with this port. I'm sure > it's changing the life of a lot FreeBSD system administrators! > > In my setup I have the following layout (several datasets for /usr, /var, > etc.): > > NAME

Re: GSSAPI and Heimdal in Base

On 2/17/2014 5:23 PM, Robert Simmons wrote: > Actually both port and base are 1.5.2. Base was updated in Apr 2012: > http://svnweb.freebsd.org/base?view=revision&revision=234027 > > Both 9.x and 10.0 have Heimdal 1.5.2, same version in ports. > > The Heimdal project's current stable version is ac

Re: misc/186883: last update of docbook broke building kdelibs

Em Qua, 2014-02-19 às 13:58 +0100, Antoine Brodin escreveu: > Please try patch below > Kdelibs expects to find docbookx.dtd in > share/xml/docbook/${DOCBOOKXML_CURRENTDTD_VERSION} , not in a subdir > > Index: textproc/docbook-xml/Makefile >

Re: misc/186883: last update of docbook broke building kdelibs

On 2/19/2014 8:37 AM, Sergio de Almeida Lenzi wrote: Em Qua, 2014-02-19 às 13:58 +0100, Antoine Brodin escreveu: Please try patch below Kdelibs expects to find docbookx.dtd in share/xml/docbook/${DOCBOOKXML_CURRENTDTD_VERSION} , not in a subdir Index: textproc/docbook-xml/Makefile

[QAT] r345043: 5x success, 2x configure_error, 1x leftovers, 1x coredump, 2x depend (configure_error in www/seamonkey), 1x depend (coredump in www/seamonkey)

Update to 2.24 Submitted by: Jan Beich Security: http://www.vuxml.org/freebsd/1753f0ff-8dd5-11e3-9b45-b4b52fce4ce8.html - Build ID: 20140219092600-15858 Job owner: b...@freebsd.org Buildtime:

Re: Ports revision bump?

+--On 18 février 2014 19:53:45 +0100 Jos Chrispijn wrote: |Dear group, |Just ran into a ports issue for Docbook 4.x.x |Can you tell me how to solve this? I'm not exactly sure what was the problem, but it should be fixed in r345097. Regards, -- Mathieu Arnold ___

Re: last update of docbook broke KDE4

+--On 18 février 2014 19:17:35 -0500 "Chad J. Milios" wrote: | On 2/18/2014 2:13 PM, Sergio de Almeida Lenzi wrote: |> FreeBSD freebsd10.toontown 10.0-RELEASE FreeBSD 10.0-RELEASE #0 |> r261076M: Thu Jan 23 21:21:09 BRST 2014 |> |> -- The following REQUIRED packages have not been found: |> |>

What should be in scripts shebangs for python2?

Hello, Freebsd-ports. My port uses some pythons scripts to configure (it is not pythonn-related by itself, only authors of this software use python scripts on build stage). How should I patch these scripts to work? It looks like /usr/local/bin/python2 is installed by devel/python2 port, and USE

Re: What should be in scripts shebangs for python2?

On Wed, 19 Feb 2014 19:02:01 +0400 Lev Serebryakov wrote: > Hello, Freebsd-ports. > > My port uses some pythons scripts to configure (it is not pythonn-related > by itself, only authors of this software use python scripts on build > stage). > > How should I patch these scripts to work? It loo

Re: What should be in scripts shebangs for python2?

Lev Serebryakov : Hello, Freebsd-ports. My port uses some pythons scripts to configure (it is not pythonn-related by itself, only authors of this software use python scripts on build stage). How should I patch these scripts to work? It looks like /usr/local/bin/python2 is installed by devel

RE: [patch] sysutils/beadm

> Date: Wed, 19 Feb 2014 07:27:45 -0600 > From: bdrew...@freebsd.org > To: andrew.hot...@hotmail.com > CC: po...@freebsd.org; verma...@interia.pl > Subject: Re: [patch] sysutils/beadm > > On 2/13/2014 4:19 PM, Andrew Hotlab wrote: >> First of all, thank you

Re: Issues with postmaster after freebsd-update

On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > pkg_libchk -o | grep icu | cut -d: -f1 | sort | uniq > ~/reinstall-ports > portmaster -D `cat ~/reinstall-ports` > > When all of the ports reported have been re-installed: > rm ~/reinstall-ports > pkg_libchk -o Thanks, I will give that a try if t

dns/djbdns [do-package] Error code 1

there seems to be a timing issue. can anyone else please confirm this problem is happening? I haven't gone ahead and tried any non-default values of vfs.timestamp_precision. make package fails 26/30 times make && sleep 1 && make package succeeds 50/50 times Thanks in advance. here is the ful

Re: dns/djbdns [do-package] Error code 1

Interesting, I can't seem to replicate it here. It doesn't seem like MAKE_JOBS_UNSAFE would apply, but perhaps try that? On 02/19, Chad J. Milios wrote: > there seems to be a timing issue. can anyone else please confirm this > problem is happening? I haven't gone ahead and tried any non-default

Re: dns/djbdns [do-package] Error code 1

Oh yeah, I probably should have mentioned I'm on 9.2-RELEASE/amd64 with all ZFS file systems (except tmpfs /tmp). I'll give that a shot and report back, usually woulda been my first stab at it but i too had a feeling that just didnt seem to be applicable in this case. I'll have to try it out to

[QAT] r345133: 4x leftovers

Disable gnome-panel 2.x support. It will go away in the GNOME 3 import. - Build ID: 20140219190800-32433 Job owner: k...@freebsd.org Buildtime: 6 minutes Enddate: Wed, 19 Feb 2014 19:14:2

Re: FreeBSD Port: strongswan-5.1.1_1

Hello Dewayne - >> 21[KNL] adding PF_ROUTE route failed: Invalid argument >> 21[KNL] installing route failed: 192.68.1.1/32 via (null) src %any dev vtnet1 > > Clemens, > I only use FreeBSD 9.2Stable and Strongswan 5.1.1 performs nicely. > After setting knl=4 in charon debug, I received this: >

RE: [patch] sysutils/beadm

Hi, I will try to test that patch then, I will reply when I'm done with info about issues or info about commit ;) Regards, vermaden Od: "Andrew Hotlab" Do: "Bryan Drewery" ; Wysłane: 17:18 Środa 2014-02-19 Temat: RE: [patch] sysutils/beadm > > > Date:

Re: GSSAPI and Heimdal in Base

On 20/02/2014 12:29 AM, Bryan Drewery wrote: > On 2/17/2014 5:23 PM, Robert Simmons wrote: >> Actually both port and base are 1.5.2. Base was updated in Apr 2012: >> http://svnweb.freebsd.org/base?view=revision&revision=234027 >> >> Both 9.x and 10.0 have Heimdal 1.5.2, same version in ports. >> >

Re: FreeBSD Port: strongswan-5.1.1_1

On 19/02/2014 2:31 AM, Clemens Schrimpe wrote: > On 18.02.2014, at 16:12, Francois ten Krooden wrote: > >> I will have a look on my test setup with FreeBSD to see if I can get the >> same error. > Thank you. Watch for messages re: PF_ROUTE failed, like these: > > 21[KNL] adding PF_ROUTE route fa

[CFT] finance/grisbi: upgrade to 0.9.99

Hello, This is a call for test: 0.9.99 is an unstable version of Grisbi, surely the latest before 1.0. There is no need for a finance/grisbi-devel, and I'm just pushing the patch at . I won't commit it - just waiting for the next stable version - b

VirtualBox & vim no longer building

Here's the build logs with details: https://dl.dropboxusercontent.com/u/141097/virtualbox-ose-4.3.6.log https://dl.dropboxusercontent.com/u/141097/vim-7.4.182.log ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freeb

textproc/docbook-utils fails to build

Now that everything has been committed, most of the docbook stuff builds, but docbook-utils fails with what appears to be a typo with an errant \n in a file name: I get a huge number of near identical errors similar to these: jade:/usr/local/share/xml/docbook/catalog:6:8:E: cannot open "/usr/local/

Re: textproc/docbook-utils fails to build

Am 20.02.2014 00:12, schrieb Kevin Oberman: > Now that everything has been committed, most of the docbook stuff builds, > but docbook-utils fails with what appears to be a typo with an errant \n in > a file name: > I get a huge number of near identical errors similar to these: > jade:/usr/local/sha

the docbook updates fisco continues...

The saga of the untested or inadequately test docbook updates of the last ___ 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: textproc/docbook-utils fails to build

On Wed, Feb 19, 2014 at 3:14 PM, Matthias Andree wrote: > Am 20.02.2014 00:12, schrieb Kevin Oberman: > > Now that everything has been committed, most of the docbook stuff builds, > > but docbook-utils fails with what appears to be a typo with an errant \n > in > > a file name: > > I get a huge nu

How do submit updates to ports?

How do I send updates to ports that I created/maintain? smime.p7s Description: S/MIME Cryptographic Signature

Re: How do submit updates to ports?

Daniel Morante wrote: > How do I send updates to ports that I created/maintain? Send a PR, either by using send-pr(1) or through the web interface at http://www.freebsd.org/send-pr.html If you are the maintainer, be sure to set the class to maintainer-update. AvW -- I'm not completely useles

Unable to build kfelibs (not docbook)

Well, I have gotten docbook updated. I now have five docbook ports and docbook-utils builds correctly. But I still can't build kdelibs. It now configures fine, but: Scanning dependencies of target docbookl10nhelper [ 9%] Built target threadweaver [ 9%] Building CXX object kdoctools/CMakeFiles/doc

Re: Unable to build kfelibs (not docbook)

On Wed, Feb 19, 2014 at 9:45 PM, Kevin Oberman wrote: > Well, I have gotten docbook updated. I now have five docbook ports and > docbook-utils builds correctly. But I still can't build kdelibs. It now > configures fine, but: > Scanning dependencies of target docbookl10nhelper > [ 9%] Built target

docbook updates fiasco continues...

Wednesday's round of docbook updates broke all the docbook ports fixed yesterday, plus other ports that depend upon docbook stuff. On my system the latter appear to include sysutils/polkit graphics/colord graphics/giflib sysutils/policykit devel/git

Re: Unable to build kfelibs (not docbook)

On Wed, Feb 19, 2014 at 8:54 PM, Scot Hetzel wrote: > On Wed, Feb 19, 2014 at 9:45 PM, Kevin Oberman > wrote: > > Well, I have gotten docbook updated. I now have five docbook ports and > > docbook-utils builds correctly. But I still can't build kdelibs. It now > > configures fine, but: > > Scann

Re: How do submit updates to ports?

El 20/02/2014 02:28, "A.J. 'Fonz' van Werven" escribió: > > Daniel Morante wrote: > > > How do I send updates to ports that I created/maintain? > > Send a PR, either by using send-pr(1) or through the web interface at > http://www.freebsd.org/send-pr.html > > If you are the maintainer, be sure to

Re: What should be in scripts shebangs for python2?

Hello, Marcus. You wrote 19 февраля 2014 г., 19:55:00: MvA> In short: MvA> * Use ${PYTHON_CMD} to replace the shebang lines or references of the MvA> python command So, it is not possible to use "static" patch? It is pity :( MvA> * Use the proper supported python version (yes for any, 2 or 3