Bug 98595 - Puts file in /usr/lib64 on i386
Puts file in /usr/lib64 on i386
Product: Red Hat Raw Hide
Classification: Retired
Component: pkgconfig (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
: Triaged
: 97384 (view as bug list)
Depends On:
Blocks: CambridgeBlocker
  Show dependency treegraph
Reported: 2003-07-04 08:09 EDT by Alexander Larsson
Modified: 2007-04-18 12:55 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-23 17:46:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Larsson 2003-07-04 08:09:23 EDT
On my i386 install containing gtk-doc-1.1-1 I have the file
/usr/lib64/pkgconfig/gtk-doc.pc. I guess this is because this is a noarch
package, and it happened to be built on a lib64 machine.

Its not immediately obvious what the right solution is here though.. moving it
ot /usr/lib will break x86-64.
Comment 1 Alexander Larsson 2003-07-04 08:14:24 EDT
Possible choices seem to be: 
* store the .pc in both lib and lib64
* don't make the package noarch
Comment 2 Owen Taylor 2003-07-04 10:05:21 EDT
Another possibility, that I'd be interested in hearing's hp's take on:

 - Make pkgconfig also search /usr/share/pkgconfig
 - Put the .pc file there
Comment 3 Havoc Pennington 2003-07-04 10:41:10 EDT
Seems reasonable, though I can imagine people using datadir when they shouldn't.
(Just because their .pc file happens to not look arch-specific at the moment,
rather than a plainly noarch package)

Would need to sort out how it relates to PKG_CONFIG_PATH
Comment 4 Miloslav Trmac 2003-07-04 13:33:23 EDT
*** Bug 97384 has been marked as a duplicate of this bug. ***
Comment 5 Alexander Larsson 2003-08-13 07:34:57 EDT
I think we need to solve this soon. Otherwise won't it start to create problems
when we build packages using the new gtk-doc.make stuff?
Comment 6 Owen Taylor 2003-08-28 16:42:27 EDT
I think the PKG_CONFIG_PATH relationship is simply that you have
to list both directories in PKG_CONFIG_PATH if you want both searched.
Maybe we could have something like


and have that automatically expand to:


Filed gtk-doc bug upstream as:


I can't file a pkg-config bug upstream since there is no bugzilla for it.

* Thu Aug 28 2003 Owen Taylor <otaylor@redhat.com> 1.1-3.0
- Move gtk-doc.pc file to %{_datadir}/pkgconfig (#98595)
- Require: /usr/bin/cmp (#88763, Thomas Vander Stichele)
- Added libxslt docbook-style-xsl to Require: and BuildPrereq
  (#99143, Ken MacFarlane)

I don't think this should affect our building much - very few things
require gtk-doc at build time. (Nothing should - everything should
be distributed with the built HTML docs, but there may be exceptions.)
Comment 7 Owen Taylor 2003-08-28 16:43:25 EDT
It should be noted that this applies both for RHL and RHEL, since 
1.1 is in both trees.
Comment 8 Dave Habben 2003-10-22 10:44:19 EDT
Verified as fixed in the latest release, suggesting that this be marked as

$ rpm -q gtk-doc

$ rpm -ql gtk-doc | grep gtk-doc.pc

$ rpm -q gtk-doc --changelog | head
* Thu Aug 28 2003 Owen Taylor <otaylor@redhat.com> 1.1-3.0

- Move gtk-doc.pc file to /usr/share/pkgconfig (#98595)
Comment 9 Owen Taylor 2003-10-22 11:44:01 EDT
No, this bug is very much not fixed; the gtk-doc part is there, but
the pkgconfig part is not; the file is in /usr/share/pkgconfig, but
won't be found.
Comment 10 Owen Taylor 2003-10-23 17:46:59 EDT
* Thu Oct 23 2003 Owen Taylor <otaylor@redhat.com> 1:0.14.0-6
- Make pkgconfig look in /usr/share/pkgconfig as well by default (#98595)

(Note that I *didn't* build this into the RHEL 3 updates tree, since
it's something of a semantic change, and I don't think compiling gtk-doc
using applications from source is going to be a big usage of RHEL 3.)
Comment 11 Alexander Larsson 2004-01-19 07:14:42 EST
I did this for gnome-icon-theme.pc too.

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