Bug 2803 - build on amd64 and ppc64 uses /usr/X11R6/lib not /usr/X11R6/lib64
Summary: build on amd64 and ppc64 uses /usr/X11R6/lib not /usr/X11R6/lib64
Alias: None
Product: xprint
Classification: Unclassified
Component: Build config (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Roland Mainz
QA Contact:
URL: http://bugs.debian.org/cgi-bin/bugrep...
Depends on:
Reported: 2005-03-24 21:42 UTC by Drew Parsons
Modified: 2011-09-13 15:48 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Drew Parsons 2005-03-24 21:42:13 UTC
A debian porter for amd64 reports (Debian bug #301028):
- amd64 and ppc64 use -L/usr/X11R6/lib not -L/usr/X11R6/lib64
- there's an ExecCommand still remaining which needs to go.

He mentions failure with gcc4, but the patch he provides does not seem specific
to gcc4, unless it's the ExecCommand.

Comment 1 Drew Parsons 2005-03-24 22:38:11 UTC
Note, the ExecCommand problem was addressed in Xprint bug #2254, but this new
bug refers to attributes.h, not attributes.c, i.e. the definition of
ExecCommand.  I think #2254 only cleared the reference in attributes.c.
Comment 2 Juergen Kreileder 2005-04-01 04:29:36 UTC
Note that the 'lib' vs 'lib64' issue is Debian specific.  The AMD64 and PPC64
ABIs say that 'lib64' is the way to go.  Most distributions follow that and put
64-bit libs into 'lib64' dirs.  Debian/AMD64 and Debian/PPC64 violate the ABI in
this respect and put 64-bit libs into 'lib'.
Comment 3 Drew Parsons 2005-04-01 05:59:41 UTC
Oh ok.  I'm surprised to hear it.  Normally Debian is good about following
standards. They must have decided the standards suck ;)

Thanks for letting me know. I guess that means this bug can be closed (apart
from the extra ExecCommand deletion).
Comment 4 Corbin Simpson 2011-09-13 15:48:11 UTC
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

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.