All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Naranjo <manuel@aircable.net>
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: Sat, 08 Dec 2007 20:30:42 -0300	[thread overview]
Message-ID: <475B2922.5090001@aircable.net> (raw)
In-Reply-To: <1197156509.12292.251.camel@violet>

Marcel
> the bluez-utils is not installing any libraries. Never has been and
> never will be.
>   
You are right, but it install the services inside the lib folder, and
that's making conflicts. If you don't get those to the right folder
(lib64) in this case, then when you want to use any of those services
(serial service for example) via dbus you get an error telling that the
elf version is not right (even though it is, it's elf64)

> 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
>   
Ok, isn't there a way to know this from autotools? Actually this is the
only project that I had faced with such problems.

Thanks,
Manuel Naranjo

-------------------------------------------------------------------------
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:30 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
2007-12-08 23:30     ` Manuel Naranjo [this message]
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=475B2922.5090001@aircable.net \
    --to=manuel@aircable.net \
    --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.