Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] bluez installation query
Date: Thu, 17 Mar 2005 11:25:49 +0100	[thread overview]
Message-ID: <1111055149.11792.51.camel@pegasus> (raw)
In-Reply-To: <20050317060516.82046.qmail@web41129.mail.yahoo.com>

Hi Jose,

> On suse linux 9.1, iam not able to make and make
> install the bluez install files 'utils, libs etc'.
> when i say ./configure, this is what is listed:
> 
> ose:/home/jose/bluetooth/bluez-hcidump-1.18 #
> ./configure --with-gcc --prefix=/usr
> --mandir=/usr/share/man
> checking for a BSD-compatible install...
> /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... no
> checking whether to enable maintainer-specific
> portions of Makefiles... no
> checking for gcc... no
> checking for cc... no
> checking for cc... no
> checking for cl... no
> configure: error: no acceptable C compiler found in
> $PATH
> See `config.log' for more details.
> 
> 
> how do i set the path to the gcc?

is this the SuSE 9.1 Personal edition? If yes, then you don't have a GCC
on it. Otherwise simply install it.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-03-17 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  6:05 [Bluez-devel] bluez installation query jose pl
2005-03-17 10:25 ` Marcel Holtmann [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=1111055149.11792.51.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sf.net \
    --cc=bluez-devel@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