Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
N
nx-libs
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
dimbor
nx-libs
Commits
94fcba36
Commit
94fcba36
authored
Feb 28, 2019
by
Ulrich Sibiller
Committed by
Mike Gabriel
Oct 17, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
libNX_X11: set FAIL_HARD
as it has been in the imake builds Fixes ArcticaProject/nx-libs#783
parent
b4124219
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
0 deletions
+13
-0
configure.ac
nx-X11/lib/configure.ac
+13
-0
No files found.
nx-X11/lib/configure.ac
View file @
94fcba36
...
...
@@ -67,9 +67,22 @@ m4_pattern_forbid([^NX_XTRANS_CONNECTION_FLAGS$])
# Transport selection macro from nx-xtrans.m4
NX_XTRANS_CONNECTION_FLAGS
# Secure RPC detection macro from xtrans.m4
NX_XTRANS_SECURE_RPC_FLAGS
# Original comments regarding FAIL_HARD from libxtrans:
# "fail hard if socket directories cannot be chowned to root or
# chmod'ed to the requested mode if 'sticky' bit is requested for this
# directory instead of just print a warning that will remain unnoticed
# most of the times.
# Set the define XtransFailSoft to restore the old
# behavior to fail softly when socket directory cannot chowned/chmod
# to correct user/group."
#
# -> we want to always fail in that scenario.
AC_DEFINE(FAIL_HARD,1,[Fail if the xtrans socket directory has wrong permissions])
# Check for dlopen
AC_MSG_CHECKING([if run-time linking is supported])
AC_SEARCH_LIBS(dlopen,[dl svld])
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment