# DCMQI extension: New linking error

**URL:** <https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966>\
**Category:** Development\
**Tags:** extensions-manager, bug\
**Created:** [August 29, 2017, 3:18pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966 "2017-08-29T15:18:53Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 29, 2017, 3:18pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/1 "2017-08-29T15:18:53Z")

</div>

It looks like some of the commits done yesterday introduced a new linking error for one of our extensions:

/usr/bin/ld: cannot find -lITKFactoryRegistration

[http://slicer.cdash.org/viewBuildError.php?buildid=1087743](http://slicer.cdash.org/viewBuildError.php?buildid=1087743)

@jcfr we really need to finalize the set of binaries for the MICCAI tutorial on Sept 10, so this is quite urgent for us. Would it be possible to wait for a day or so until we have Slicer binaries for 3 platforms and all extensions we need, before moving on with all the VTK/Qt5 related upgrades?

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 29, 2017, 3:20pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/2 "2017-08-29T15:20:53Z")

</div>

Nightly was fixed last night in [r26314](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26314)

Regarding, error reported [here](http://slicer.cdash.org/viewBuildError.php?buildid=1087743). I have been working on fixing the extensions, I will have a look at this one.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 29, 2017, 3:23pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/3 "2017-08-29T15:23:16Z")

</div>

Thank you. It’s something new, I don’t recall seeing it before.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 29, 2017, 10:10pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/4 "2017-08-29T22:10:27Z")

</div>

Hi @fedorov,

I suspect the link error is due to the Slicer core build error that already been fixed.

Otherwise, here are three PRs fixing various issues with the DCMQI extensions.

> <https://github.com/QIICR/dcmqi/pull/298>

> <https://github.com/QIICR/dcmqi/pull/299>

> <https://github.com/QIICR/dcmqi/pull/300>

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 30, 2017, 1:15am UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/5 "2017-08-30T01:15:03Z")

</div>

Thank you @jcfr! Fingers crossed for the dashboard tomorrow!

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 30, 2017, 11:34am UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/6 "2017-08-30T11:34:05Z")

</div>

@fedorov, look like DCMQI was successfully build and packages on windows and linux. See [http://slicer.cdash.org/index.php?project=Slicer4&date=2017-08-30&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=DCMQI](http://slicer.cdash.org/index.php?project=Slicer4&date=2017-08-30&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=DCMQI)

Still waiting on macOS

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 30, 2017, 7:55pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/7 "2017-08-30T19:55:01Z")

</div>

Thanks, I am checking it all now.

Unfortunately, there was a new error in Slicer core, so I again have to wait for the next nightly … For now I will replace the affected file manually, and see if everything else is working as expected - I see @lassoan commit that mentions a problem in DataProbe.

```auto
Traceback (most recent call last):
  File "C:\Program Files\Slicer 4.7.0-2017-08-29\lib\Slicer-4.7\qt-scripted-modules\DataProbeLib\SliceViewAnnotations.py", line 432, in updateViewAnnotations
    self.makeAnnotationText(caller)
  File "C:\Program Files\Slicer 4.7.0-2017-08-29\lib\Slicer-4.7\qt-scripted-modules\DataProbeLib\SliceViewAnnotations.py", line 610, in makeAnnotationText
    self.makeDicomAnnotation(uid,None,sliceViewName)
  File "C:\Program Files\Slicer 4.7.0-2017-08-29\lib\Slicer-4.7\qt-scripted-modules\DataProbeLib\SliceViewAnnotations.py", line 715, in makeDicomAnnotation
    dicomDic = self.extractDICOMValues(uid)
  File "C:\Program Files\Slicer 4.7.0-2017-08-29\lib\Slicer-4.7\qt-scripted-modules\DataProbeLib\SliceViewAnnotations.py", line 856, in extractDICOMValues
    self.extractedDICOMValuesCache.pop_item(last=False)
AttributeError: 'OrderedDict' object has no attribute 'pop_item'

```

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 30, 2017, 8:08pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/8 "2017-08-30T20:08:18Z")

</div>

Yes, I’ve committed a fix for this error already. Tomorrow’s nightly build should not have this error.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 30, 2017, 10:16pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/9 "2017-08-30T22:16:44Z")

</div>

The current error doesn’t see to affect the functionality of the relevant part of the workflow that we need for the tutorial, so I might just use the today’s set of items, to make things easier.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 30, 2017, 11:18pm UTC](https://discourse.slicer.org/t/dcmqi-extension-new-linking-error/966/10 "2017-08-30T23:18:25Z")

</div>

I think the only effect of the error is that slice view annotations (patient name, etc. in the corner of slice views) are not displayed.