public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jouni.Lohikoski@iki.fi" <jlohikos@cc.hut.fi>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez-hciemu-1.0 install error- Glib Not found
Date: Wed, 29 Sep 2004 18:52:22 +0300	[thread overview]
Message-ID: <20040929155222.GA131327@kosh.hut.fi> (raw)
In-Reply-To: <296459384.12087@bjut.edu.cn>

On Wed, Sep 29, 2004 at 08:15:46PM +0800, Jin Pu wrote:
>  checking for glib-config... not found
>  configure: error: GLib not found
>  ---then ./configure exit back to the shell---
>  
>  I know from the README, I need GLib package before
>  install the hciemu. But I suppose that the package is
>  already installed with RedHat 9.

You need glib-devel package in RH9 or in Fedora. When developing
something, you need many devel-packages.

After error like this, you could try if you find yourself the missing
file/program. One method here:

# locate glib-config
.....probably won't find it.

Then to < http://rpm.pbone.net/ >
and "Search for rpms which contain given file name": "glib-config"

...you can guess from the results, you'll need glib-devel package.

// jouni



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-09-29 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 12:15 [Bluez-users] bluez-hciemu-1.0 install error- Glib Not found Jin Pu
2004-09-29 15:52 ` Jouni.Lohikoski@iki.fi [this message]

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=20040929155222.GA131327@kosh.hut.fi \
    --to=jlohikos@cc.hut.fi \
    --cc=Jouni.Lohikoski@iki.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox