Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix FTBFS on non-ELF platforms. #663

Merged
merged 3 commits into from Feb 25, 2018

Conversation

Ionic
Copy link
Member

@Ionic Ionic commented Feb 25, 2018

Check if target system is ELF-based and only add flag that enables new ELF dtags on ELF-based target systems.

Fixes: #661

@Ionic Ionic added the bug label Feb 25, 2018
@Ionic Ionic requested a review from sunweaver February 25, 2018 03:40
Copy link
Member

@sunweaver sunweaver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Thanks for working on this.

@sunweaver sunweaver merged commit 06c14b8 into ArcticaProject:3.6.x Feb 25, 2018
sunweaver added a commit that referenced this pull request Feb 25, 2018
uli42 added a commit to uli42/nx-libs that referenced this pull request Dec 11, 2019
Fixes ArcticaProject#663

The previous logic was completely broken as it depended on the order
of atoms being created on the real X server. This might have been
working in the beginning of NX but eventually atom mapping between
nxagent and the real X server was introduced which broke the whole
logic. As a rather ugly fix let's not create the NX_IDENTITY and
NX_AGENT_SIGNATURE atoms to the real X server. If we find them
nevertheless on the remote side we are running nested.

This change is neither nice nor efficient, just functional. It should
be redesigned one day.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants