SuiteSparse fails to link in shared library due to missing -fPIC in libsuitesparseconfig.a

[Arne Morten Kvarving]

The config library is only available as a .a which is not compiled with -fPIC. Thus, linking into shared libraries fails on AMD64.

Attaching a minimal program to trigger the bug.

gcc -shared -fPIC -o test.so suitetest.cpp -lumfpack -lsuitesparseconfig

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Budo Zindovic (bzindovic)]

I've added a fix to official libraries and packaged it in my ppa. To install libraries with a fix of this bug, do the following:

1. sudo add-apt-repository ppa:bzindovic/suitesparse-bugfix-1319687
2. sudo apt-get update
3. sudo apt-get upgrade

I hope it will be resolved in the official package.

[Arne Morten Kvarving (arne-morten-kvarving)]

doh, missed your response. thanks a lot!

[Philipp Huebner (debalance-debian)]

Hi Budo,
I don't think your approach is the right one, working against the package maintainer's intent to provide both types of libraries, one with -fPIC and one without.
Check out my update to Debian bug #684116: the package already builds a libsuitesparseconfig_pic.a and simply misses to include it in the binary .deb file. I noticed when going through the patches that were already in the package before yours.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "include libsuitesparseconfig_pic.a in libsuitesparse-dev" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Sebastien Bacher (seb128)]

Thanks bug reading bugs.debian.org/cgi-bin/bugreport.cgi?bug=684116 it seems the Debian maintainer disagrees with the change, unsubscribing sponsors until that's resolved, no need to have the discussion in 2 different bug trackers

[Pedro (pedro-cavestany)]

Hi, this bug has been around for near 2 years now, when will it be fixed in Ubuntu?
thanks