What to do when the port fails in poudriere with "Too many open files" ?

I have the port that builds fine without poudriere, but in poudriere it always fails with "Too many open files". This happens during the Java build. Where is the limit set in jail? /etc/login.conf doesn't have any limit. What to do in such case? Maybe there is some way to tell Java to limit

Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi)

On 2017-Jun-28, at 7:44 PM, Mark Millard wrote: > Is the below a BSDL vs. GPL DTS issue? > > In my attempt to build sysutils/u-boot-pine64 I got: > > OBJCOPY u-boot.srec > OBJCOPY u-boot-nodtb.bin > start=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 -d

/usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi)

Is the below a BSDL vs. GPL DTS issue? In my attempt to build sysutils/u-boot-pine64 I got: OBJCOPY u-boot.srec OBJCOPY u-boot-nodtb.bin start=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' ');

Re: math/R: Build failure after PORTREVISION for shlib change

Hi David, So far I haven't been able to reproduce any problems in an 11.0-RELEASE-p1 jail. Could you send your list of port options? If I can't reproduce any issues with the same options turned on, I will ask you for a full build log. Joseph signature.asc Description: PGP signature

Re: [RFC] Why FreeBSD ports should have branches by OS version

Hallo Julian H. Stacey, > But if one stands on a broken system & needs to recover, some simple > stock cc & sh tool/procedure with no dependencies is attractive, even if > one has to coble something ones self. I agree. maybe you like to try: $ less /usr/ports/ports-mgmt/pkg_jail/files/README

Re: math/R: Build failure after PORTREVISION for shlib change

On Wed, Jun 28, 2017 at 04:36:18PM -0300, Joseph Mingrone wrote: > Hi David, > > So far I haven't been able to reproduce any problems in an > 11.0-RELEASE-p1 jail. Could you send your list of port options? If I > can't reproduce any issues with the same options turned on, I will ask > you for a

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

On 2017-Jun-28, at 3:21 AM, Gerald Pfeifer wrote: > I am testing a patch for gcc5-devel right now that will disable fixincludes > (or rather its fixed files) being packaged. > > Should that work fine for you, I will push this back to gcc5 the following > days. > > That

Re: 'pkg version' strangeness - No valid entries found

On 28/06/2017 22:01, Adam Weinberger wrote: It may be a typo in your make.conf. If you have DEFAULT_VERSIONS+= perl5=lang/perl5.22 It should be DEFAULT_VERSIONS+= perl5=5.22 # Adam root# cat /etc/make.conf cat: /etc/make.conf: No such file or directory -andyf

Re: [RFC] Why FreeBSD ports should have branches by OS version

On Tue, 27 Jun 2017 18:16:01 -0500, Mark Linimon wrote: >On Tue, Jun 27, 2017 at 04:53:36PM -0400, scratch65...@att.net wrote: >> Since that's what I integrate for my dev use, I'd be happy to >> take a zero'th-order cut at defining it, if nobody else wants to. > >Fine. See

Re: 'pkg version' strangeness - No valid entries found

> On 28 Jun, 2017, at 4:24, Andy Farkas wrote: > > > root# cd /usr/ports > root# make index > Generating INDEX-11 - please wait..--- describe.accessibility --- > --- describe.arabic --- > --- describe.archivers --- > . > . > . > --- describe.x11-toolkits --- > ---

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,

'pkg version' strangeness - No valid entries found

root# cd /usr/ports root# make index Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- . . . --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/archivers/atool: no entry for

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

Hi everyone, I am testing a patch for gcc5-devel right now that will disable fixincludes (or rather its fixed files) being packaged. Should that work fine for you, I will push this back to gcc5 the following days. That said, the change that triggered this is what I would expect on CURRENT,

Re: [RFC] Why FreeBSD ports should have branches by OS version

On 27.06.2017 15:24, scratch65...@att.net wrote: [Default] On Mon, 26 Jun 2017 19:33:50 +, Grzegorz Junka wrote: we could start small with a just a handful of ports in a stable LTS (Long Term Support) branch. Develop processes around maintaining them, get some feedback

Re: [RFC] Why FreeBSD ports should have branches by OS version

On 26.06.2017 21:33, Grzegorz Junka wrote: On 26/06/2017 07:24, Torsten Zuehlsdorff wrote: Aloha David, I think the current process of having rolling-releases packages makes unpredictable upgrades as we have to manually check if the upgrade will be fine or not. When a user installs FreeBSD

Re: Should a package restart on upgrade itself

On 06/27/17 19:32, Miroslav Lachman wrote: > Matthias Fechner wrote on 2017/06/27 18:29: >> Dear all, >> >> it is always a pain if pkg upgrade a lot of packages to restart all >> services to make sure update/security fixes are applied to all running >> services. >> >> Is there an option in pkg

Re: Should a package restart on upgrade itself

On 27.06.2017 18:29, Matthias Fechner wrote: Dear all, it is always a pain if pkg upgrade a lot of packages to restart all services to make sure update/security fixes are applied to all running services. Is there an option in pkg that it restart services automatically or is it OK if I would

Re: [RFC] Why FreeBSD ports should have branches by OS version

from Mark Linimon: > On Tue, Jun 27, 2017 at 09:01:39PM +, Thomas Mueller wrote: > > raising the possibility of building for other targets. > Which is very much not hardly even the same as "they are being resistant > to change". In fact, about as far away from it as is possible to get. >