Hello!
Chavdar Ivanov wrote:
But I also remember having to force update devel/glib2, as was indeed
already suggested, although I don't know if this will solve your
problem.
this could be the solution. I updated pkgsrc. This caused also a glib2
update and afterwards gobject-introspection
On Tue, 30 Jun 2020 at 15:52, Riccardo Mottola
wrote:
>
> Hi,
>
> Chavdar Ivanov wrote:
> > FWIW I just rebuilt it on today's -current amd64 and -current pkgsrc;
> > it wasn't rebuilt during the last rolling-replace, so the package was
> > from early May; today it was also built right away.
>
>
Hi,
Chavdar Ivanov wrote:
FWIW I just rebuilt it on today's -current amd64 and -current pkgsrc;
it wasn't rebuilt during the last rolling-replace, so the package was
from early May; today it was also built right away.
let me check for updates of pkgsrc then...
I've had various troubles in
Hi Robert,
Robert Swindells wrote:
rerun the build twice, so I should see two crashes.
The laptop has 4GB of ram and the same swap this even is enough to
build geck and more or less rust... what's with gobject?
What have you set MAKE_JOBS to ?
I have set it to 2.
What is wrong with the
On Mon, 29 Jun 2020 12:32:27 +0200, Riccardo Mottola
wrote:
> [103/163] Generating gir-glib with a custom command
> FAILED: gir/GLib-2.0.gir
>
> [snip]
>
> distutils.errors.DistutilsExecError: command 'cpp' terminated by signal 11
>
> [snip]
>
> distutils.errors.CompileError: command 'cpp'
FWIW I just rebuilt it on today's -current amd64 and -current pkgsrc;
it wasn't rebuilt during the last rolling-replace, so the package was
from early May; today it was also built right away.
I've had various troubles in the past building this package; at one
stage it would not build unless
I wrote:
>What is wrong with the idea that you have run out of memory ?
OTOH, running top(1) at the same time as building it doesn't show
any particularly large processes.
On Mon, Jun 29, 2020 at 11:43:55PM +0200, Riccardo Mottola wrote:
> Hi Maya!
>
> m...@netbsd.org wrote:
> > > > distutils.errors.CompileError: command 'cpp' terminated by signal 11
> > > Usually any GCC crashes on widely used architectures are running out of
> > > RAM.
> > See `dmesg |tail` to
Riccardo Mottola wrote:
>m...@netbsd.org wrote:
distutils.errors.CompileError: command 'cpp' terminated by signal 11
>>> Usually any GCC crashes on widely used architectures are running out of
>>> RAM.
>> See `dmesg |tail` to see some messages related to out-of-RAM GCC
>> components
Hi Maya!
m...@netbsd.org wrote:
distutils.errors.CompileError: command 'cpp' terminated by signal 11
Usually any GCC crashes on widely used architectures are running out of
RAM.
See `dmesg |tail` to see some messages related to out-of-RAM GCC
components killed.
dmesg does not report
On Mon, Jun 29, 2020 at 04:02:43PM +, m...@netbsd.org wrote:
> On Mon, Jun 29, 2020 at 12:32:27PM +0200, Riccardo Mottola wrote:
> > distutils.errors.CompileError: command 'cpp' terminated by signal 11
>
> Usually any GCC crashes on widely used architectures are running out of
> RAM.
See
On Mon, Jun 29, 2020 at 12:32:27PM +0200, Riccardo Mottola wrote:
> distutils.errors.CompileError: command 'cpp' terminated by signal 11
Usually any GCC crashes on widely used architectures are running out of
RAM.
12 matches
Mail list logo
