Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #6936
Closed
Open
Issue created Sep 22, 2012 by weasel (Peter Palfrader)@weasel

link to librt and libdl only when needed

According to dpkg-shlibdeps, the three binaries in tor, tor-resolve, tor-gencert, and tor, link to libdl.so.2 and librt.so.1. without using any of their symbols.

dpkg-shlibdeps: warning: dependency on libdl.so.2 could be avoided if "debian/tor/usr/bin/tor-resolve debian/tor/usr/sbin/tor debian/tor/usr/bin/tor-gencert" were not uselessly linked against it (they use none of its symbols).
dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if "debian/tor/usr/bin/tor-resolve debian/tor/usr/sbin/tor debian/tor/usr/bin/tor-gencert" were not uselessly linked against it (they use none of its symbols).

Why do we link against them? Should we?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking