From: Ted Feng <artisdom@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: build system defect
Date: Thu, 27 Aug 2009 11:58:56 +0800 [thread overview]
Message-ID: <8e7043060908262058x5fb20f24wf995a82a575abe1d@mail.gmail.com> (raw)
Hi:
I met a problem while making.
Since I like to put all stuff generating from build elsewhere,
I do all the configure, make action in a different directory.
$ ls
bluez-4.50/ bluez-build/
$ cd bluez-build
$ ../bluez-4.50/configure --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --enable-debug -enable-test --enable-gstreamer
--enable-alsa --enable-usb --enable-netlink --enable-tools
--enable-bccmd --enable-pcmcia --enable-hid2hci --enable-dfutool
--enable-hidd --enable-pand --enable-dund --enable-cups
--enable-udevrules --enable-configfiles
...
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/bluetooth.rules
config.status: creating doc/version.xml
config.status: creating src/bluetoothd.8
config.status: creating bluez.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
$ make
make --no-print-directory all-am
CC audio/audio_libasound_module_pcm_bluetooth_la-pcm_bluetooth.lo
CC audio/audio_libasound_module_pcm_bluetooth_la-ipc.lo
...
CCLD test/hciemu
GEN scripts/97-bluetooth.rules
GEN scripts/97-bluetooth-hid2hci.rules
cp: cannot stat `scripts/bluetooth-hid2hci.rules': No such file or directory
make[1]: *** [scripts/97-bluetooth-hid2hci.rules] Error 1
make: *** [all] Error 2
The error seems just a small path problem.
Should I claim this a bug, or I have to live with it?
Thanks in advance.
Regards
Ted
next reply other threads:[~2009-08-27 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 3:58 Ted Feng [this message]
2009-08-27 19:25 ` build system defect Marcel Holtmann
[not found] ` <8e7043060908271916w76adc10fh8fdc088802d3a1f9@mail.gmail.com>
2009-08-28 2:31 ` Ted Feng
2009-08-29 4:32 ` 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=8e7043060908262058x5fb20f24wf995a82a575abe1d@mail.gmail.com \
--to=artisdom@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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