Bug 2122790 - Invalid libdir in mt32emu pkgconfig
Summary: Invalid libdir in mt32emu pkgconfig
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mt32emu
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Otto Liljalaakso
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-30 19:33 UTC by Otto Liljalaakso
Modified: 2023-08-16 07:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Otto Liljalaakso 2022-08-30 19:33:18 UTC
Description of problem:
The libdir field in mt32emu's pkgconfig is invalid.

Version-Release number of selected component (if applicable):
2.7.0-1.fc36, and all other versions

How reproducible:
Always

Steps to Reproduce:

$ cat /usr/lib64/pkgconfig/mt32emu.pc  | head -n 3
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}//usr/lib64
$ LANG=C.UTF-8 ls /usr//usr/lib64
ls: cannot access '/usr//usr/lib64': No such file or directory

Additional info:

This happens because Fedora cmake macros set LIB_INSTALL_DIR to absolute path /usr/lib64,
and mt32emu pkgconfig template just appends that to '${exec_prefix}/'

Comment 1 Ben Cotton 2023-04-25 17:51:25 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Otto Liljalaakso 2023-04-26 04:55:42 UTC
Still happens in every version.
I change the version to 'rawhide'.

Comment 3 Fedora Release Engineering 2023-08-16 07:05:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


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