From: Saul Wold <sgw@linux.intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: native gcc compiler error
Date: Mon, 18 Jul 2011 10:22:26 -0700 [thread overview]
Message-ID: <4E246BD2.1020903@linux.intel.com> (raw)
In-Reply-To: <2D727437-8D9C-44CA-8470-EAD5E6932976@kernel.crashing.org>
On 07/18/2011 07:54 AM, Kumar Gala wrote:
>
> On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
>
>> On Mon, Jul 18, 2011 at 5:58 AM, Kumar Gala<galak@kernel.crashing.org> wrote:
>>> I've been working on trying to get an e500v2 (linux-gnuspe) compiler working and seem to have build a native toolchain. However when I try and compile a simple hello world style app I get:
>>>
>>> root@p2020-ds:~# gcc float.c
>>> gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
>>> compilation terminated.
>>>
>>> Wondering if anyone's seen this before and had any ideas.
>>>
>>
>> You can try -fno-use-linker-plugin as a workaround. Does
>> liblto_plugin.so exist on target rfs ?
>> it might be then gcc driver bug if the library is not there then we
>> forgot to package it.
>
> File appears to be there:
> root@p2020-ds:/# file /usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so.0.0.0
> ./usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so.0.0.0: ELF 32-bit MSB shared object, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked, with unknown capability 0x41000000 = 0xf676e75, with unknown capability 0x10000 = 0x70402, stripped
>
> root@p2020-ds:~# ls -lstr /usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/
> total 31624
> 9812 -rwxr-xr-x 1 root root 10046304 Jul 16 22:40 lto1
> 28 -rwxr-xr-x 1 root root 26344 Jul 16 22:40 lto-wrapper
> 60 -rwxr-xr-x 1 root root 60132 Jul 16 22:40 liblto_plugin.so.0.0.0
> 124 -rwxr-xr-x 1 root root 124776 Jul 16 22:40 collect2
> 11208 -rwxr-xr-x 1 root root 11476244 Jul 16 22:40 cc1plus
> 10392 -rwxr-xr-x 1 root root 10640644 Jul 16 22:40 cc1
> 0 lrwxrwxrwx 1 root root 22 Jul 17 15:07 liblto_plugin.so.0 -> liblto_plugin.so.0.0.0
>
> So not clear why its not finding it.
>
This looks similar to Yocto Bug 1233
(http://bugzilla.yoctoproject.org/show_bug.cgi?id=1233
Can you confirm if you have the following commit in your branch?
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2429773613cb95b6a0541b5cce6ce1338d5cfc2b
It's possible you might be missing this and it's not finding the file
correctly.
As Richard mentioned also, an strace output would be helpful if you do
have the above commit.
Thanks
Sau!
> - k
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2011-07-18 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 12:58 native gcc compiler error Kumar Gala
2011-07-18 14:45 ` Khem Raj
2011-07-18 14:54 ` Kumar Gala
2011-07-18 17:04 ` Richard Purdie
2011-07-18 17:22 ` Saul Wold [this message]
2011-07-18 18:01 ` Kumar Gala
2011-07-18 18:04 ` Khem Raj
2011-07-18 18:24 ` Kumar Gala
2011-07-18 18:37 ` Khem Raj
2011-07-18 19:22 ` Kumar Gala
2011-07-18 19:27 ` Khem Raj
2011-07-18 20:04 ` Kumar Gala
2011-07-18 20:20 ` Khem Raj
2011-07-18 18:14 ` Kumar Gala
2011-07-19 14:28 ` Kumar Gala
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=4E246BD2.1020903@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=galak@kernel.crashing.org \
--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.