yocto@lists.yoctoproject.org

yes I will but may be a day or two

By Khem Raj · #1970 ·

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

By Kumar Gala <galak@...> · #1969 ·

Re: native gcc compiler error

OK thanks. So I think we just need to package this symlink along with gcc and all is good.

By Khem Raj · #1968 ·

Re: native gcc compiler error

Yes if I install gcc-dev it works. - k

By Kumar Gala <galak@...> · #1967 ·

Re: native gcc compiler error

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

By Khem Raj · #1966 ·

Re: native gcc compiler error

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

By Kumar Gala <galak@...> · #1965 ·

Re: native gcc compiler error

If I add the link by hand the issues goes away. - K

By Kumar Gala <galak@...> · #1964 ·

Re: native gcc compiler error

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.

By Khem Raj · #1963 ·

Re: native gcc compiler error

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",

By Kumar Gala <galak@...> · #1962 ·

Re: native gcc compiler error

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

By Saul Wold <sgw@...> · #1961 ·

Re: native gcc compiler error

Does strace show where its looking for it? Cheers, Richard

By Richard Purdie · #1960 ·

EXTRA_IMAGE_FEATURES question

I was trying a core-image-minimal build with 'tools-sdk' added to EXTRA_IMAGE_FEATURES and was expecting a native gcc in the generated rootfs. This was for mpc8315e-rdb config. conf/local.conf

By Kumar Gala <galak@...> · #1959 ·

Re: native gcc compiler error

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

By Kumar Gala <galak@...> · #1958 ·

Re: native gcc compiler error

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.

By Khem Raj · #1957 ·

native gcc compiler error

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

By Kumar Gala <galak@...> · #1956 ·

Yocto weekly bug trend charts -- WW29

Hi all, Last week QA finished testing for M2 RC2. The new-submit vs. fixed bug is 20 vs. 10 for last week. The open bug number increased to 182 (No enhancement bugs counted). WDD number increased a

By Xu, Jiajun <jiajun.xu@...> · #1955 ·

Re: yocto build fails

I had blown the tarball away yesterday working on bug #1207. The rsync should have run by now to pull it back up but for some reason, hasn't. I'll look at this on Monday but in the meantime, i've

By Flanagan, Elizabeth <elizabeth.flanagan@...> · #1954 ·

Re: yocto build fails

<snip> This would lead me to make a guess at your proxy settings not being configured correctly for git with nc. Looks like we have a bad mirrored tarball. :-/ Cheers, Joshua -- Joshua Lock

By Joshua Lock <josh@...> · #1953 ·

Re: last observations about quick start guide, then moving on

Robert, These are handled. Thanks again. ScottR

By Rifenbark, Scott M <scott.m.rifenbark@...> · #1952 ·

Re: [PATCH] DOCS: Correct format of command continuation.

Fixed. Thanks Robert.

By Rifenbark, Scott M <scott.m.rifenbark@...> · #1951 ·

Messages