Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-24 Thread Scott Andrews via blfs-support
On Sat, 24 Oct 2020 22:38:34 +0100
Ken Moffat via blfs-support 
wrote:

> On Sat, Oct 24, 2020 at 04:38:25PM -0400, Scott Andrews via
> blfs-support wrote:
> > On Thu, 22 Oct 2020 18:17:16 +0100
> > Ken Moffat via blfs-support
> >  wrote:
> >   
> > > On Mon, Oct 19, 2020 at 07:58:23AM -0400, Scott Andrews via
> > > blfs-support wrote:  
> > > > On Mon, 19 Oct 2020 02:32:39 +0100
> > > > Ken Moffat via blfs-support
> > > >  wrote:  
> >   
> > > On normal builds which use 'make' I always pass -O in my own
> > > MAKEFLAGS (with -j).  I don't recall if I ever passed that to
> > > qtwebengine, but recently I had not been doing that (the build
> > > system is very unusual, perhaps based on chrome).  But I'm now
> > > building qtwebengine.
> > > 
> > > Using 'make -O' (and letting ninja use its default number of jobs)
> > > the output from the first part (building gn) arrives
> > > target-by-target, but after that nothing has been written to
> > > stdout or stderr for the past 10 minutes while all 8 cores are
> > > churning away.  So no, for this using -O does not help.
> > > 
> > > ĸen  
> > 
> > Works on my system RPI4 *GB
> > All 4 cores are building away
> > Your system broke?
> > 
> > top - 16:35:13 up  8:09,  2 users,  load average: 7.73, 8.15, 5.88
> > Tasks: 199 total,   8 running, 191 sleeping,   0 stopped,   0 zombie
> > %Cpu(s): 66.2 us, 33.6 sy,  0.0 ni,  0.1 id,  0.0 wa,  0.0 hi,  0.2
> > si,  0.0 st 
> > MiB Mem :   7874.9 total,   5245.8 free,666.8 used,  1962.3
> > buff/cache 
> > MiB Swap:100.0 total, 95.5 free,  4.5used.   6777.1
> > avail Mem  
> 
> That was not the issue.  All cores were running, but using tail -f
> on the output (I was logging stdout and stderr to a file) I saw no
> output between the start of the main build and when it finished.  I
> had line-by line output until gn was linked (target 185 of
> Makefile.gn), then a few lines of make output before it entered
> build/src/core.  Then nothing until the build completed, at which
> point the output from all 18259 njatargets appeared.
> 
> ĸen

I am using rpmbuild -bb  |& tee 
Works for me for all packages I build including QtWebEngine
mine will pause for a few minutes and starts again, ninja builds
included.

Your system Broke?

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-24 Thread Ken Moffat via blfs-support
On Sat, Oct 24, 2020 at 04:38:25PM -0400, Scott Andrews via blfs-support wrote:
> On Thu, 22 Oct 2020 18:17:16 +0100
> Ken Moffat via blfs-support 
> wrote:
> 
> > On Mon, Oct 19, 2020 at 07:58:23AM -0400, Scott Andrews via
> > blfs-support wrote:
> > > On Mon, 19 Oct 2020 02:32:39 +0100
> > > Ken Moffat via blfs-support
> > >  wrote:
> 
> > On normal builds which use 'make' I always pass -O in my own
> > MAKEFLAGS (with -j).  I don't recall if I ever passed that to
> > qtwebengine, but recently I had not been doing that (the build
> > system is very unusual, perhaps based on chrome).  But I'm now
> > building qtwebengine.
> > 
> > Using 'make -O' (and letting ninja use its default number of jobs)
> > the output from the first part (building gn) arrives
> > target-by-target, but after that nothing has been written to stdout
> > or stderr for the past 10 minutes while all 8 cores are churning
> > away.  So no, for this using -O does not help.
> > 
> > ĸen
> 
> Works on my system RPI4 *GB
> All 4 cores are building away
> Your system broke?
> 
> top - 16:35:13 up  8:09,  2 users,  load average: 7.73, 8.15, 5.88
> Tasks: 199 total,   8 running, 191 sleeping,   0 stopped,   0 zombie
> %Cpu(s): 66.2 us, 33.6 sy,  0.0 ni,  0.1 id,  0.0 wa,  0.0 hi,  0.2
> si,  0.0 st 
> MiB Mem :   7874.9 total,   5245.8 free,666.8 used,  1962.3
> buff/cache 
> MiB Swap:100.0 total, 95.5 free,  4.5used.   6777.1 avail
> Mem

That was not the issue.  All cores were running, but using tail -f
on the output (I was logging stdout and stderr to a file) I saw no
output between the start of the main build and when it finished.  I
had line-by line output until gn was linked (target 185 of
Makefile.gn), then a few lines of make output before it entered
build/src/core.  Then nothing until the build completed, at which
point the output from all 18259 njatargets appeared.

ĸ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


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-24 Thread Scott Andrews via blfs-support
On Thu, 22 Oct 2020 18:17:16 +0100
Ken Moffat via blfs-support 
wrote:

> On Mon, Oct 19, 2020 at 07:58:23AM -0400, Scott Andrews via
> blfs-support wrote:
> > On Mon, 19 Oct 2020 02:32:39 +0100
> > Ken Moffat via blfs-support
> >  wrote:

> On normal builds which use 'make' I always pass -O in my own
> MAKEFLAGS (with -j).  I don't recall if I ever passed that to
> qtwebengine, but recently I had not been doing that (the build
> system is very unusual, perhaps based on chrome).  But I'm now
> building qtwebengine.
> 
> Using 'make -O' (and letting ninja use its default number of jobs)
> the output from the first part (building gn) arrives
> target-by-target, but after that nothing has been written to stdout
> or stderr for the past 10 minutes while all 8 cores are churning
> away.  So no, for this using -O does not help.
> 
> ĸen

Works on my system RPI4 *GB
All 4 cores are building away
Your system broke?

top - 16:35:13 up  8:09,  2 users,  load average: 7.73, 8.15, 5.88
Tasks: 199 total,   8 running, 191 sleeping,   0 stopped,   0 zombie
%Cpu(s): 66.2 us, 33.6 sy,  0.0 ni,  0.1 id,  0.0 wa,  0.0 hi,  0.2
si,  0.0 st 
MiB Mem :   7874.9 total,   5245.8 free,666.8 used,  1962.3
buff/cache 
MiB Swap:100.0 total, 95.5 free,  4.5used.   6777.1 avail
Mem
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-22 Thread rhubarbpieguy--- via blfs-support

On 10/20/20 9:00 AM, Pierre Labastie via blfs-support wrote:

On Tue, 2020-10-20 at 06:50 -0500, rhubarbpieguy--- via blfs-support
wrote:

Sorry, I was sloppy providing output.  The problem occurs with 'make'

and I included the tail end of 'make install.'   The error with
'make'
is:

  ninja: build stopped: subcommand failed.
  make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
  make[3]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
  make[2]: *** [Makefile:82: sub-gn_run-pro-make_first]
Error 2
  make[2]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
  make[1]: *** [Makefile:80: sub-core-make_first] Error 2
  make[1]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'
  make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?

Yes, that output is meaningless.  We need a dozen or more lines
before the
subcommand failed line.

-- Bruce


True, but we can already see it is in Makefile.gn.

A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
The gn tool needs that.  The only other thing on my systems which
needs it is binutils (in that case, for the testsuite).

More generally, when building in parallel the failure is sometimes
*many* lines before the ' Error ' report.

ĸen

I believe I have /usr/lib/libstdc++.a  I see the following libstdc++
files:

   /usr/lib/libstdc++.a
   /usr/lib/libstdc++fs.a
   /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6.0.28
   /usr/lib/libstdc++.so.6.0.28.dbg

I'm attaching more output generated with the '--output-sync' option
suggested in another response.  Perhaps that will show what I've done
wrong.



As pointed out by Christopher Gregory, the error is with some
incompatible changes in system icu. There is a patch in blfs-10.0 to
cure that. Have you applied it? (qtwebengine-everywhere-src-5.15.0-
consolidated_fixes-3.patch)

Pierre

My miscue was the patch.  I saw the patch in the documentation and 
sincerely thought I'd installed it via a bash script. Unfortunately, I 
modified the script I'd used for several releases.  My modification was 
misguided and I didn't see the patch hadn't applied (long story).  My 
lesson is to compile a package manually should it fail using a script.  
Live and learn.




--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-22 Thread Ken Moffat via blfs-support
On Mon, Oct 19, 2020 at 07:58:23AM -0400, Scott Andrews via blfs-support wrote:
> On Mon, 19 Oct 2020 02:32:39 +0100
> Ken Moffat via blfs-support 
> wrote:
> 
> > > > > 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).
> > > > > 
[...]
> 
> 5.4.1 Output During Parallel Execution
> When running several recipes in parallel the output from each recipe
> appears as soon as it is generated, with the result that messages from
> different recipes may be interspersed, sometimes even appearing on the
> same line. This can make reading the output very difficult.
> 
> To avoid this you can use the ‘--output-sync’ (‘-O’) option. This
> option instructs make to save the output from the commands it invokes
> and print it all once the commands are completed. Additionally, if
> there are multiple recursive make invocations running in parallel, they
> will communicate so that only one of them is generating output at a
> time.

On normal builds which use 'make' I always pass -O in my own
MAKEFLAGS (with -j).  I don't recall if I ever passed that to
qtwebengine, but recently I had not been doing that (the build
system is very unusual, perhaps based on chrome).  But I'm now
building qtwebengine.

Using 'make -O' (and letting ninja use its default number of jobs)
the output from the first part (building gn) arrives
target-by-target, but after that nothing has been written to stdout
or stderr for the past 10 minutes while all 8 cores are churning
away.  So no, for this using -O does not help.

ĸ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


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-20 Thread Pierre Labastie via blfs-support
On Tue, 2020-10-20 at 06:50 -0500, rhubarbpieguy--- via blfs-support
wrote:
> Sorry, I was sloppy providing output.  The problem occurs with 'make'
> > > > and I included the tail end of 'make install.'   The error with
> > > > 'make'
> > > > is:
> > > > 
> > > >  ninja: build stopped: subcommand failed.
> > > >  make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
> > > >  make[3]: Leaving directory
> > > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> > > >  make[2]: *** [Makefile:82: sub-gn_run-pro-make_first]
> > > > Error 2
> > > >  make[2]: Leaving directory
> > > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> > > >  make[1]: *** [Makefile:80: sub-core-make_first] Error 2
> > > >  make[1]: Leaving directory
> > > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src'
> > > >  make: *** [Makefile:49: sub-src-make_first] Error 2
> > > > 
> > > > Is there other output I should cite?
> > > Yes, that output is meaningless.  We need a dozen or more lines
> > > before the
> > > subcommand failed line.
> > > 
> > >-- Bruce
> > > 
> > True, but we can already see it is in Makefile.gn.
> > 
> > A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
> > The gn tool needs that.  The only other thing on my systems which
> > needs it is binutils (in that case, for the testsuite).
> > 
> > More generally, when building in parallel the failure is sometimes
> > *many* lines before the ' Error ' report.
> > 
> > ĸen
> 
> I believe I have /usr/lib/libstdc++.a  I see the following libstdc++
> files:
> 
>   /usr/lib/libstdc++.a
>   /usr/lib/libstdc++fs.a
>   /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6.0.28.dbg
> 
> I'm attaching more output generated with the '--output-sync' option 
> suggested in another response.  Perhaps that will show what I've done
> wrong.
> 
> 

As pointed out by Christopher Gregory, the error is with some
incompatible changes in system icu. There is a patch in blfs-10.0 to
cure that. Have you applied it? (qtwebengine-everywhere-src-5.15.0-
consolidated_fixes-3.patch)

Pierre

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-20 Thread Christopher Gregory via blfs-support


> Sent: Wednesday, October 21, 2020 at 12:50 AM
> From: "rhubarbpieguy--- via blfs-support" 
> 
> To: "Ken Moffat via blfs-support" 
> Cc: rhubarbpie...@vivaldi.net
> Subject: Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: 
> sub-src-make_first] Error 2 - BLFS 10.0
>
> Sorry, I was sloppy providing output.  The problem occurs with 'make'
> >>> and I included the tail end of 'make install.'   The error with 'make'
> >>> is:
> >>>
> >>>      ninja: build stopped: subcommand failed.
> >>>      make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
> >>>      make[3]: Leaving directory
> >>> '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> >>>      make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
> >>>      make[2]: Leaving directory
> >>> '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> >>>      make[1]: *** [Makefile:80: sub-core-make_first] Error 2
> >>>      make[1]: Leaving directory
> >>> '/sources/qtwebengine-everywhere-src-5.15.0/build/src'
> >>>      make: *** [Makefile:49: sub-src-make_first] Error 2
> >>>
> >>> Is there other output I should cite?
> >> Yes, that output is meaningless.  We need a dozen or more lines before the
> >> subcommand failed line.
> >>
> >>-- Bruce
> >>
> > True, but we can already see it is in Makefile.gn.
> >
> > A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
> > The gn tool needs that.  The only other thing on my systems which
> > needs it is binutils (in that case, for the testsuite).
> >
> > More generally, when building in parallel the failure is sometimes
> > *many* lines before the ' Error ' report.
> >
> > ĸen
> 
> I believe I have /usr/lib/libstdc++.a  I see the following libstdc++ files:
> 
>   /usr/lib/libstdc++.a
>   /usr/lib/libstdc++fs.a
>   /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6.0.28
>   /usr/lib/libstdc++.so.6.0.28.dbg
> 
> I'm attaching more output generated with the '--output-sync' option 
> suggested in another response.  Perhaps that will show what I've done wrong.
> 
> 
> -- 
> http://lists.linuxfromscratch.org/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 

Hello,

I took a look at the attachment, and did a google search on the error.  It 
seems that the issue is with the version of icu being used.  I have found a 
solution on gentoo, that patches the chromium source to build with this version 
of icu.  I am not sure how this will work with QtWebEngine version of chromium, 
but it should at least be a starting point.

The below is the patch that gentoo has made:

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d2da708be8232c1fde4417584c056e519d015087


This is the link to the filed bug:

https://bugs.gentoo.org/720100

The error that is indicated in the gentoo bug, matches the error in the 
attached log, so it *should* work.

Regards,

Christopher.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-20 Thread rhubarbpieguy--- via blfs-support

Sorry, I was sloppy providing output.  The problem occurs with 'make'

and I included the tail end of 'make install.'   The error with 'make'
is:

     ninja: build stopped: subcommand failed.
     make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
     make[3]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
     make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
     make[2]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
     make[1]: *** [Makefile:80: sub-core-make_first] Error 2
     make[1]: Leaving directory
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'
     make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?

Yes, that output is meaningless.  We need a dozen or more lines before the
subcommand failed line.

   -- Bruce


True, but we can already see it is in Makefile.gn.

A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
The gn tool needs that.  The only other thing on my systems which
needs it is binutils (in that case, for the testsuite).

More generally, when building in parallel the failure is sometimes
*many* lines before the ' Error ' report.

ĸen


I believe I have /usr/lib/libstdc++.a  I see the following libstdc++ files:

 /usr/lib/libstdc++.a
 /usr/lib/libstdc++fs.a
 /usr/lib/libstdc++.so -> libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6.0.28
 /usr/lib/libstdc++.so.6.0.28.dbg

I'm attaching more output generated with the '--output-sync' option 
suggested in another response.  Perhaps that will show what I've done wrong.



[10700/18215] /usr/bin/g++ -MMD -MF obj/v8/v8_base_without_compiler/log.o.d 
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_MINOR_MC -DV8_INTL_SUPPORT 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_EMBEDDED_BUILTINS -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_COMPRESS_POINTERS 
-DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_X64 
-DV8_HAVE_TARGET_OS -DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS 
-DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC 
-DUCHAR_TYPE=uint16_t -DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH 
-DV8_DEPRECATION_WARNINGS -Igen -I../../../../src/3rdparty/chromium 
-I../../../../src/3rdparty/chromium/v8 -Igen/v8 -Igen -Igen 
-I../../../../src/3rdparty/chromium/v8/include 
-I../../../../src/3rdparty/chromium/third_party/zlib -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables 
-fno-asynchronous-unwind-tables -fPIC -pipe -pthread -m64 -Wall 
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -Wno-deprecated-declarations 
-fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned 
-Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter 
-fno-omit-frame-pointer -fvisibility=hidden -Wno-strict-overflow 
-Wno-return-type -O3 -fno-ident -fdata-sections -ffunction-sections -g0 
-std=gnu++14 -Wno-narrowing -Wno-class-memaccess -Wno-attributes 
-Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof 
-Wno-return-type -Wno-deprecated-copy -fno-exceptions -fno-rtti 
-fvisibility-inlines-hidden -c 
../../../../src/3rdparty/chromium/v8/src/logging/log.cc -o 
obj/v8/v8_base_without_compiler/log.o
[10701/18215] /usr/bin/g++ -MMD -MF obj/v8/v8_base_without_compiler/strtod.o.d 
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD 
-DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DNO_UNWIND_TABLES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_MINOR_MC -DV8_INTL_SUPPORT 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_EMBEDDED_BUILTINS -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_COMPRESS_POINTERS 
-DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_X64 
-DV8_HAVE_TARGET_OS -DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH -DV8_DEPRECATION_WARNINGS 
-DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC 
-DUCHAR_TYPE=uint16_t -DV8_COMPRESS_POINTERS -DV8_31BIT_SMIS_ON_64BIT_ARCH 
-DV8_DEPRECATION_WARNINGS -Igen -I../../../../src/3rdparty/chromium 
-I../../../../src/3rdparty/chromium/v8 -Igen/v8 -Igen -Igen 
-I../../../../src/3rdparty/chromium/v8/include 
-I../../../../src/3rdparty/chromium/third_party/zlib -fno-strict-aliasing 

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-19 Thread Scott Andrews via blfs-support
On Mon, 19 Oct 2020 02:32:39 +0100
Ken Moffat via blfs-support 
wrote:

> On Sun, Oct 18, 2020 at 05:55:39PM -0500, Bruce Dubbs via
> blfs-support wrote:
> > On 10/18/20 5:16 PM, rhubarbpieguy--- via blfs-support wrote:  
> > > On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote:  
> > > > 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/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  
> > > 
> > > Sorry, I was sloppy providing output.  The problem occurs with
> > > 'make' and I included the tail end of 'make install.'   The error
> > > with 'make' is:
> > > 
> > >     ninja: build stopped: subcommand failed.
> > >     make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
> > >     make[3]: Leaving directory
> > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> > >     make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
> > >     make[2]: Leaving directory
> > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> > >     make[1]: *** [Makefile:80: sub-core-make_first] Error 2
> > >     make[1]: Leaving directory
> > > '/sources/qtwebengine-everywhere-src-5.15.0/build/src'
> > >     make: *** [Makefile:49: sub-src-make_first] Error 2
> > > 
> > > Is there other output I should cite?  
> > 
> > Yes, that output is meaningless.  We need a dozen or more lines
> > before the subcommand failed line.
> > 
> >   -- Bruce
> >   
> 
> True, 

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-18 Thread Ken Moffat via blfs-support
On Sun, Oct 18, 2020 at 05:55:39PM -0500, Bruce Dubbs via blfs-support wrote:
> On 10/18/20 5:16 PM, rhubarbpieguy--- via blfs-support wrote:
> > On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote:
> > > 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/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
> > 
> > Sorry, I was sloppy providing output.  The problem occurs with 'make'
> > and I included the tail end of 'make install.'   The error with 'make'
> > is:
> > 
> >     ninja: build stopped: subcommand failed.
> >     make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
> >     make[3]: Leaving directory
> > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> >     make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
> >     make[2]: Leaving directory
> > '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'
> >     make[1]: *** [Makefile:80: sub-core-make_first] Error 2
> >     make[1]: Leaving directory
> > '/sources/qtwebengine-everywhere-src-5.15.0/build/src'
> >     make: *** [Makefile:49: sub-src-make_first] Error 2
> > 
> > Is there other output I should cite?
> 
> Yes, that output is meaningless.  We need a dozen or more lines before the
> subcommand failed line.
> 
>   -- Bruce
> 

True, but we can already see it is in Makefile.gn.

A wild guess: has /usr/lib/libstdc++.a been hidden or deleted ?
The gn tool needs that.  The only other thing on my systems which
needs it is binutils (in that case, for the testsuite).

More generally, when building in parallel the failure is sometimes
*many* lines 

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-18 Thread Bruce Dubbs via blfs-support

On 10/18/20 5:16 PM, rhubarbpieguy--- via blfs-support wrote:

On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote:
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/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


Sorry, I was sloppy providing output.  The problem occurs with 'make' 
and I included the tail end of 'make install.'   The error with 'make' is:


    ninja: build stopped: subcommand failed.
    make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
    make[3]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

    make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
    make[2]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

    make[1]: *** [Makefile:80: sub-core-make_first] Error 2
    make[1]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'

    make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?


Yes, that output is meaningless.  We need a dozen or more lines before 
the subcommand failed line.


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-18 Thread rhubarbpieguy--- via blfs-support

On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote:

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/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


Sorry, I was sloppy providing output.  The problem occurs with 'make' 
and I included the tail end of 'make install.'   The error with 'make' is:


   ninja: build stopped: subcommand failed.
   make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1
   make[3]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

   make[2]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
   make[2]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src/core'

   make[1]: *** [Makefile:80: sub-core-make_first] Error 2
   make[1]: Leaving directory 
'/sources/qtwebengine-everywhere-src-5.15.0/build/src'

   make: *** [Makefile:49: sub-src-make_first] Error 2

Is there other output I should cite?


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

2020-10-17 Thread Ken Moffat via blfs-support
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/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