All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Cliff Brake <cliff.brake@gmail.com>,
	Martin Jansa <martin.jansa@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][for-daisy][PATCH] php: Fix native build due mistakenly linking against host's iconv
Date: Thu, 28 Aug 2014 12:37:02 -0700	[thread overview]
Message-ID: <53FF84DE.7040402@gmail.com> (raw)
In-Reply-To: <CAP9ODKrzJAW+NXr7LmzQ0+CnmJE_pc5786Xq64AMqeRN_X6=kg@mail.gmail.com>

  Acked-by: Armin Kuster <akuster808@gmail.com>


might have acked the wrong one.



On 08/28/2014 06:54 AM, Otavio Salvador wrote:
> Martin,
>
> On Wed, Aug 27, 2014 at 11:04 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Mon, Aug 25, 2014 at 10:15 AM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>> On Sun, Aug 24, 2014 at 8:36 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>> On Sun, Aug 24, 2014 at 2:03 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.
>>>>>
>>>>
>>>> the patch subject is confusing. enabling iconv is not mistake but its
>>>> probed and if found its used. in this case libz against which libxml2
>>>> is linked is not used here and that ends up in error.
>>>>
>>>> Can you try to add --with-iconv-dir=${STAGING_LIBDIR_NATIVE}
>>>> and see if it helps ?
>>>
>>> The native does not depends on virtual/iconv. So the natural thing is
>>> to disable it.
>>
>> Hey guys, can you review this one for backporting?
>
> This is the Daisy backport one.
>


  reply	other threads:[~2014-08-28 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 21:03 [meta-oe][for-daisy][PATCH] php: Fix native build due mistakenly linking against host's iconv Otavio Salvador
2014-08-24 23:36 ` Khem Raj
2014-08-25 13:15   ` Otavio Salvador
2014-08-28  2:04     ` Otavio Salvador
2014-08-28 13:54       ` Otavio Salvador
2014-08-28 19:37         ` akuster808 [this message]
2014-08-29 18:11           ` Cliff Brake

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=53FF84DE.7040402@gmail.com \
    --to=akuster808@gmail.com \
    --cc=cliff.brake@gmail.com \
    --cc=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.