Re: Failure to build gobject-introspection
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 built fine! It is strange that an outdated dependency would cause a SIGSEGV... Thanks! Riccardo
Re: Failure to build 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. > > let me check for updates of pkgsrc then... > > > > I've had various troubles in the past building this package; at one > > stage it would not build unless DISPLAY was set to a working X > > server... (that problem was resolved at the time). > > I just tried building inside X11 (I usually avoid, since it steals some > RAM...) but it does not help Yes, I mentioned that particular problem with it was resolved at the time. 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. > > Riccardo Chavdar --
Re: Failure to build gobject-introspection
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 the past building this package; at one stage it would not build unless DISPLAY was set to a working X server... (that problem was resolved at the time). I just tried building inside X11 (I usually avoid, since it steals some RAM...) but it does not help Riccardo
Re: Failure to build gobject-introspection
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 idea that you have run out of memory ? Other people can build gobject-introspection fine, me included. Because I to not see a trace in dmesg of a process! I also kept "top" running while trying again and even with X11 running, I had about 1.3GB free RAM just before it consistently crashed. Riccardo
Re: Failure to build gobject-introspection
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' terminated by signal 11 I see this failure occasionally. Your "devel/glib2" has gotten out of sync. If you explicitly rebuild/replace "devel/glib2", "gobject-introspection" (and a number of other packages which exhibit the same failure) will then build without further problems. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Failure to build gobject-introspection
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 DISPLAY was set to a working X server... (that problem was resolved at the time). On Mon, 29 Jun 2020 at 23:32, Robert Swindells wrote: > > > 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. --
Re: Failure to build gobject-introspection
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.
Re: Failure to build gobject-introspection
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 see some messages related to out-of-RAM GCC > > components killed. > > dmesg does not report anything suspect since boot.. and I did try to 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? > > any better ideas? :-) > > true is that we have now changed GCC in base now.. and 8.4.0 is giving me > other issues... I was about to write that the usual failure for gobject-introspection is that /usr/pkg or pkgsrc is a symlink, before seeing "signal 11" which is SIGSEGV.
Re: Failure to build gobject-introspection
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 killed. > >dmesg does not report anything suspect since boot.. and I did try to >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 ? >any better ideas? :-) What is wrong with the idea that you have run out of memory ? Other people can build gobject-introspection fine, me included.
Re: Failure to build gobject-introspection
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 anything suspect since boot.. and I did try to 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? any better ideas? :-) true is that we have now changed GCC in base now.. and 8.4.0 is giving me other issues... Riccardo
Re: Failure to build gobject-introspection
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 `dmesg |tail` to see some messages related to out-of-RAM GCC components killed.
Re: Failure to build gobject-introspection
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.
