From: Vikrampal <vikram.pal@samsung.com>
To: 'Szymon Janc' <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, cpgs@samsung.com
Subject: RE: BlueZ make error
Date: Tue, 17 Jun 2014 15:15:01 +0530 [thread overview]
Message-ID: <014301cf8a10$d1c51e20$754f5a60$@samsung.com> (raw)
In-Reply-To: <2956882.SkGP9SSC5Z@uw000953>
Hi Szymon,
>-----Original Message-----
>From: Szymon Janc [mailto:szymon.janc@tieto.com]
>Sent: Monday, June 16, 2014 4:45 PM
>To: Vikrampal
>Cc: linux-bluetooth@vger.kernel.org; cpgs@samsung.com
>Subject: Re: BlueZ make error
>
>Hi Vikrampal,
>
>On Tuesday 03 of June 2014 18:55:33 Vikrampal wrote:
>> Hi,
>>
>> While building the latest BlueZ, I'm getting below error:
>>
>> krampal-ubuntu:~/bluez$ sudo make
>
>Why building as superuser?
>
>> make --no-print-directory all-am
>> CC client/main.o
>> client/main.c: In function 'cmd_version':
>> client/main.c:1098:28: error: 'VERSION' undeclared (first use in this
>> function)
>> rl_printf("Version %s\n", VERSION);
>> ^
>> client/main.c:1098:28: note: each undeclared identifier is reported
>> only once for each function it appears in
>> client/main.c: In function 'main':
>> client/main.c:1489:18: error: 'VERSION' undeclared (first use in this
>> function)
>> printf("%s\n", VERSION);
>> ^
>> make[1]: *** [client/main.o] Error
>> make: *** [all] Error 2
>>
>> Please help me. Thanks!
>
>That could happen if you tempered with either Makefile or config.h files (both are auto generated).
>
>I suggest running configure (or bootstrap-configure if this is for development) again.
>
>--
>Best regards,
>Szymon Janc
I could build bluez by running bootstrap-configure, make and make install.
This time not as a superuser. Thanks a lot for your kind advice, it worked!
Regards,
Vikram
prev parent reply other threads:[~2014-06-17 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 13:25 BlueZ make error Vikrampal
2014-06-16 11:14 ` Szymon Janc
2014-06-17 9:45 ` Vikrampal [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='014301cf8a10$d1c51e20$754f5a60$@samsung.com' \
--to=vikram.pal@samsung.com \
--cc=cpgs@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.com \
/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