Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: PICCA Frederic-Emmanuel Newsgroups: linux.debian.maint.python Subject: RE:trying to solve the pytango FTBFS with gcc5 Date: Sun, 06 Sep 2015 18:40:01 +0200 Message-ID: References: X-Original-To: Dmitry Shachnev , "debian-python@lists.debian.org" X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Sep 6 16:30:10 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-0.699 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=0.001, THREADTOPIC=2] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Thread-Topic: trying to solve the pytango FTBFS with gcc5 Thread-Index: AdDofVQ/A0v0lRKxQVKW4aerapVG+QAIZk0AAABnHQAAAdR+AAAFweLI Accept-Language: fr-FR, en-US Content-Language: fr-FR X-Originating-IP: [195.221.0.171] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailing-List: archive/latest/12559 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/A2A20EC3B8560D408356CAC2FC148E53B2F8077C@SUN-DAG3.synchrotron-soleil.fr Approved: robomod@news.nic.it Lines: 19 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 6 Sep 2015 16:14:50 +0000 X-Original-Message-ID: X-Original-References: <1921765.67YpD7VbQY@kitterma-e6430> <55EC4F3C.6000004@debian.org>,<144155328471.2505.17612112195669382799@mitya57.me> <144155328471.2505.17612112195669382799@mitya57.me> Xref: csiph.com linux.debian.maint.python:7253 > The actual error is about another symbol: > _PyTango.so: undefined symbol: _ZN5Tango17ranges_type2constIjE3strE > This symbol is old ABI, as opposed to _ZN5Tango17ranges_type2constIjE3str= B5cxx11E > (which *does* exist in libtango.so.8). > Can it be a bug in GCC? I don't think it should produce such a broken _Py= Tango.so. Yes I have this feeling also. I do not understand why gcc produce something= with the old ABI. Except thaht python build extensions with gcc and not g++. Maybe this is the problem. gcc and g++ do not behave the same when compiling c++ files ? Fred=