Cabal build does not actually use the library search paths that Autoconf has found #53
Comments
|
Can you find out what openbsd calls the X screensaver extension client library? The includes for it appear tp be present, from the build output. |
|
And it's a good question why configure only tests for the headers and not the associated libraries... we inherited this beast and it has a number of flaws, some of which we're already trying to fix. cc @pjones |
|
Here is the X screensaver extension client library code for OpenBSD, via web cvs:
On a running OpenBSD 6.1-stable-amd64 system, I find does that help, or do you need something else? |
|
It found scrnsaver.h, that's why it was trying to use the extension. What
it couldn't find was -lXss (aka libXss.a or libXss.so), the library
corresponding to the header.
|
|
Got it. Those are in /usr/X11R6/lib |
|
Sorry for delay, I am mostly offline at the moment.
I think all you need is --extra-lib-dirs=/usr/X11R6/lib to get it to link.
…--
brandon s allbery kf8nh sine nomine associates
[email protected] [email protected]
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
|
|
Thanks! That seems to have worked. Now its in PR form: #54 |
|
The issue still exists on OpenBSD 6.5. The workaround of supplying Why is Also, here, X_LIBS in Full log: Notice the linker line starting with |
blackgnezdo
added a commit
to blackgnezdo/ports
that referenced
this issue
Aug 31, 2019
blackgnezdo
added a commit
to blackgnezdo/ports
that referenced
this issue
Sep 1, 2019
|
This is not a bug in |
|
To be completely clear, is the value determined by I've added a flag to OpenBSD ports. It's just whoever aspires to use |
Oh, sorry, I misunderstood that part of the ticket. No, that is not supposed to be happening. |
peti
changed the title
peti
added a commit
that referenced
this issue
Aug 25, 2020
Pass X libraries as extra-lib-dirs to fix #53
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
EDIT: Autoconf successfully determines the necessary
-Lsearch paths, but Cabal does not actually use them. See #53 (comment) for details.error:
full log below
Using Stackage LTS 6.35 which points at X11 v1.6.1.2 everything works just fine and X11 successfully compiles. Using the newer Stackage LTS 9.0 which points at X11 v1.8, I get the above error and cannot complete the compile.
The text was updated successfully, but these errors were encountered: