Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13373

Closed (moved)
Open
Opened Oct 09, 2014 by Georg Koppen@gk

Get rid of LD_LIBRARY_PATH and use a relative RPATH/RUNPATH in Linux bundles

Relying on LD_LIBRARY_PATH in our start script can cause all sorts of pain (see #13359 (moved) for an example). We should take the cleaner approach to compile the binaries that need it with a relative RPATH/RUNPATH and get rid of LD_LIBRARY_PATH. We need to adapt our tests as well to make the pass if a RPATH/RUNPATH with ${ORIGIN} is showing up.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13373