Bug 18039 - three small patches for pkg-config-0.23
Summary: three small patches for pkg-config-0.23
Status: RESOLVED FIXED
Alias: None
Product: pkg-config
Classification: Unclassified
Component: src (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Tollef Fog Heen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-13 02:18 UTC by Peter Breitenlohner
Modified: 2009-12-06 13:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
patch for pkg-config-0.23 (1 of 3: AC_MSG_RESULT) (1.31 KB, patch)
2008-10-13 02:18 UTC, Peter Breitenlohner
Details | Splinter Review
patch for pkg-config-0.23 (2 of 3: gcc-warning ) (621 bytes, patch)
2008-10-13 02:20 UTC, Peter Breitenlohner
Details | Splinter Review
patch for pkg-config-0.23 (3 of 3: manpage formatting) (748 bytes, patch)
2008-10-13 02:21 UTC, Peter Breitenlohner
Details | Splinter Review

Description Peter Breitenlohner 2008-10-13 02:18:43 UTC
Created attachment 19617 [details] [review]
patch for pkg-config-0.23 (1 of 3: AC_MSG_RESULT)

Attached are three small patches addressing:

pkg.m4: Ensure matching AC_MSG_CHECKING ... AC_MSG_RESULT pairs.

pkg.c: Avoid (the only two) gcc warnings.

pkg.1: Correct some manpage formatting glitches.

====================

What is the current situation about a pkg-config version to properly handle bi-arch systems?

Locally, we have a patch to do this, just for our situation (i686/x86_64-linux) and by far not general enough.
Comment 1 Peter Breitenlohner 2008-10-13 02:20:08 UTC
Created attachment 19618 [details] [review]
patch for pkg-config-0.23 (2 of 3: gcc-warning )
Comment 2 Peter Breitenlohner 2008-10-13 02:21:24 UTC
Created attachment 19619 [details] [review]
patch for pkg-config-0.23 (3 of 3: manpage formatting)
Comment 3 Tollef Fog Heen 2009-12-06 13:44:39 UTC
Thanks for your patches; those have all been incorporated one way or another.  (Some were duplicates of other bugs).


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.