Re: WebKitGTK-2.52.5

Bruce Dubbs ([email protected] via blfs-dev Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.devel
Message-ID <[email protected]>
On 8/19/26 5:46 PM, Zeckma ([email protected] via blfs-dev Mailing List) wrote:
> On 8/19/26 15:58, Bruce Dubbs ([email protected] via blfs-dev
> Mailing List) wrote:
>  > I had a bit of a problem with building WebKitGTK-2.52.5 on a 13.1
>  > system. I'm using a system with 28 cores.  When I tried to build
>  > WebKitGTK-2.52.5 using all 28 cores, it failed to build.  The
>  > message was something about a file that was not complete.  I
>  > tried twice and it failed at the same point.  I then tried at -j8
>  > and the build was successful.
> 
> I suspect that this is a result of incomplete dependency information.
> I've run into this with samurai, a reimplementation of the Ninja
> build system, which runs into this issue a lot. But it isn't really
> the fault of samurai.
> 
> -j1 or a small amount of threads will conveniently get around the
> issue of missing dependency information, but if a large or
> larger amount of threads are used, a rule or target simply won't
> wait for another to complete, and bails. With dependency information,
> the rule will then wait for the dependent rule/target to complete
> before running.
> 
> With how large WebKitGTK is, I imagine this is such a case.
> Usually, this seems to happen more with Meson, and I haven't seen
> a CMake case yet. But typically this is very fixable if you know
> what depedency information is missing and what needs it.
> 
> Thus, the solution would be to fix the code. Another may be to use
> Make instead of Ninja and see if that helps, but Ninja due to its
> methodology happens to avoid most stuff like this except for lots
> of targets that big projects like WebKitGTK need. So if Make doesn't
> bear fruit or it's really inconsistent, either an admon (note,
> important, etc.) or fixing the build system would be my two
> recommendations.
> 
> What was your build error? May give a good clue as to what the target
> is that is missing the dependency information...

Right, I figured it is a dependency issue with a generated file.

I've overwritten the log.  I suppose I can run it again without the install. I'm 
still trying to update to Qt-6.11.2 so it will be a while until I can do that.

BYW, I noticed that qt6 patch has been incorporated into 6.11.2, but qtopcua still 
breaks.

   -- Bruce

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.