Bug 218677 - x11-wm/libwraster fails to link
Summary: x11-wm/libwraster fails to link
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Tobias Kortkamp
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2017-04-15 15:55 UTC by rnmtw70
Modified: 2019-01-31 20:56 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (hrs)


Attachments
Patch to Makefile (372 bytes, patch)
2017-04-15 15:55 UTC, rnmtw70
no flags Details | Diff
Poudriere log from failed build (87.66 KB, text/plain)
2017-04-15 15:57 UTC, rnmtw70
no flags Details
Poudriere log from successful build (i.e. with proposed patch applied) (98.36 KB, text/plain)
2017-04-15 15:59 UTC, rnmtw70
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rnmtw70 2017-04-15 15:55:16 UTC
Created attachment 181811 [details]
Patch to Makefile

x11-wm/libwraster fails to link, with ld complaining that it cannot find -lomp. Attached is a patch that seems to resolve this, by adding compiler:openmp to the USES variable.
Comment 1 rnmtw70 2017-04-15 15:57:55 UTC
Created attachment 181812 [details]
Poudriere log from failed build
Comment 2 rnmtw70 2017-04-15 15:59:15 UTC
Created attachment 181813 [details]
Poudriere log from successful build (i.e. with proposed patch applied)
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-01-31 19:56:38 UTC
Maintainer timeout?
Comment 4 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-12 08:57:58 UTC
I do not think that this is a problem with libwraster per se.

What I think is going on is that graphics/ImageMagick was compiled with
OPENMP=on (a deviation from the default options) and the libwraster
build is picking up "-fopenmp" from ImageMagick's pkg-config file or
from somewhere else.

I think that adding USES=compiler:openmp to libwraster is the wrong
solution here.