81076 – vte-0.11.11 python interface error initializing

Bug 81076 - vte-0.11.11 python interface error initializing

Summary: vte-0.11.11 python interface error initializing

Status:	RESOLVED DUPLICATE of bug 81006

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Library (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-02-06 23:52 UTC by Brian Dolbec
Modified:	2005-07-17 13:06 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Brian Dolbec (RETIRED) gentoo-dev

2005-02-06 23:52:10 UTC

There is an error in the code for the python interface for all revisions of -0.11.11.



Reproducible: Always
Steps to Reproduce:
1.emerge /x11-libs/vte-0.11.11-r*
2.from a python shell or script: import vte
3.

Actual Results:  
IDLE 1.0.3      
>>> import vte

Traceback (most recent call last):
  File "<pyshell#0>", line 1, in -toplevel-
    import vte
ImportError: dynamic module does not define init function (initvte)
>>> 


I have found a change in the /python Makefile.in line 213:
@BUILD_PYTHON_MODULES_TRUE@vtemodule_la_LDFLAGS = -module -avoid-version
-export-symbols-regex=initvte


In vte-0.11.10 that line is:

@BUILD_PYTHON_MODULES_TRUE@vtemodule_la_LDFLAGS = -module -avoid-version
-export-symbols-regex initvte

It state that that file is auto generated from Makefile.am but I do not see any
 difference in it that would cause that change.

Comment 1 Brian Dolbec (RETIRED) gentoo-dev

2005-02-07 00:09:11 UTC

It looks like my search for this bug did not reveal bug #61683.  I am emerging -r3 and hopefully find that it is fixed.   I'll report back and/or close this bug if it is fixed.

Comment 2 Brian Dolbec (RETIRED) gentoo-dev

2005-02-07 00:13:19 UTC

I don't know what happened, but this bug somehow was duplicated from bug#81006.

Please close this one as a duplicate.

*** This bug has been marked as a duplicate of 81006 ***