All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH] php: Fix native build due mistakenly linking against host's iconv
Date: Sun, 24 Aug 2014 22:36:35 +0200	[thread overview]
Message-ID: <20140824203635.GL20524@jama> (raw)
In-Reply-To: <CAP9ODKoDCx4yHcKrfMiZr85vorRm-8fcsy6zG-r+YDxpp17bPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

On Sun, Aug 24, 2014 at 04:45:22PM -0300, Otavio Salvador wrote:
> On Sun, Aug 24, 2014 at 4:39 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
> > The configure script has mistakenly choose to enable iconv support,
> > due host to provide it, adding '/usr/lib' to the linking flags and
> > failing as:
> >
> > ,----[ Linking error while testing 'fork' support ]
> > | conftest.c:268: warning: conflicting types for built-in function 'fork'
> > | .../build/tmp/sysroots/x86_64-linux/usr/lib/libxml2.so:
> > |     undefined reference to `gzopen64@ZLIB_1.2.3.3'
> > | collect2: ld returned 1 exit status
> > `----
> >
> > This patch disables iconv support for native builds fixing the error.
> >
> > Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> 
> Same error exist in Daisy.
> 
> I did the rebase here and I can send a patch for it, as it has a minor
> conflict due the pkgconfig rework. Martin, do you want me to send the
> patch on top of Daisy as well or do you resolve the conflict yourself?

Please send it.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-08-24 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 19:39 [meta-oe][PATCH] php: Fix native build due mistakenly linking against host's iconv Otavio Salvador
2014-08-24 19:45 ` Otavio Salvador
2014-08-24 20:36   ` Martin Jansa [this message]
2014-08-28  2:37 ` akuster808
2014-08-28  9:26   ` Martin Jansa

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=20140824203635.GL20524@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.