Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#59174 closed defect (fixed)

kcachegrind4 fail to build

Reported by: tartarini (Daniele Tartarini) Owned by: Nicolas Pavillon <pavillon.nicolas@…>
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: mojave Cc: nicos@…
Port: kcachegrind4

Description

the port doesn't build, here the command line and attached the log file. running on OSX 10.14.6 and XCode 11.

 sudo port install kcachegrind4 -s
--->  Computing dependencies for kcachegrind4
--->  Fetching archive for kcachegrind4
--->  Attempting to fetch kcachegrind4-4.14.3_3.darwin_18.x86_64.tbz2 from https://packages.macports.org/kcachegrind4
--->  Attempting to fetch kcachegrind4-4.14.3_3.darwin_18.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/kcachegrind4
--->  Attempting to fetch kcachegrind4-4.14.3_3.darwin_18.x86_64.tbz2 from http://lil.fr.packages.macports.org/kcachegrind4
--->  Building kcachegrind4
Error: Failed to build kcachegrind4: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kcachegrind4/kcachegrind4/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port kcachegrind4 failed

any idea how to solve?

Attachments (1)

kcachegrind4.log.zip (32.6 KB) - added by tartarini (Daniele Tartarini) 5 years ago.

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by tartarini (Daniele Tartarini)

Attachment: kcachegrind4.log.zip added

comment:1 Changed 5 years ago by Nicolas Pavillon <pavillon.nicolas@…>

Owner: set to Nicolas Pavillon <pavillon.nicolas@…>
Resolution: fixed
Status: newclosed

In 5e6f578b0b8864c154da5b7cd9cc0e7c8045799b/macports-ports (master):

kcachegrind4: fix build with recent compilers (fixes #59174)

comment:2 Changed 5 years ago by NicosPavlov

Thanks for the report. The commit above should fix the problem.

comment:3 Changed 5 years ago by kencu (Ken)

you planning the same for qchachegrind?

comment:4 Changed 5 years ago by tartarini (Daniele Tartarini)

thanks for looking into it. The error disappears but kcachegrind4 is not installed anywhere. I cannot get moredebug information other than:

sudo port install kcachegrind4
--->  Computing dependencies for kcachegrind4
--->  Cleaning kcachegrind4
--->  Scanning binaries for linking errors
--->  No broken files found.                             
--->  No broken ports found

any idea why the binary is not staged anywhere?

comment:5 Changed 5 years ago by NicosPavlov

In principle (with standard installation paths), binaries are installed in /Applications/MacPorts/KDE4/. It is also possible to list files installed by a port with

port contents kcachegrind4

comment:6 Changed 5 years ago by tartarini (Daniele Tartarini)

thanks again. I tested the installed kcachegrind4.app on mojave and it doesn't start.

I believe it is missing the dependency kdesdk4. After installing it works.

Last issue is that it flickers making the interface not usable. I launched the application from command line after declaring the following environment variable

export RasterOff=true

it seems to work fine but I was wondering whether exist a cleaner way to solve.

comment:7 in reply to:  6 Changed 5 years ago by NicosPavlov

Replying to tartarini:

I believe it is missing the dependency kdesdk4. After installing it works.

I could not reproduce that issue. Kcachegrind seems to be working with only kdelibs4 installed.

Last issue is that it flickers making the interface not usable. I launched the application from command line after declaring the following environment variable

export RasterOff=true

it seems to work fine but I was wondering whether exist a cleaner way to solve.

There are notes in kdelibs4 about using qtconfig for addressing flickering issues, but this is somewhat similar to your approach. You can get them by running

port notes kdelibs4

If there are other issues, please either open a new ticket or get assistance on the mailing list, as these points have not much to do with the problem described in that ticket.

Note: See TracTickets for help on using tickets.