Re: Texmaker installation failed due to inability to build qt5 web engine

[Ryan Schmidt]

On Nov 4, 2022, at 07:03, Chris Jones wrote:

> Just on this point, if you don't want to have to build everything from 
> source, then you should not update your OS before MacPorts has deployed 
> buildbots for the new OS. You can check this at e.g.
> 
> https://build.macports.org/waterfall
> 
> and yes we do not yet have macOS13 in place. Ryan might be able to give an 
> idea of a timeline for this.

I can't give you any timeline yet.

Re: Texmaker installation failed due to inability to build qt5 web engine

[Chris Jones]

Apart from the glacial place of OS update migration (*every *app and 
dependency  is downloaded and built from source),


Just on this point, if you don't want to have to build everything from 
source, then you should not update your OS before MacPorts has deployed 
buildbots for the new OS. You can check this at e.g.


https://build.macports.org/waterfall

and yes we do not yet have macOS13 in place. Ryan might be able to give 
an idea of a timeline for this.


Chris

Re: Texmaker installation failed due to inability to build qt5 web engine

[Mojca Miklavec]

Dear Gregory,

On Fri, 4 Nov 2022 at 06:10, Gregory Dodwell wrote:
>
> :error:build Failed to build qt5-qtwebengine: command execution failed
...
> Other errors deep in the text-dump. Too long to paste here. Should I send a 
> .zip file of the build log somewhere? At a loose end.

The best way to report such issues is Trac where you can upload
main.log with complete logs of the failure:
https://trac.macports.org/wiki/Tickets

(It's nothing wrong if you ask for further advice on the list anyway,
but having the log available, or someone else with access to the
latest OS, is essential to be able to proceed).

Mojca

Texmaker installation failed due to inability to build qt5 web engine

[Gregory Dodwell]

Mac OS 13 Ventura
MacPorts version 2.8.0
Xcode 14.1 RC2 plus 14.1 RC2 command-line tools
M1 Macbook Pro

Ahh, the risks of going bleeding edge. -_-

Essential reason for Mac Ports for me is the LaTeX environment,
particularly for Texmaker — I'm a secretary for a volunteer organisation
and use it to generate our meeting agendas.

Everything was OK under MacPorts 2.8.0 with MacOS 12.6.1

Apart from the glacial place of OS update migration (*every *app and
dependency  is downloaded and built from source), so far so good — apart
from me mistyping and downloading MacPorts Sudo (which overrode my existing
Sudoers list).

Last para of the main.log:
"...

info:build Exit code: 2

:error:build Failed to build qt5-qtwebengine: command execution failed

:debug:build Error code: CHILDSTATUS 79065 2

:debug:build Backtrace: command execution failed

:debug:build while executing

:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"

:debug:build invoked from within

:debug:build "command_exec -callback portprogress::target_progress_callback
build"

:debug:build (procedure "portbuild::build_main" line 8)

:debug:build invoked from within

:debug:build "$procedure $targetname"

..."
Other errors deep in the text-dump. Too long to paste here. Should I send a
.zip file of the build log somewhere? At a loose end.

Greg./