On Sat, Oct 17, 2020 at 04:11:07PM -0500, rhubarbpieguy--- via blfs-support 
wrote:
> 
> Compiling QtWebEngine fails with the following end output:
> 
>    make[3]: *** No rule to make target 
> '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core/release/QtWebEngineCore.stamp',
> needed by '../../lib/libQt5WebEngineCore.so.5.15.0'.  Stop.
>    make[3]: Leaving directory
> '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
>    make[2]: *** [Makefile:132: sub-core_module-pro-install_subtargets] Error
> 2
>    make[2]: Leaving directory
> '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
>    make[1]: *** [Makefile:92: sub-core-install_subtargets] Error 2
>    make[1]: Leaving directory
> '/sources/qtwebengine-everywhere-src-5.15.0/build/src'
>    make: *** [Makefile:61: sub-src-install_subtargets] Error 2
> 
> However, the problem appears to start with 'make: *** [Makefile:49:
> sub-src-make_first] Error 2.'
> 
> Qt5 appears to have compiled without error and I believe I'm following the
> documentation.  I tried 'NINJA_JOBS=4 make' without success?
> 

I can recall that at times building qtwebengine with NINJA_JOBS has
been a right PITA, and my notes suggest that passing VERBOSE=1 to
make definitely stopped it using NINJA_JOBS.

I think that on one occasion I was able to find the error by
rerunning make in the broken build (and writing to a file, but I
also recall that there is no output until the build ends).

If you need to restrict the number of cores (e.g. insufficient
DRAM), taking cores offline (not core 0!) by echoing 0 to
/sys/devices/system/cpu/cpu<N>/online etc for the cores you wish to
disable (on intel, probably the highest numbered if SMT, on zen the
"slow" cores might vary).  But that's just a workaround.

However, looking at your output I'm puzzled (unless the error was
during the install) - Output from 'make' (e.g. at start of line,
there are a lot of filenames which include make in them) doesn't
really appear in my log from the main build except in

make[3]: Nothing to be done for 'first'.
[1/185] CXX base/files/file_path_constants.o

 (running make Makefile.gn to put things together, the part that
 needs a static lib, which ends at

[185/185] LINK gn
make[3]: Nothing to be done for 'first'.

 and then a little later

make[3]: Entering directory 
'/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core'
ninja -v  -C 
/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core/release 
QtWebEngineCore
ninja: Entering directory 
`/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core/release'
[1/18172] touch obj/base/allocator/allocator.stamp

 and nothing more until

[18172/18172] touch QtWebEngineCore.stamp
make[3]: Leaving directory 
'/scratch/working/qtwebengine-everywhere-src-5.15.0/build/src/core'

and then after that I see 'make' bouncing around directories,
removing files, (re) creating .so libs - I assumed that was part of
the install, but perhaps it is the end of 'make' itself.  If so, did
all the ninja targets complete ?

ĸen
-- 
The people next door oppress me all night long. I tell them: I work
all day, a man's got to have some time to learn to play the tuba.
That's oppression, that is.    [ Guards! Guards! ]
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to