All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: libconfig installs in /lib, should be /lib64
Date: Fri, 22 Jan 2010 15:50:58 +0100	[thread overview]
Message-ID: <4B59BB52.1090607@amd.com> (raw)

Hi,

the libconfig shipped with libxl is put in the /usr/lib directory (at 
least on my setup). Since the library is ELF64, it should go into 
/usr/lib64 - as all the other Xen libraries do.
I have no idea of the autotools / Makefile magic to do this (and don't 
feel like learning about it this afternoon), so I hope someone else can 
fix this. The default Xen libraries include $(XEN_ROOT)/tools/Rules.mk, 
which eventually pulls in LIB_DIR from x86_{32,64}.mk, which contains 
the correct directory. But I don't see an easy way to inject this into 
the autotools setup of libconfig.
The same issue is with the pkgconfig directory, which also should reside 
below lib64 as well as the path written in the .pc file itself.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

             reply	other threads:[~2010-01-22 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 14:50 Andre Przywara [this message]
2010-01-22 15:24 ` libconfig installs in /lib, should be /lib64 Stefano Stabellini
2010-01-22 15:31   ` Stefano Stabellini
2010-01-22 17:03     ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B59BB52.1090607@amd.com \
    --to=andre.przywara@amd.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.