All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [BlueZ-Announce] Release of bluez-libs-3.23 and	bluez-utils-3.23
Date: Sun, 09 Dec 2007 00:28:29 +0100	[thread overview]
Message-ID: <1197156509.12292.251.camel@violet> (raw)
In-Reply-To: <475B263E.4060801@aircable.net>

Hi Manuel,

> I think there's a bug in the automake scripts, both bluez-libs and
> bluez-utils. In 64 bits systems if there's lib64 present then both
> packages are trying to install to lib instead of lib64. I sent a rather
> simple patch for this, but I think it should be more complex, and it
> didn't applied to libs only utils

the bluez-utils is not installing any libraries. Never has been and
never will be.

For the bluez-libs this is on purpose and you can overwrite it with
--libdir when calling configure. All distros are different and
especially with the new multi-arch stuff.

Regards

Marcel



-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-12-08 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1197153708.12292.247.camel@violet>
2007-12-08 23:18 ` [Bluez-users] [BlueZ-Announce] Release of bluez-libs-3.23 and bluez-utils-3.23 Manuel Naranjo
2007-12-08 23:28   ` Marcel Holtmann [this message]
2007-12-08 23:30     ` Manuel Naranjo
2007-12-09  0:42       ` Marcel Holtmann

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=1197156509.12292.251.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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.