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

Compiler environment variables should be consistent #6610

Closed
sagetrac-ghtdak mannequin opened this issue Jul 24, 2009 · 2 comments
Closed

Compiler environment variables should be consistent #6610

sagetrac-ghtdak mannequin opened this issue Jul 24, 2009 · 2 comments

Comments

@sagetrac-ghtdak
Copy link
Mannequin

sagetrac-ghtdak mannequin commented Jul 24, 2009

Sage sets the environment variable LIBRARY_PATH which is a gcc variable. OTOH, it doesn't set CPATH or C_INCLUDE_PATH or CPLUS_INCLUDE_PATH. This causes inconsistencies, particularly since Sage replicates many Linux libraries potentially leading to version issues.

LD_LIBRARY_PATH is also set (appended / modified), as it would need to be, but that is for the loader (ld). Sometimes this leads to difficulties when running non-Sage installed executables which use replicated libraries. One example is Git which doesn't like Sage's zlib.

This latter problem is more difficult to address and rarely causes difficulty. In fact, the only manifestation I've seen is git although it seems obvious that there are potential problems lurking.

In my case, I replace the symlinks for libz.so* to reference the system libraries. This will work as long as major version's (interfaces) are consistent.

Component: build

Keywords: Environment

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/6610

@sagetrac-ghtdak sagetrac-ghtdak mannequin added c: build labels Jul 24, 2009
@jdemeyer
Copy link

This is essentially a duplicate of #10572.

@jdemeyer
Copy link

Reviewer: Jeroen Demeyer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants