13 replies to this topic

[christophecvr]

Hello I tried to buildimage 2.21 on freshly installed 11.10.

But build faild included here the log

ERROR: Logfile of failure stored in: /home/christophe/openpli/build-dm8000/tmp/work/mipsel-oe-linux/python-2.6.6-ml12.3/temp/log.do_install.31265
Log data follows:

see log file attached  logdo_install31265.txt   26.35KB   13 downloads

NOTE: package python-2.6.6-ml12.3: task do_install: Failed
ERROR: Function 'do_install' failed (see /home/christophe/openpli/build-dm8000/tmp/work/mipsel-oe-linux/python-2.6.6-ml12.3/temp/log.do_install.31265 for further information)
ERROR: Task 583 (/home/christophe/openpli/openembedded/recipes/python/python_2.6.6.bb, do_install) failed with exit code '1'
ERROR: '/home/christophe/openpli/openembedded/recipes/python/python_2.6.6.bb' failed
make: *** [image] Fout 1

[christophecvr]

OK I found out the problem, I will also ad solution to quick setup of ubuntu.

Ubuntu installs at base python 2.7 but not 2.6.

For that reason somehow it tried to use lib32 files. Why ??? I don't know .

I just installed extra python 2.6 and lib python 2.6 and it did run .

Now there is just A new problem since ppanel is missing. Whic causes rootfs to fail. This problem is not 11.10 related as it did showed up when I updated my previous images which is on ubuntu 11.04.

I made topic of that problem.

[macnuts]

Thank for the tip , I had the same problem but had no time (and experience) to solve it. See http://openpli.org/f...tu-1110-x86-64/. I could only confirm that it also happens on Ubuntu 11.10 32 bit (errors in log are somwhat different: instead of "wrong ELF class" I got "missing").

BUT, are you sure that installing libpython2.6 solved the problem? It did not for me. Have you rebuild package python-2.6.6-ml12.3 entirely or just made image again after installing libpython2.6?
I am asking this as for me (before installing libpython2.6) I had the error on first fresh build but on rebuild I got no error at all - but the task log contained the errors about wrong ELF class.

And now, after installing the libpython2.6, the fresh build still fails.

Regards.

[christophecvr]

Thank for the tip , I had the same problem but had no time (and experience) to solve it. See http://openpli.org/f...tu-1110-x86-64/. I could only confirm that it also happens on Ubuntu 11.10 32 bit (errors in log are somwhat different: instead of "wrong ELF class" I got "missing").

BUT, are you sure that installing libpython2.6 solved the problem? It did not for me. Have you rebuild package python-2.6.6-ml12.3 entirely or just made image again after installing libpython2.6?
I am asking this as for me (before installing libpython2.6) I had the error on first fresh build but on rebuild I got no error at all - but the task log contained the errors about wrong ELF class.

And now, after installing the libpython2.6, the fresh build still fails.

Regards.

Hello , I did several rebuilds before adding the libpython2.6 . It always showed same problem. Only after installing libpython2.6 it went fine.

But as You work with i386, You need to install : libpython2.6:64 (or something like that use synaptic to find out) I think. I can't test it as I only run x86_64

Edited by christophecvr, 30 October 2011 - 17:43.

[macnuts]

I switched back to x86_64 to test your solution . And x86_64 is much faster for me (build on i386 failed as well so using it was no solution at all).

I am rebuilding the OpenPli right now (fresh, no folders except sources) after having installed the python2.6-dev, it may help maybe.

BTW, to get the latest Makefile i use the command:

wget http://openpli.svn.sourceforge.net/viewvc/openpli/trunk/pli-oe/Makefile-2.1 -O ~/openpli-test/Makefile-2.1

Is it correct? I know that the howto states differently but the trunk has been updated to 2.1.

[christophecvr]

I switched back to x86_64 to test your solution . And x86_64 is much faster for me (build on i386 failed as well so using it was no solution at all).

I am rebuilding the OpenPli right now (fresh, no folders except sources) after having installed the python2.6-dev, it may help maybe.

BTW, to get the latest Makefile i use the command:

wget http://openpli.svn.sourceforge.net/viewvc/openpli/trunk/pli-oe/Makefile-2.1 -O ~/openpli-test/Makefile-2.1

Is it correct? I know that the howto states differently but the trunk has been updated to 2.1.

Hello I as well just starts a new test. It's wel on an older pc. So it will take some time to build.

The make file you use I don't now yet,

But if you use the one into my quicksetup document You will have as well the latest change corrected for the ppanel error

link same as in my document :

http://users.telenet...file-2.1.tar.gz

[christophecvr]

Unfortunately with new build same problem concerning python. The second time it worked out. So at the end seems not to be libpython2.6

[macnuts]

Unfortunately with new build same problem concerning python. The second time it worked out. So at the end seems not to be libpython2.6

Please check the logs after second build.

In my case I can see one log.do_compile (from first build) and this one contains failure notifications (look up 'failed').
There are two log.do_install but the one, of the second build has the same warnings and failure notifications.

I do not know if those errors are vital in image building but for me some of the 'renamed' items looks very generic (like '_struct'). I am not sure if the output is runnable - I am scared to test the "second-run-succeded" image.

[christophecvr]

Unfortunately with new build same problem concerning python. The second time it worked out. So at the end seems not to be libpython2.6

Please check the logs after second build.

In my case I can see one log.do_compile (from first build) and this one contains failure notifications (look up 'failed').
There are two log.do_install but the one, of the second build has the same warnings and failure notifications.

I do not know if those errors are vital in image building but for me some of the 'renamed' items looks very generic (like '_struct'). I am not sure if the output is runnable - I am scared to test the "second-run-succeded" image.

The second build does has error free install log. Only in compile log a couple of modules are not build, Think they do not harm. But this has nothing to do with the previous ELF error.

I do have only one remaining install log, That from second build.

[christophecvr]

I now also did a fresh compile on 11.04 ubuntu. It did compiled OK. 02 Hr 5 min. However when You check the installog of python in mipsel-oe-linux/python-2.6.6-ml12.3/temp, It does contain the ELF errors. Binnary's are build anyway. That image does work good as well. (tested)

The build from 11.10 There as well indeed two logs. The first from unsuccessful compilation. the second compilation was ok binary's are build. The log is identical to that from the build in 11.04 and does contain the ELF errors just like the build with 11.04 pc.
The resulting image is not tested yet, But I guess it will be ok.

[macnuts]

You are one step ahead of me .
I am now in the process of restoring ubuntu 11.04 to do the same test (to compare logs). I will continue as the restore operation is almost finished.

It looks like the "two-phase" build on ubuntu 11.10 produces good image, I agree with you (as ELF errors are present on both ubuntu platforms). And this was my main concern.

Thank you for your support.

[christophecvr]

Hello, For me it's easy as a do have two pc's. each three two 4 years a build a new pc. Then the one I had becomes my backup and test pc, The new one my main working pc.

I installed the new 11.10 on my old (now test pc amd X2 2gb ram) . But spend a lot of time to understand the new gnome3 stuff. Unity is unusable for me or let say to much restricted in possibilities . Gnome shell much better. I well had to learn the use of it It's a bit like being faced to a whole new distro. At start it's always a pain in the ass. With a lot of tweaking, it becomes usable . And after all not that bad as I initially found. I still needs to get really used to this new desktop (shell) old habits are difficult to unlearn.

I did further research on subjects, Think I have found the solution. 11.10 does use at base the new gcc 4.6 , this gcc is full of new by default enabled warnings. Since finally this project uses mainly older gcc versions to cross compile, its not a problem to assign when working with bitbake gcc-4.4 and g++-4.4 by default. Now i think a couple of problems are coming because the openpli crosscompiler gcc for croscompiling on the specified box you are using, is compiled with systems standard gcc compiler on 11.10 that is gcc 4.6 .

I'm now just started a new fresh build, i changed the make file line 32 : added --compiler=/usr/bin/gcc-4.4

line orig =

bitbake:
$(GIT) clone -b $(BITBAKE_BRANCH) git://git.openembedded.org/bitbake
cd bitbake && ( \
  python setup.py build ;\
)

changed in

bitbake:
$(GIT) clone -b $(BITBAKE_BRANCH) git://git.openembedded.org/bitbake
cd bitbake && ( \
  python setup.py build --compiler=/usr/bin/gcc-4.4  ;\
)

I don't now if this will work out, I erased all (except sources) and restart from scratch with first

make -f Makefile-2.1

and when git is in

make -f Makefile-2.1 image

Hope that first build error will be gone.

Edited by christophecvr, 1 November 2011 - 14:04.

[christophecvr]

Unfortunately this did not solve the problem.

I even tried a compilation, Where I just changed the systems default compiler from gcc-4.6 to gcc-4.4 by changing the gcc link from linked to gcc-4.6 to gcc-4.4 as well for the g++ from linked to g++-4.6 to g++-4.4

It still failed on first fresh compilation due to python binaries not being build.

[christophecvr]

Hello I tried a lot , whatever I do The build always fails the first time. I just have to do ~/openpli $ make -f Makefile-2.1 image A second time then it builds.

The first time it will fail pointing to log file log.do_install.18362 . There are no other install logs present. The second time it builds, When checking I'll find a second log install file named :
log.do_install.16323

I now just thinks that it is somehow related to the moment it tries to install not having all needed files avbl yet.

Is there not a way to modify the sequence so that this installs does occur later during build from a full fresh image ??

With this mail I attached three log files. One is the compilation log, The log.do_install ok and not ok. That with the highest number was the failed from first build attempt.

p.s. Note I wroted at start kernel 3.0.3 But actually its' kernel 3.0.0

Attached Files

•  log.do_compile.30594.txt   201.44KB   2 downloads
•  log.do_install.18362.txt   26.5KB   3 downloads
•  log.do_install.16323.txt   582.38KB   2 downloads