Bug 1583431

Summary: link fails using libgerbv from a C++ program, undefined reference to 'screen'
Product: [Fedora] Fedora Reporter: Eric Smith <spacewar>
Component: gerbvAssignee: Alain V. <alain.vigne.14>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alain.vigne.14, kiarakovalevsky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:00:39 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
trivial example source file
none
Makefile for example
none
bug fix patch dd8f9fa from gerbv repo
none
RPM spec patch to apply code patch none

Description Eric Smith 2018-05-29 00:10:42 UTC
Created attachment 1444984 [details]
trivial example source file

Description of problem:
Use of libgerbv from a C++ program fails to link, complaining of an undefined reference to 'screen'

Version-Release number of selected component (if applicable):
2.6.2-1

How reproducible:
100%

Steps to Reproduce:
1. Attempt to compile a trival program using libgerbv (see attachments)

Actual results:
/usr/lib/gcc/x86_64-redhat-linux/7/../../../../lib64/libgerbv.so: undefined reference to `screen'
collect2: error: ld returned 1 exit status
make: *** [<builtin>: main] Error 1


Expected results:
successful link


Additional info:
Web search reveals reports of this happening with 2.6.1, but claimed to have been fixed in 2.6.2. Debian says they cherry-picked a commit from 2013 to fix it, which seems somewhat dubious to me.

Comment 1 Eric Smith 2018-05-29 00:11:11 UTC
Created attachment 1444985 [details]
Makefile for example

Comment 2 Eric Smith 2018-05-30 17:33:52 UTC
Created attachment 1445965 [details]
bug fix patch dd8f9fa from gerbv repo

Comment 3 Eric Smith 2018-05-30 17:34:33 UTC
Created attachment 1445966 [details]
RPM spec patch to apply code patch

Comment 4 Eric Smith 2018-05-30 17:35:51 UTC
I've confirmed that the gerbv patch Debian cherry-picked, dd8f9fa, solves the problem. I've attached that patch, along with a trivial patch to the RPM spec which applies it.

Comment 5 Alain V. 2018-10-24 09:56:47 UTC
Hello Eric
I think this problem is still bugging you ?
I will try to move it forward...

Comment 6 Eric Smith 2018-10-24 22:54:20 UTC
Hi Alain,
That would be great!
Let me know if I can be of any assistance.

Comment 7 Ben Cotton 2019-05-02 20:34:53 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2019-05-28 23:00:39 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.