Hi Lisandro !
On Wed, May 27, 2015 at 6:27 PM, Lisandro Damián Nicanor Pérez
<perezme...@gmail.com> wrote:
> tag 786969 moreinfo
> thanks
>
> Hi Mathieu!
>
> Can you check the version of dpkg used in the build process?
>
> It might be related to that.
I have the *exact* same output using a jessie or a sid chroot. So in my case:
jessie:
$ apt-cache policy dpkg
dpkg:
Installed: 1.17.25
Candidate: 1.17.25
Version table:
*** 1.17.25 0
700 http://ftp.fr.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
sid:
$ apt-cache policy dpkg
dpkg:
Installed: 1.18.0
Candidate: 1.18.0
Version table:
*** 1.18.0 0
500 http://ftp.fr.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
IMHO, I suspect the issue lie instead in the merging of symbols
(remember that the first dpkg-gensymbols generated file is ok), so I
suspect:
[...]
pkgkde-symbolshelper: info: ambiguous symbols for subst detection
(_ZNSt6vectorImSaImEE14_M_dlll_lnsertEN9__gnu_cll17__normal_lteratorIPmS1_EEmRKm@Base/libIlmImf.so.6).
[...]
indicate an error instead of just an information. It is hard to give
more details as `pkgkde-symbolshelper` does not seems to be documented
(no man page AFAIK)
Comments ?
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/ca+7wuszptffwwenbsfhs75smzqftujxjeoutb2q9c9+f8df...@mail.gmail.com
