From: "Woronicz, Bartosz ( NSN - PL/Wroclaw)" <bartosz.woronicz@nokia.com>
To: Chris Z. <winotu.email@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Native packages compiled with host gcc set in PATH and with LD_LIBRARY_PATH to libstd++
Date: Fri, 6 May 2016 16:38:55 +0200 [thread overview]
Message-ID: <572CAC7F.8090602@nokia.com> (raw)
In-Reply-To: <1C3E490A-CAB1-4487-AED1-5919690AB6D9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
Nokia Networks - PL/Wroclaw
On 06.05.2016 15:55, EXT Khem Raj wrote:
>
>> On May 6, 2016, at 1:43 AM, Chris Z. <winotu.email@gmail.com
>> <mailto:winotu.email@gmail.com>> wrote:
>>
>> Hi,
>>
>> Any tips ?
>
> you need to insert your non-standard install of gcc-4.9 and glibc into
> OE build via BUILD_CFLAGS
> and prepending it to your PATH variable that bitbake will see.
I use such hack in local.conf
BUILD_LDFLAGS_append_class-native = "${BB_EXT_ENV_GLIBCXX_RPATH}"
where BB_EXT_ENV_GLIBCXX_RPATH is
$ export BB_EXT_ENV_GLIBCXX_RPATH="$(echo "$LD_LIBRARY_PATH" | tr ':'
'\n' | grep gcc | xargs -I % echo " -Wl,-rpath,%" | tr '\n' ' ')"
in my oe-init-buildenv wrapping script
>
>>
>> On Fri, Mar 4, 2016 at 4:13 PM, Chris Z. <winotu.email@gmail.com
>> <mailto:winotu.email@gmail.com>> wrote:
>>
>> Hi,
>>
>> I have set newer gcc(4.9) in PATH and with proper
>> LD_LIBRARY_PATH. Default system gcc is 4.4.
>>
>> Bulding cmake-native fails when bootstrap cmake tries to compile
>> cmake native binary.
>>
>> This is due to the fact that bootstrap was compiled with newer
>> glibcxx and it can't be found in system/host /usr/lib, /usr/lib64
>> nor in -rpath.
>>
>> rpath is set to
>> -Wl,-rpath,${STAGING_LIBDIR_NATIVE} \
>> -Wl,-rpath,${STAGING_BASE_LIBDIR_NATIVE} \
>>
>> from BUILD_LDFLAGS var in bitbake.conf which is expand in native
>> class.
>>
>> What is the correct approach to fix this ? Or I shouldn't use gcc
>> from PATH for compilation of native packages ?
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
[-- Attachment #2: Type: text/html, Size: 5608 bytes --]
prev parent reply other threads:[~2016-05-06 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 15:13 Native packages compiled with host gcc set in PATH and with LD_LIBRARY_PATH to libstd++ Chris Z.
2016-05-06 8:43 ` Chris Z.
2016-05-06 13:55 ` Khem Raj
2016-05-06 14:38 ` Woronicz, Bartosz ( NSN - PL/Wroclaw) [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=572CAC7F.8090602@nokia.com \
--to=bartosz.woronicz@nokia.com \
--cc=winotu.email@gmail.com \
--cc=yocto@yoctoproject.org \
/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.