libsilo misses silo_exports.h header

Bug #1810786 reported by SFriedemann
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
silo-llnl (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

after installing silo on ubuntu ...
Code:
sudo apt-get install libsilo-bin libsilo-dev

I get
Code:
/usr/include/silo.h:75:10: fatal error: silo_exports.h: No such file or directory
 #include <silo_exports.h>
           ^~~~~~~~~~~~~~~~
           compilation terminated.
when compiling parflow which depends on silo.

It does not find `silo_exports.h` ! Where can I find this header? is it a packaging problem?

Code:
/usr$ find . -name '*silo*'
./lib/x86_64-linux-gnu/pkgconfig/silo.pc
./lib/x86_64-linux-gnu/libsiloh5.so
./lib/x86_64-linux-gnu/libsiloh5.so.0.0.0
./lib/x86_64-linux-gnu/libsiloh5.so.0
./share/doc/libsiloh5-0
./share/doc/libsilo-dev
./share/doc/libsilo-bin
./include/silo.h
./include/silo.inc
./bin/silofile
./bin/silodiff
./bin/silock
does not help the file seems to not be installed on my system. (Or is there another path where I could search for it?)

My ubuntu version:
Code:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

I already posted on https://ubuntuforums.org/showthread.php?t=2408482 with no response...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in silo-llnl (Ubuntu):
status: New → Confirmed
Revision history for this message
Ian J. Bertolacci (ianbertolacci) wrote :

I was also using libsilo-dev under 16.04 and everything was fine.
Then I upgraded to 18.04 (and reinstalled libsilo) and my previously working builds using silo broke.

Maybe something between 16.04 and 18.04 is breaking this.
In the meantime, I've downloaded the SILO source from the LLNL website and built and installed it locally.

Revision history for this message
Ian J. Bertolacci (ianbertolacci) wrote :

Scratch that. I just found out that the build of SILO I was doing from source is somehow different from libsiloh5-0, but it includes the silo_exports.h so things things were silently breaking until I uninstalled libsiloh5-0

Revision history for this message
SFriedemann (s-friedemann) wrote :

So can somebody of the packagers help us? I want to have parflow running in a docker container and thus it would be cool to activate silo without recompiling libsilo in it.

Revision history for this message
Jon Cook (grwoef) wrote :

I see that this bug has been fixed in disco (19.04). Could we get the fix backported to bionic (18.04)? I'm willing to help if someone could point me in the correct direction. I know software and compiling, though I am not familiar with .deb packaging.

Revision history for this message
Jon Cook (grwoef) wrote :

The fix in Debian:

+ -- Gianfranco Costamagna <email address hidden> Wed, 12 Dec 2018 11:35:20 +0100
+
 silo-llnl (4.10.2.real-5) unstable; urgency=medium

   * Export missing header files (silo_exports.h, etc)

Revision history for this message
Glen Flint (glenflint) wrote :

How do I use this as a new software source? Software Sources rejects every attempt I've made to enter this under Additional Repositories.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.