Bug 954351 - mingw32-configure unsets PKG_CONFIG_PATH
Summary: mingw32-configure unsets PKG_CONFIG_PATH
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-filesystem
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Erik van Pienbroek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-22 11:03 UTC by Jonathan Dieter
Modified: 2014-02-05 23:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:08:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonathan Dieter 2013-04-22 11:03:45 UTC
Description of problem:
I am trying to cross-compile a program for Windows, and it needs a library that I've already cross-compiled.  I set PKG_CONFIG_PATH to point to the directory that contains the .pc file for that library, but mingw32-configure unsets PKG_CONFIG_PATH and I can't compile my program

Version-Release number of selected component (if applicable):
mingw32-filesystem-97-1.fc18.noarch

Additional info:
This can be easily fixed by removing the following line from /etc/rpm/macros.mingw32
unset PKG_CONFIG_PATH; \

I've verified that if PKG_CONFIG_PATH isn't set, then mingw32-configure shows it as empty, but if it is configured, my program compiles correctly, using both public mingw libraries and my private library.

Comment 1 Jonathan Dieter 2013-04-22 11:04:42 UTC
I've just noticed that, at least according to the rpm changelog, this was already supposedly done back in 2011.  Not sure how it got back in there.

Comment 2 Erik van Pienbroek 2013-04-22 12:02:23 UTC
The unset is really required here. When building RPMs the PKG_CONFIG_PATH environment variable gets set by rpm automatically so that it points to %{_libdir}/pkgconfig. As we don't want to use any native libraries when cross-compiling this environment variable has to be unset first before running mingw32-configure (or %mingw32_configure in RPM terms)

Comment 3 Fedora End Of Life 2013-12-21 15:29:20 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 4 Fedora End Of Life 2014-02-05 23:08:22 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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