* native gcc compiler error
@ 2011-07-18 12:58 Kumar Gala
2011-07-18 14:45 ` Khem Raj
0 siblings, 1 reply; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 12:58 UTC (permalink / raw)
To: Yocto discussion list
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.
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
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
0 siblings, 1 reply; 15+ messages in thread
From: Khem Raj @ 2011-07-18 14:45 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
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.
> - k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
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
0 siblings, 2 replies; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 14:54 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
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.
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 14:54 ` Kumar Gala
@ 2011-07-18 17:04 ` Richard Purdie
2011-07-18 17:22 ` Saul Wold
1 sibling, 0 replies; 15+ messages in thread
From: Richard Purdie @ 2011-07-18 17:04 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Mon, 2011-07-18 at 09:54 -0500, 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.
Does strace show where its looking for it?
Cheers,
Richard
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 14:54 ` Kumar Gala
2011-07-18 17:04 ` Richard Purdie
@ 2011-07-18 17:22 ` Saul Wold
2011-07-18 18:01 ` Kumar Gala
2011-07-19 14:28 ` Kumar Gala
1 sibling, 2 replies; 15+ messages in thread
From: Saul Wold @ 2011-07-18 17:22 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
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
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 17:22 ` Saul Wold
@ 2011-07-18 18:01 ` Kumar Gala
2011-07-18 18:04 ` Khem Raj
2011-07-18 18:14 ` Kumar Gala
2011-07-19 14:28 ` Kumar Gala
1 sibling, 2 replies; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 18:01 UTC (permalink / raw)
To: Saul Wold; +Cc: Yocto discussion list
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
> 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!
access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
So it appears we are missing in the package 'liblto_plugin.so' link.
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
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:14 ` Kumar Gala
1 sibling, 1 reply; 15+ messages in thread
From: Khem Raj @ 2011-07-18 18:04 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Mon, Jul 18, 2011 at 11:01 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
>
>> 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!
>
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>
> So it appears we are missing in the package 'liblto_plugin.so' link.
Does that symlink exist in your gcc install tree during build ? if not
then gcc makefiles need to generate it. if its just a case we
forgot to bundle it then we should add it to FILES var of gcc.
>
> - k
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 18:01 ` Kumar Gala
2011-07-18 18:04 ` Khem Raj
@ 2011-07-18 18:14 ` Kumar Gala
1 sibling, 0 replies; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 18:14 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Jul 18, 2011, at 1:01 PM, Kumar Gala wrote:
>
> On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
>
>> 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!
>
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>
> So it appears we are missing in the package 'liblto_plugin.so' link.
>
> - k
If I add the link by hand the issues goes away.
- K
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 18:04 ` Khem Raj
@ 2011-07-18 18:24 ` Kumar Gala
2011-07-18 18:37 ` Khem Raj
0 siblings, 1 reply; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 18:24 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
>>>>> 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!
>>
>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>
>> So it appears we are missing in the package 'liblto_plugin.so' link.
>
> Does that symlink exist in your gcc install tree during build ? if not
> then gcc makefiles need to generate it. if its just a case we
> forgot to bundle it then we should add it to FILES var of gcc.
How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
For the MPC8315E-RDB build:
http://pastebin.com/yYSww5nK
[ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
For the e500v2 (P2020-DS) build:
http://pastebin.com/B1qyfbGE
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 18:24 ` Kumar Gala
@ 2011-07-18 18:37 ` Khem Raj
2011-07-18 19:22 ` Kumar Gala
0 siblings, 1 reply; 15+ messages in thread
From: Khem Raj @ 2011-07-18 18:37 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>>>> 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!
>>>
>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>
>>> So it appears we are missing in the package 'liblto_plugin.so' link.
>>
>> Does that symlink exist in your gcc install tree during build ? if not
>> then gcc makefiles need to generate it. if its just a case we
>> forgot to bundle it then we should add it to FILES var of gcc.
>
> How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
>
> For the MPC8315E-RDB build:
>
> http://pastebin.com/yYSww5nK
>
> [ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
>
> For the e500v2 (P2020-DS) build:
>
> http://pastebin.com/B1qyfbGE
>
> - k
hmm the symlink goes into gcc-dev package since the package splitter
sees a sumlink xyz.so
but in this case this should be packages explicitly into gcc as we see
gcc depends on it for normal
execution or may be create a new package called liblto or somesuch
Can you install gcc-dev package on your device and see if this helps ?
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 18:37 ` Khem Raj
@ 2011-07-18 19:22 ` Kumar Gala
2011-07-18 19:27 ` Khem Raj
0 siblings, 1 reply; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 19:22 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>>>>> 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!
>>>>
>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>
>>>> So it appears we are missing in the package 'liblto_plugin.so' link.
>>>
>>> Does that symlink exist in your gcc install tree during build ? if not
>>> then gcc makefiles need to generate it. if its just a case we
>>> forgot to bundle it then we should add it to FILES var of gcc.
>>
>> How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
>>
>> For the MPC8315E-RDB build:
>>
>> http://pastebin.com/yYSww5nK
>>
>> [ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
>>
>> For the e500v2 (P2020-DS) build:
>>
>> http://pastebin.com/B1qyfbGE
>>
>> - k
>
> hmm the symlink goes into gcc-dev package since the package splitter
> sees a sumlink xyz.so
> but in this case this should be packages explicitly into gcc as we see
> gcc depends on it for normal
> execution or may be create a new package called liblto or somesuch
>
> Can you install gcc-dev package on your device and see if this helps ?
Yes if I install gcc-dev it works.
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 19:22 ` Kumar Gala
@ 2011-07-18 19:27 ` Khem Raj
2011-07-18 20:04 ` Kumar Gala
0 siblings, 1 reply; 15+ messages in thread
From: Khem Raj @ 2011-07-18 19:27 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Mon, Jul 18, 2011 at 12:22 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
>
>> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>>>>>> 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!
>>>>>
>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>
>>>>> So it appears we are missing in the package 'liblto_plugin.so' link.
>>>>
>>>> Does that symlink exist in your gcc install tree during build ? if not
>>>> then gcc makefiles need to generate it. if its just a case we
>>>> forgot to bundle it then we should add it to FILES var of gcc.
>>>
>>> How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
>>>
>>> For the MPC8315E-RDB build:
>>>
>>> http://pastebin.com/yYSww5nK
>>>
>>> [ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
>>>
>>> For the e500v2 (P2020-DS) build:
>>>
>>> http://pastebin.com/B1qyfbGE
>>>
>>> - k
>>
>> hmm the symlink goes into gcc-dev package since the package splitter
>> sees a sumlink xyz.so
>> but in this case this should be packages explicitly into gcc as we see
>> gcc depends on it for normal
>> execution or may be create a new package called liblto or somesuch
>>
>> Can you install gcc-dev package on your device and see if this helps ?
>
> Yes if I install gcc-dev it works.
OK thanks. So I think we just need to package this symlink along with gcc
and all is good.
>
> - k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 19:27 ` Khem Raj
@ 2011-07-18 20:04 ` Kumar Gala
2011-07-18 20:20 ` Khem Raj
0 siblings, 1 reply; 15+ messages in thread
From: Kumar Gala @ 2011-07-18 20:04 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
On Jul 18, 2011, at 2:27 PM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 12:22 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>
>> On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
>>
>>> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>>>>>>> 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!
>>>>>>
>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>
>>>>>> So it appears we are missing in the package 'liblto_plugin.so' link.
>>>>>
>>>>> Does that symlink exist in your gcc install tree during build ? if not
>>>>> then gcc makefiles need to generate it. if its just a case we
>>>>> forgot to bundle it then we should add it to FILES var of gcc.
>>>>
>>>> How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
>>>>
>>>> For the MPC8315E-RDB build:
>>>>
>>>> http://pastebin.com/yYSww5nK
>>>>
>>>> [ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
>>>>
>>>> For the e500v2 (P2020-DS) build:
>>>>
>>>> http://pastebin.com/B1qyfbGE
>>>>
>>>> - k
>>>
>>> hmm the symlink goes into gcc-dev package since the package splitter
>>> sees a sumlink xyz.so
>>> but in this case this should be packages explicitly into gcc as we see
>>> gcc depends on it for normal
>>> execution or may be create a new package called liblto or somesuch
>>>
>>> Can you install gcc-dev package on your device and see if this helps ?
>>
>> Yes if I install gcc-dev it works.
>
> OK thanks. So I think we just need to package this symlink along with gcc
> and all is good.
Agreed, do you mind working up such a patch. I'm not an expert in this area so feel a little concerned about not knowing enough to try and do this cleanly (or generically).
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 20:04 ` Kumar Gala
@ 2011-07-18 20:20 ` Khem Raj
0 siblings, 0 replies; 15+ messages in thread
From: Khem Raj @ 2011-07-18 20:20 UTC (permalink / raw)
To: Kumar Gala; +Cc: Yocto discussion list
On Mon, Jul 18, 2011 at 1:04 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Jul 18, 2011, at 2:27 PM, Khem Raj wrote:
>
>> On Mon, Jul 18, 2011 at 12:22 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>
>>> On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
>>>
>>>> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>>>>>>>> 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!
>>>>>>>
>>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/libexec/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/powerpc-poky-linux-gnuspe/4.6.1/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>> access("/usr/lib/gcc/powerpc-poky-linux-gnuspe/4.6.1/../../../../powerpc-poky-linux-gnuspe/bin/liblto_plugin.so", R_OK) = -1 ENOENT (No such file or directory)
>>>>>>>
>>>>>>> So it appears we are missing in the package 'liblto_plugin.so' link.
>>>>>>
>>>>>> Does that symlink exist in your gcc install tree during build ? if not
>>>>>> then gcc makefiles need to generate it. if its just a case we
>>>>>> forgot to bundle it then we should add it to FILES var of gcc.
>>>>>
>>>>> How do I tell? Which gcc dir should I be looking at under build/tmp/work/* ?
>>>>>
>>>>> For the MPC8315E-RDB build:
>>>>>
>>>>> http://pastebin.com/yYSww5nK
>>>>>
>>>>> [ the first three lines look interesting about packages-split/gcc-dev vs packages-split/gcc ]
>>>>>
>>>>> For the e500v2 (P2020-DS) build:
>>>>>
>>>>> http://pastebin.com/B1qyfbGE
>>>>>
>>>>> - k
>>>>
>>>> hmm the symlink goes into gcc-dev package since the package splitter
>>>> sees a sumlink xyz.so
>>>> but in this case this should be packages explicitly into gcc as we see
>>>> gcc depends on it for normal
>>>> execution or may be create a new package called liblto or somesuch
>>>>
>>>> Can you install gcc-dev package on your device and see if this helps ?
>>>
>>> Yes if I install gcc-dev it works.
>>
>> OK thanks. So I think we just need to package this symlink along with gcc
>> and all is good.
>
> Agreed, do you mind working up such a patch. I'm not an expert in this area so feel a little concerned about not knowing enough to try and do this cleanly (or generically).
yes I will but may be a day or two
>
> - k
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: native gcc compiler error
2011-07-18 17:22 ` Saul Wold
2011-07-18 18:01 ` Kumar Gala
@ 2011-07-19 14:28 ` Kumar Gala
1 sibling, 0 replies; 15+ messages in thread
From: Kumar Gala @ 2011-07-19 14:28 UTC (permalink / raw)
To: Saul Wold; +Cc: Yocto discussion list
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
> 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!
So it appears the fix for bug 1233 isn't complete. Should I re-open the bug or a new one?
- k
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2011-07-19 14:28 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.