From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Poco 1.6.1 with glib for Raspberry Pi
Date: Tue, 3 Nov 2015 17:22:15 +0100 [thread overview]
Message-ID: <20151103172215.4afe95f7@free-electrons.com> (raw)
In-Reply-To: <5638CEBF.1030502@prosystems.de>
Benno,
On Tue, 3 Nov 2015 16:11:59 +0100, Benno wrote:
> > This is unclear. Can you give the *exact* commands you are running
> > using the example program above to get the problem ?
>
> for compiling:
> path/to/buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabi-g++
> -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"src/Example.d"
> -MT"src/Example.d" -o "src/Example.o" "../src/Example.cpp"
>
> for linking:
> path/to/output/host/usr/bin/arm-buildroot-linux-gnueabi-g++
> -L/path/to/buildroot/output/target/usr/lib -o "ExampleProj"
> ./src/Example.o -lPocoFoundation -lPocoUtil -lPocoNet
I didn't test your program since you never gave me the Example.cpp
source code. Instead, I used the example HTTP server provided in the
Poco documentation. I indeed stumbled across the pcre issue, and also a
library installation problem.
I've fixed both issues in commit
http://git.buildroot.net/buildroot/commit/?id=b8527eb3c017c74c861db8b21f8a0def55988382.
With those patches, I can successfully build and run the HTTP server
example.
Thanks for reporting the issue in the first place, and don't hesitate
to test and report back if the patches are working for you.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-03 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 9:49 [Buildroot] Poco 1.6.1 with glib for Raspberry Pi Benno
2015-11-03 14:19 ` Thomas Petazzoni
2015-11-03 14:58 ` Benno
2015-11-03 15:02 ` Thomas Petazzoni
2015-11-03 15:11 ` Benno
2015-11-03 16:22 ` Thomas Petazzoni [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=20151103172215.4afe95f7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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