pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: webkit-gtk fails to build
In the second occasion, the process was killed as there was no more
swap available. I increased the memory of the VM substantially and
also configured both of them to use ccache as suggested, placing the
ccache directory in a md device. Later.
On Tue, 22 Jan 2019 at 16:14, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> No luck. On the first box, with ccache setup, I got the same error as
> on my other message about the lack of DISPLAY:
> ....
> [ 43%] Linking CXX shared library ../../lib/libjavascriptcoregtk-4.0.so
> [ 44%] Built target JavaScriptCore
> Scanning dependencies of target JavaScriptCore-4-gir
> [ 44%] Generating ../../JavaScriptCore-4.0.gir
>
> ** (process:14188): CRITICAL **: 15:56:52.864: Failed to get
> connection to xfconfd: Cannot autolaunch D-Bus without X11 $DISPLAY
>
> ** (process:14203): CRITICAL **: 15:56:53.755: Failed to get
> connection to xfconfd: Cannot autolaunch D-Bus without X11 $DISPLAY
> [ 44%] Generating ../../JavaScriptCore-4.0.typelib
>
> ** (g-ir-compiler:17622): CRITICAL **: 15:56:53.986: Failed to get
> connection to xfconfd: Cannot autolaunch D-Bus without X11 $DISPLAY
> gmake[2]: *** [Source/JavaScriptCore/CMakeFiles/JavaScriptCore-4-gir.dir/build.make:61:
> JavaScriptCore-4.0.typelib] Trace/BPT trap (core dumped)
> gmake[1]: *** [CMakeFiles/Makefile2:587:
> Source/JavaScriptCore/CMakeFiles/JavaScriptCore-4-gir.dir/all] Error 2
> gmake: *** [Makefile:152: all] Error 2
> *** Error code 2
>
> Stop.
> make[1]: stopped in /usr/pkgsrc/www/webkit-gtk
> *** Error code 1
>
> Stop.
> make: stopped in /usr/pkgsrc/www/webkit-gtk....
>
> So the next try will be with a valid DISPLAY, I guess.
>
> On the second machine, where I started from scratch, I got:
> ----
> [ 59%] Building CXX object
> Source/WebCore/CMakeFiles/WebCore.dir/__/__/DerivedSources/WebCore/unified-sources/UnifiedSource20.cpp.o
> g++: internal compiler error: Killed (program cc1plus received signal 9)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://www.NetBSD.org/support/send-pr.html> for instructions.
> gmake[2]: *** [Source/WebCore/CMakeFiles/WebCore.dir/build.make:3786:
> Source/WebCore/CMakeFiles/WebCore.dir/__/__/DerivedSources/WebCore/unified-sources/UnifiedSource20.cpp.o]
> Error 4
> gmake[1]: *** [CMakeFiles/Makefile2:888:
> Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2
> gmake: *** [Makefile:152: all] Error 2
> *** Error code 2
>
> Stop.
> make[1]: stopped in /usr/pkgsrc/www/webkit-gtk
> *** Error code 1
>
> Stop.
>
> which is perhaps an exhaused resource - it is just 2CPU 2GB VirtualBox
> guest. I'll boost it and try again.
>
> As I said, I am not particularly bohered by the lack of the package,
> but by the points one could get to whilst using pkgsrc...
>
>
> On Tue, 22 Jan 2019 at 14:57, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> >
> > Thanks for the tip! I'll try it, haven't so far. I am actually trying
> > to build it on a copletely different machine, starting with an empty
> > /usr/pkg, on -current as well (albeit a bit older, from early
> > January).
> >
> > On Tue, 22 Jan 2019 at 14:53, Greg Troxel <gdt%lexort.com@localhost> wrote:
> > >
> > > Chavdar Ivanov <ci4ic4%gmail.com@localhost> writes:
> > >
> > > >> This can often be a symptom of building where the path is a symlink.
> > > >>
> > > >> make clean, and then
> > > >>
> > > >> cd `pwd -P`
> > > >
> > > > I had it tried twice before, always cleaning. Also:
> > > > ...
> > > > # pwd
> > > > /usr/pkgsrc/www/webkit-gtk
> > > > # pwd -P
> > > > /usr/pkgsrc/www/webkit-gtk
> > > > ...
> > > >
> > > > (pkgsrc is on /).
> > >
> > > It sounds like that is not the issue.
> > >
> > > > I cleaned PATH and am trying again. There were no suspicious links,
> > > > except /usr/src and /usr/xsrc, but these should not have been used; I
> > > > deleted them anyway.
> > >
> > > So proabbly something else
> > >
> > > > Trouble is, it happens at 92% of the execution, and it takes hours to
> > > > get there...
> > >
> > > ccache!
> > >
> > > Seriously, I use ccache for pkgsrc, and it helps a lot, especially for
> > > debugging.
> > >
> > > CCACHE_DIR?= ${HOME}/.ccache
> > > PKGSRC_COMPILER= ccache gcc
> > >
> > > (if you are using gcc)
> > >
> > > and do 'ccache -M5G' which is a reasonable size.
> > >
> > > It's fine for ~/.ccache to be a symlink off someplace.
> > >
> > >
> > > So all in all somebody will have to trace what's happening.
> >
> >
> >
> > --
> > ----
>
>
>
> --
> ----
--
----
Home |
Main Index |
Thread Index |
Old Index