Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1753475

Summary: RFE: Update swig for octave 5.1 compatibility
Product: Red Hat Enterprise Linux 8 Reporter: Orion Poplawski <orion>
Component: swigAssignee: Jitka Plesnikova <jplesnik>
Status: CLOSED DUPLICATE QA Contact: RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.0Keywords: FutureFeature, Patch, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-14 09:02:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Support for Octave 4.4
none
Support for Octave 5.1
none
Adapt OCTAVE_LDFLAGS for Octave 5.1 none

Description Orion Poplawski 2019-09-19 03:49:22 UTC
Description of problem:

octave bindings with 5.1 fail to build with errors like:

BUILDSTDERR: /builddir/build/BUILD/plplot-5.14.0/fedora/bindings/octave/plplot_octaveOCTAVE_wrap.cxx: In function 'void SWIG_Octave_LinkGlobalValue(std::__cxx11::string)':
BUILDSTDERR: /builddir/build/BUILD/plplot-5.14.0/fedora/bindings/octave/plplot_octaveOCTAVE_wrap.cxx:2274:3: error: 'symbol_table' has not been declared
BUILDSTDERR:    symbol_table::mark_global(name);
BUILDSTDERR:    ^~~~~~~~~~~~

Upstream swig has support for 5.1 now.  I'm not sure what the best course here will be.  Will there be a swig 4 module stream soon?  Are the octave support patches easily back-ported?  What about a swig4 package in EPEL?

Version-Release number of selected component (if applicable):
swig-3.0.12-18.module+el8+2480+72897362.x86_64

Comment 1 Jitka Plesnikova 2019-10-01 11:30:36 UTC
Created attachment 1621374 [details]
Support for Octave 4.4

Comment 2 Jitka Plesnikova 2019-10-01 11:31:11 UTC
Created attachment 1621375 [details]
Support for Octave 5.1

Comment 3 Jitka Plesnikova 2019-10-01 11:31:55 UTC
Created attachment 1621376 [details]
Adapt OCTAVE_LDFLAGS for Octave 5.1

Comment 4 Jitka Plesnikova 2019-10-01 11:35:29 UTC
It will be easier to backport the octave patches than create stream for SWIG 4.0.

I attached all necessary patches.

Comment 5 Jitka Plesnikova 2019-10-01 11:39:34 UTC
Octave is not supported by RHEL and I don't have any experience with it. 

Could you please provide me any small example how to test that it works properly after the fix?

Comment 6 Orion Poplawski 2019-10-01 12:57:22 UTC
Easiest would be to simply rebuild the current octave package from Fedora master.

Comment 7 Jitka Plesnikova 2019-10-03 13:44:35 UTC
Thank you for the report. 

Please contact Red Hat support that helps you escalate this issue.

Comment 9 Jitka Plesnikova 2020-09-14 09:02:50 UTC
The support of new octave will be added by module swig:4.0.

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