Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #443
Closed
Open
Created May 16, 2016 by RingBot@RingBotOwner

daemon: cannot compile shared object on GNU/linux

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

Compiling the daemon on GNU/linux system does not generate a .so as it should by default, nor when the configure option "--enable-shared" is given explicitly. This seems to be due to some sort of architecture/gcc compatibility check during configure, as can be found in the config.log file:

 

  
configure:11517: checking whether the gcc linker (/usr/bin/ld -m elf\_x86\_64) supports shared libraries  
configure:12674: result: no  

 

The .so is needed in order to be able to compile Ring into a single process instead of running the daemon and client seperately.

This seems to be a long standing bug... a possible "solution" in order to force .so compilation is to manually edit the generate "configure" script in the right place in order to skip the failed check.

Assignee
Assign to
Time tracking