From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error compiling bluez-utils for buildroot/ARM
Date: Thu, 17 Mar 2005 12:14:20 +0100 [thread overview]
Message-ID: <1111058060.11792.63.camel@pegasus> (raw)
In-Reply-To: <4239536C.5030202@amplex.dk>
Hi Stephan,
> If I add --libdir=${TARGET_DIR}/usr/lib (which expands to
> --libdir=/home/sth/au/buildroot/build_arm/root/usr/lib) to the
> configure command, the configuring succeeds, but compilation fails:
>
> ...
>
> /home/sth/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc
> -I/usr/include -DDBUS_API_SUBJECT_TO_CHANGE -Os -pipe -o hcid
> main.o security.o storage.o lib.o parser.o lexer.o kword.o
> glib-ectomy.o -L/home/sth/au/buildroot/build_arm/root/usr/lib
> -lbluetooth
> lexer.o(.text+0x7e0): In function `yy_get_next_buffer':
> : undefined reference to `_IO_getc'
> collect2: ld returned 1 exit status
this looks like we have a problem with the generated code for the
parser. Try to remove parser.[ch] and lexer.c. Maybe you need to add
another library for the target platform to provide _IO_getc().
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
next prev parent reply other threads:[~2005-03-17 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 9:52 [Bluez-devel] Error compiling bluez-utils for buildroot/ARM Stephan Henningsen
2005-03-17 11:14 ` Marcel Holtmann [this message]
2005-03-17 11:59 ` Stephan Henningsen
2005-03-17 12:38 ` Marcel Holtmann
2005-03-17 13:20 ` Stephan Henningsen
2005-03-17 13:18 ` Stephan Henningsen
2005-03-17 13:36 ` Stephan Henningsen
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=1111058060.11792.63.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.