Date: Wed, 16 May 2012 06:36:22 -0400 From: Michael Scheidell <scheidell@FreeBSD.org> To: <freebsd-ports@freebsd.org> Subject: Re: how to find the number of processor cores Message-ID: <4FB38326.4000806@FreeBSD.org> In-Reply-To: <4FB37E61.5030500@gmail.com> References: <CAERaTk_7s%2Bk-Z3fKr31uYf=ry0oio_qmgfJMKPACT0yK832qqg@mail.gmail.com> <4FB36669.8060803@FreeBSD.org> <CAERaTk-JKJ22W=WBsYpaNfys=HbR7KHFBbwrM_d0cwkSmRYwVA@mail.gmail.com> <4FB37E61.5030500@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/16/12 6:16 AM, Vitaly Magerya wrote: > Svyatoslav Lempert wrote: >>> Try to describe why/ and why you want to do this. >> http://www.freebsd.org/cgi/query-pr.cgi?pr=167953 >> miwi has this pr, I suggest you make sure you work this out with him, and/or the ports maintainer. ports@mcdermottroe.com miwi is not only a ports committer, but a senior developer working deep in the heat of FreeBSD. also, don't be surprised if the maintainer of that port ports@mcdermottroe.com rejects your patch. >>> Try: >>> >>> CPUS!= ${SYSCTL} -n kern.smp.cpus > What if the package was built on one machine, but is installed on > another one? The number of CPUs during the build is meaningless; you > need to test for those at runtime (or find another workaround). Like Vitaly said. you need to find a better way to fix the problem. maybe some runtime test. it looks like the upstream needs fixing as well. Not only is this broken for so many reasons, but puts an undue burden on make index. (you did run portlint -abt and read the warning, didn't you?) -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FB38326.4000806>