All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benno <b.schweikert@prosystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] Poco 1.6.1 with glib for Raspberry Pi
Date: Tue, 3 Nov 2015 10:49:45 +0100	[thread overview]
Message-ID: <56388339.6080904@prosystems.de> (raw)

Hello Everyone,

I got Problems with POCO 1.6.1 compiles with the 'unbundled' Flag for 
Raspberry Pi.

When I compile my program with the POCO libs from buildroot this error 
appear:


|..../libPocoFoundation.so: undefined reference to `_pcre_ucd_stage1' 
|||....|/libPocoFoundation.so: undefined reference to 
`_pcre_ucd_records' |||....|/libPocoFoundation.so: undefined reference 
to `_pcre_ucp_gentype' |||....|/libPocoFoundation.so: undefined 
reference to `_pcre_ucd_stage2'|


after a short internet search I found out that other people have the 
same problem too but no clear solution to solve it.

I made sure that the packages pcre, zlib, expat and sqlite are checked 
in buildroot then the program run through compilation,
but when I execute it on the pi the program returns with the error:

'undefined symbole: _prce_ucd_stage1'

Did I missed something important?

For my kernel I use glibc, for the FPEnviroment.
The only POCO packages that I  need are: Foundation, XML, Util, Net and 
Sqlit.
I'm building on a Ubuntu 14.04 64 Bit System.

-- 
Mit freundlichen Gr??en / with best regards


Benno Schweikert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151103/89c822c8/attachment.html>

             reply	other threads:[~2015-11-03  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  9:49 Benno [this message]
2015-11-03 14:19 ` [Buildroot] Poco 1.6.1 with glib for Raspberry Pi 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

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=56388339.6080904@prosystems.de \
    --to=b.schweikert@prosystems.de \
    --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 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.