From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Plugz Building Problem
Date: Fri, 19 Jan 2007 10:26:34 +0100 [thread overview]
Message-ID: <45B08ECA.9090109@free.fr> (raw)
In-Reply-To: <45B03C7E.000044.16122@bj163app38.163.com>
Hi,
Did you use a Windows station at some point in the download process ??
Fabien
> Hello ,everybody!
>
> I am a newbie of bluez.I have downloaded plugz from cvs repository
> informed on site http://bluetooth-alsa.sourceforge.net/build.html.when I
> built sbc project I found bootstrap cound not run on my fc6 system
> directly.It printed the following error message:bash: ./bootstrap:
> /bin/sh^M: bad interpreter: ?????????, then I tried to run
> every commands in bootstrap one by one and It generated configure script
> .The problem also existed when building plugz.So I built sbc project
> successfully at last.However,I had another trouble when I built
> plugz.After I ran configure to generate correspording files make had errors:
>
> make all-recursive
> make[1]: Entering directory `/download/bluetooth-alsa/plugz'
> Making all in avdtp
> make[2]: Entering directory `/download/bluetooth-alsa/plugz/avdtp'
> /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/include -Wall -O2
> -o avtest avtest.o -lbluetooth libavdtp.a -lbluetooth -lasound -lm -ldl
> -lpthread -lbluetooth
> : command not found1:
> : command not found3:
> : command not found0:
> /bin/sed:-e ??? #1,?? 10:unknown option to `s'
> : command not found4:
> : command not found8:
> : command not found3:
> : command not found4:
> ../libtool: line 409: syntax error near unexpected token `elif'
> './libtool: line 409: `elif test "X$1" = X--fallback-echo; then
> make[2]: *** [avtest] ?? 2
> make[2]: Leaving directory `/download/bluetooth-alsa/plugz/avdtp'
> make[1]: *** [all-recursive] ?? 1
> make[1]: Leaving directory `/download/bluetooth-alsa/plugz'
> make: *** [all] ?? 2.
>
> I tried to run libtool script generated by configure following hints.It
> prints the errors message as well:
> : command not found
> : command not found
> : command not found
> /bin/sed:-e ??? #1,?? 10:unknown option to `s'
> : command not found
> : command not found
> : command not found
> : command not found
> libtool: line 409: syntax error near unexpected token `elif'
> 'ibtool: line 409: `elif test "X$1" = X--fallback-echo; then
>
> So I found out that the problem was the libtool script.Then I found out
> there was another libtool script in /usr/bin which was installed in
> libtool-1.5.22-6.1 package and it's different from the libtool generated
> by configure ,and then I replaced libtool by /usr/bin/libtool and make
> ran smoothly.The make masseges in the end is
>
> (cd .libs && rm -f libasound_module_ctl_sco.so.0 && ln -s
> libasound_module_ctl_sco.so.0.0.0 libasound_module_ctl_sco.so.0)
> (cd .libs && rm -f libasound_module_ctl_sco.so && ln -s
> libasound_module_ctl_sco.so.0.0.0 libasound_module_ctl_sco.so)
> ar cru .libs/libasound_module_ctl_sco.a ctl_sco.o
> ranlib .libs/libasound_module_ctl_sco.a
> creating libasound_module_ctl_sco.la
> (cd .libs && rm -f libasound_module_ctl_sco.la && ln -s
> ../libasound_module_ctl_sco.la libasound_module_ctl_sco.la)
> make[3]: Leaving directory `/download/bluetooth-alsa/plugz/alsa-plugins'
> make[2]: Leaving directory `/download/bluetooth-alsa/plugz/alsa-plugins'
> make[2]: Entering directory `/download/bluetooth-alsa/plugz'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory `/download/bluetooth-alsa/plugz'
> make[1]: Leaving directory `/download/bluetooth-alsa/plugz'
>
>
> However I found there is no sample.a2dprc file in subdirectory
> alsa-plugins after make install finished,so I counldn't continue to
> install plugz following instuction on the site
> http://bluetooth-alsa.sourceforge.net/build.html.
> I am sorry for wasting your time for my unbearably long description.I
> questions are :
> what difference is there between the two libtools,one of which is
> installed in libtool-1.5.22-6.1 and the other of which is generated by
> plugz ?have I built plugz successully by replacement of libtool ?can it
> work with this ?How can I complete the installation ?and is plugz able
> to embed in arm s3c2440.
>
> Thank you in advance!I am so grateful for your reply since I don't know
> what to do now!
>
>
>
> Yours Jimscene Wang
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-19 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 3:35 [Bluez-devel] Plugz Building Problem 飞天猪
2007-01-19 9:26 ` Fabien Chevalier [this message]
2007-01-20 0:52 ` [Bluez-devel] Plugz Building Prob lem 飞天猪
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=45B08ECA.9090109@free.fr \
--to=fabchevalier@free.fr \
--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