octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44430] dicom package does not seem to recogni


From: anonymous
Subject: [Octave-bug-tracker] [bug #44430] dicom package does not seem to recognize gdcm package
Date: Thu, 05 Mar 2015 10:25:56 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?44430>

                 Summary: dicom package does not seem to recognize gdcm
package
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Thu 05 Mar 2015 10:25:55 AM UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Installation Failure
                  Status: None
             Assigned to: None
         Originator Name: leo
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.2
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Im am trying to install the dicom package for octave in a Jessie distribution.
I have installed all gdcm packages and their folder is called something like
libgdcm4. I get this error when installing the dicom package:


fatal error: gdcm-2.0/gdcmReader.h: No such file


First I thought maybe the dicom package is only compatible with an older gdcm
version so I installed previous gdcm versions but I keep getting the same
error. I think the path the dicom package is trying to use is hardcoded in
there which causes the dicom package to not be able to be installed anymore. 

Im not very Linux savvy so some of my interpretations may be off and there
might be a simple solution to this. But I do have some programming/scripting
experience and Im pretty sure the predefined path is the problem here. 

I also saw on the forge that the latest version was from 2011 so maybe no one
is maintaining this package anymore and I should not try to use it?




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44430>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]