Linux bluetooth development
 help / color / mirror / Atom feed
From: Alain Volmat <avolmat@src.ricoh.co.jp>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] 'make' and 'make install' not working
Date: Thu, 17 Mar 2005 18:30:11 +0900	[thread overview]
Message-ID: <20050317093011.GM4513@snoopy.src.ricoh.co.jp> (raw)
In-Reply-To: <20050317091358.63188.qmail@web52403.mail.yahoo.com>

Hi Jose,

this has actually nothing to do with Bluetooth I think but...

a common way to do, in case of your gcc is a a specific location
is to use CC environment variable.
CC=mygcc AR=myar LD=myLD NM=myNM ./configure ....

well here you don't need AR, LD, NM I think but that's just for the example.
so just doing CC=yourgccpath/gcc ./configure should do the trick.

or just follow what configure is telling you ...
> configure: error: no acceptable C compiler found in $PATH
since it couldn't found gcc inside $PATH, then add gcc's location into $PATH :D

Alain

* jose [Thu, 17 Mar 2005 at 01:13 -0800]
<quote>
> Hi,
> 
> After downloadin the bluez files, i did './configure',
> but iam unable to 'make' or 'make install'.
> 
> this is what i got when i did ./configure
> 
> 
> jose:/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
> 
> 
> 
> now, how do i set the path to gcc?
> 
> Thanks in advance,
> Jose
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> 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
</quote>


-------------------------------------------------------
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  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  9:13 [Bluez-devel] 'make' and 'make install' not working jose
2005-03-17  9:30 ` Alain Volmat [this message]
2005-03-19 16:05 ` Anderson Clayton B Rodrigues

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=20050317093011.GM4513@snoopy.src.ricoh.co.jp \
    --to=avolmat@src.ricoh.co.jp \
    --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