RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

swig rpm carries an unneeded patch which breaks some swig uses with other sources.

This patch was added to fix a swig 2.0.7 issue but is not needed anymore from swig 2.0.8.
See author comment here:
https://github.com/swig/swig/issues/515

Noticed the issue while trying to build nfqueue bindings for perl and python (https://github.com/chifflier/nfqueue-bindings)
which results in incorrectly appended prefixes to some functions names  that leads to undefined symbols on
built module usage.

Using the same vanilla version of swig works correctly.

Investigation led to swig207-setools.patch as the culprit.

Version-Release number of selected component (if applicable):
swig-2.0.10-4.el7

How reproducible:
Always

Steps to Reproduce:
1. Get nfqueue-bindings sources ( https://github.com/chifflier/nfqueue-bindings )
2. build and try to load in a python application

Actual results:
unresolved symbols on swig generated module


Expected results:
swig module works ok


Additional info:
According to author, the patch is not needed anymore, so can be dropped (also from Fedora)

The removing unnecessary patch solves the bug.

Tests steps:
1) Install cmake, gcc, gcc-c++, python-devel, swig
2) Get nfqueue-bindings sources ( https://github.com/chifflier/nfqueue-bindings )
3) Build and try to load in a python application. I used simple test script

$ cat ./test.py 
#!/usr/bin/python

import sys

sys.path.append('python')
sys.path.append('build/python')
import nfqueue

Output is empty.

Previously it failed with following error:

Traceback (most recent call last):
  File "./test.py", line 7, in <module>
    import nfqueue
  File "build/python/nfqueue.py", line 26, in <module>
    _nfqueue = swig_import_helper()
  File "build/python/nfqueue.py", line 22, in swig_import_helper
    _mod = imp.load_module('_nfqueue', fp, pathname, description)
ImportError: build/python/_nfqueue.so: undefined symbol: struct_queue_process_pending

Reproduced with swig-2.0.10-4.el7, verified with swig-2.0.10-5.el7.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2227.html