Bug 1544527 - Using net-snmp-config --external-libs cause link failure if redhat-rpm-config not installed
Summary: Using net-snmp-config --external-libs cause link failure if redhat-rpm-config...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: net-snmp
Version: 33
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Josef Ridky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-12 18:18 UTC by Quentin Armitage
Modified: 2021-08-15 01:32 UTC (History)
5 users (show)

Fixed In Version: net-snmp-5.9.1-4.fc34 net-snmp-5.9.1-4.fc33
Clone Of:
Environment:
Last Closed: 2021-08-15 01:09:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1543394 0 unspecified CLOSED redhat-rpm-config: Provide macros for extension builders 2021-02-22 00:41:40 UTC

Internal Links: 1543394

Description Quentin Armitage 2018-02-12 18:18:00 UTC
Description of problem:
net-snmp-config --external-libs outputs:

-Wl,-z,relro -Wl,-z,now -lssl -lssl -lcrypto -lm -Wl,--enable-new-dtags -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld 

which causes a link failure if /usr/lib/rpm/redhat/redhat-hardened-ld is not installed

Version-Release number of selected component (if applicable):
5.7.3-31

How reproducible:
Always

Steps to Reproduce:
1. Link using the output of `net-snmp-config --external-libs`
2.
3.

Actual results:
link fails

Expected results:
link succeeds

Additional info:
This issue looks very similar to the end of the patch net-snmp-5.7.3-cflags.patch

commit 127274f8f27fba264a4c0f91190fd6f8037cdf21

Author: Jan Safranek <jsafranek.net>

Date:   Wed Feb 24 10:14:21 2016 +0100

    Trim output of net-snmp-config --cflags.

    

    We should report CFLAGS needed to import and use Net-SNMP headers, not

    CFLAGS used to compile actual Net-SNMP.

    

    E.g. we should not report various distro fortify-source options.

Comment 1 Fedora End Of Life 2018-02-20 15:23:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Petr Pisar 2018-02-22 13:26:52 UTC
You probably want to see bug #1543394. This is an initiative to define two sets compiler/linker flags to not enforce distribution enhancements to users.

Comment 3 Quentin Armitage 2018-05-07 09:20:54 UTC
The upstream patch included at the end of net-snmp-5.7.3-cflags.patch has been reverted upstream:

commit 74ffd19da3e4831f7d713d70125d760a71026a91
Author: Bart Van Assche <bvanassche>
Date:   Sat Mar 5 15:38:17 2016 -0800

    Revert "Trim output of net-snmp-config --cflags."
    
    This reverts commit 127274f8f27fba264a4c0f91190fd6f8037cdf21. Robert Story
    explained as follows on the net-snmp-cvs mailing list why this patch is
    wrong and needs to be reverted:
    <quote>
    Actually, I --cflags is supposed to be everything used to compile
    the agent, so that subagents and modules for dlmod loading can be
    built exactly the same.
    
    In particular, removing other flags can remove options that will
    change structure sizes when parsing the headers, resulting in
    binary incompatibilities.
    
    If you only need the include directories for some reason, please
    add another option.
    </quote>

Would it be possible to do as has been done for perl re bug #1557667 and for now add a dependency on redhat-rpm-config to net-snmp-devel. It seems that it can be reverted once bug #1543394 has been implemented.

Comment 4 Ben Cotton 2019-05-02 21:50:09 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 5 Quentin Armitage 2019-05-13 07:28:13 UTC
The problem still exists in F30.

Comment 6 Ben Cotton 2020-04-30 22:01:31 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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 7 Ben Cotton 2020-05-26 15:15:06 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.

Comment 8 Vincent Bernat 2020-11-23 11:05:41 UTC
Hello,

Problem still exists in Fedora 33. Maybe the fix would be to ensure netsnmp-devel depends on the appropriate package.

Comment 9 Fedora Update System 2021-07-30 12:06:38 UTC
FEDORA-2021-542c9d0570 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-542c9d0570

Comment 10 Fedora Update System 2021-07-30 12:06:41 UTC
FEDORA-2021-72e9c8074e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-72e9c8074e

Comment 11 Fedora Update System 2021-08-15 01:09:56 UTC
FEDORA-2021-542c9d0570 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2021-08-15 01:32:36 UTC
FEDORA-2021-72e9c8074e has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


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