On Mon, Aug 5, 2019, at 20:23, Stuart Henderson wrote:
> On 2019/08/05 18:58, Jeremie Courreges-Anglas wrote:
> > On Mon, Aug 05 2019, Stuart Henderson <[email protected]> wrote:
> > > On 2019/08/05 17:25, Timo Myyrä wrote:
> > >> Juan Francisco Cantero Hurtado <[email protected]> writes:
> >
> > [...]
> >
> > >> > Could you test this patch?.
> > >> >
> > >> >
> > >> > diff --git Makefile Makefile
> > >> > index 88a777f7c30..7547cf59c6c 100644
> > >> > --- Makefile
> > >> > +++ Makefile
> > >> > @@ -39,7 +39,8 @@ NO_TEST = Yes
> > >> > GERBIL_ROOT = ${PREFIX}/gerbil
> > >> >
> > >> > do-build:
> > >> > - cd ${WRKSRC}/src && ulimit -n 1024 && ${SETENV} ${MAKE_ENV}
> > >> > ./build.sh
> > >> > + cd ${WRKSRC}/src && ulimit -n 1024 -s 16384 && \
> > >> > + ${SETENV} ${MAKE_ENV} ./build.sh
> > >> >
> > >> > do-install:
> > >> > ${INSTALL_DATA_DIR} ${GERBIL_ROOT}
> > >
> > > Trying that in my next build (though it would seem odd for it to require
> > > more stack on one machine than another?)
>
> Unsurprisingly it didn't help.
>
> > Or maybe amd64.p and exopi don't use the same limits (login.conf)?
> > naddy, ajacoutot?
>
> On i386 I did copy login.conf to the new machines.
>
> Same results building lang/gerbil with ports-gcc.
>
>
Gerbil uses lang/gambit to compile code so I think both would need to be
compiled with gcc.
Though tags aren't strictly needed for the port and can be disabled.
Timo
