Opened 4 years ago

Closed 4 years ago

#59933 closed defect (worksforme)

qt5-qtdeclarative @5.14.0_0+debug build failure

Reported by: TheLastLovemark Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: qt5-qtdeclarative

Description

I attempted to install Wireshark using:

port install wireshark3 +cares +chmodbpf +debug +geoip +gnutls +kerberos5 +libsmi +lua +python37 +qt5 +zlib

There were errors during the qt5-qtdeclarative phase of the build:

The log info is attached.

Attachments (1)

qt5-qtdeclarative_main.log (888.0 KB) - added by TheLastLovemark 4 years ago.
qt5-qtdeclarative main log

Download all attachments as: .zip

Change History (13)

Changed 4 years ago by TheLastLovemark

Attachment: qt5-qtdeclarative_main.log added

qt5-qtdeclarative main log

comment:1 Changed 4 years ago by mf2k (Frank Schima)

Cc: MarcusCalhoun-Lopez removed
Keywords: qt5-qtdeclarative removed
Owner: set to MarcusCalhoun-Lopez
Status: newassigned

comment:2 Changed 4 years ago by jmroot (Joshua Root)

Summary: wireshark3 fails to build because of qt5-qtdeclarative build failureqt5-qtdeclarative @5.14.0_0+debug build failure
:info:build cp: qqmljsparser_p.h: No such file or directory
:info:build make[3]: *** [../../lib/QtQml.framework/Versions/5/Headers/5.14.0/QtQml/private/qqmljsparser_p.h] Error 1

comment:3 Changed 4 years ago by TheLastLovemark

What do I need to do?

comment:4 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Unfortunately, I cannot reproduce this error.
There is a similar bug report, but it is supposed to have been fixed.
This is just a guess, but perhaps an older version of qt5-qtdeclarative is causing the problem?
Please try running:

  • sudo port selfupdate
  • sudo port clean qt5-qtdeclarative
  • sudo port deactivate qt5-qtdeclarative
  • sudo port install qt5-qtdeclarative

comment:5 Changed 4 years ago by TheLastLovemark

forgot to mention that I just did a fresh install of 2.6.2 on Monday. so any version of qt5-qtdeclarative would be fresh also.

comment:6 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Perhaps the +debug variant is causing issues?
When you attempted to install wireshark3 with the debug variant, MacPorts passed the variant to the uninstalled dependencies (including qt5-qtdeclarative).
Perhaps you should try to install the indpedencies without the debug variant to see if that is the problem.

comment:7 Changed 4 years ago by mf2k (Frank Schima)

It installs fine for me with the +debug variant on Mojave:

$ port -v installed qt5-qtdeclarative
The following ports are currently installed:
  qt5-qtdeclarative @5.14.0_0 platform='darwin 18' archs='x86_64' date='2020-01-06T08:01:56-0700'
  qt5-qtdeclarative @5.14.0_0+debug (active) platform='darwin 18' archs='x86_64' date='2020-01-10T07:18:42-0700'
Last edited 4 years ago by mf2k (Frank Schima) (previous) (diff)

comment:8 Changed 4 years ago by TheLastLovemark

It worked for me without the +debug variant.

Installed Wireshark3 w/o debug variant.

This is not the only ticket I have open regarding a port failing to build with the debug variant.

Any idea why the install seems to work only without the +debug variant?

I'm on High Sierra and can not upgrade any further (Mid 2010 MBP).

Last edited 4 years ago by TheLastLovemark (previous) (diff)

comment:9 Changed 4 years ago by kencu (Ken)

probably all different reasons...

when you build with the +debug variant, you build everything from source always. This brings out any failings in your system, as in your clang-3.7 issue.

you build non-standard code paths, as in .your exiv2 issue, and maybe the issue here.

MacPorts has only so many people who can fix things, and so there are code paths like debug variants that don't get tested all that often, esp on systems that are not the most recent...

comment:10 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Since I cannot reproduce this error, and we at least have a workaround for the original reporter, I am inclined to close this as "works for me."
Any objections?

comment:11 Changed 4 years ago by TheLastLovemark

no. sorry for the long response time

comment:12 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: worksforme
Status: assignedclosed
Note: See TracTickets for help on using tickets.