full rebuild and errors:
Hello,
I successfully compiled buildroot for Raspberry Pi following this guide:
https://github.com/albertd/buildroot-rpi
I had a problem with some applications (btw it was: EGL Error : Could not create the egl surface: error = 0x300b) and I read some users were able to solve just rebuilding buildroot.
Thus, I issued:
make cleanall
as stated in the documentation. But this time I get the following errors:
/home/mark/dev/buildroot-rpi/output/host/usr/bin/ccache /usr/bin/gcc
-std=gnu99 -O2 -I/home/mark/dev/buildroot-rpi/output/host/usr/include
-L/home/mark/dev/buildroot-rpi/output/host/lib -L/home/mark/dev/buildroot-rpi/output/host/usr/lib -Wl,-rpath,/home/mark/dev/buildroot-rpi/output/host/usr/lib -o m4 m4.o builtin.o debug.o eval.o format.o freeze.o input.o macro.o output.o path.o symtab.o ../lib/libm4.a
m4.o: In function `main':
m4.c:(.text.startup+0x260): undefined reference to version_etc' m4.c:(.text.startup+0x3ef): undefined reference to emit_bug_reporting_address'
collect2: error: ld returned 1 exit status
make[3]: *** [m4] Error 1
make[3]: Leaving directory `/home/mark/dev/buildroot-rpi/output/build/host-m4-1.4.16/src' make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/mark/dev/buildroot-rpi/output/build/host-m4-1.4.16' make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/mark/dev/buildroot-rpi/output/build/host-m4-1.4.16'
make: *** [/home/mark/dev/buildroot-rpi/output/build/host-m4-1.4.16/.stamp_built] Error 2
Google doesn't help me on this.
Do you have any idea why this happens?
Thanks
Mark
Dear Marco Trapanese,
Quoted 7 lines · Marco Trapanese
I successfully compiled buildroot for Raspberry Pi following this guide:
https://github.com/albertd/buildroot-rpi
I had a problem with some applications (btw it was: EGL Error : Could not create the egl surface: error =
0x300b) and I read some users were able to solve just rebuilding buildroot.
The version of Buildroot you've used is a derivate of the official Buildroot version. So there is no way we can really help you on this. You should either use the official Buildroot version (and ask the people who forked Buildroot to contribute their changes back to the official version), or ask for support from the authors of the derivative version.
If you can reproduce this problem with the official Buildroot, then we can certainly look into it and help fixing the issue.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Il 27/01/2014 07:34, Thomas Petazzoni ha scritto:
Quoted 8 lines
The version of Buildroot you've used is a derivate of the official Buildroot version. So there is no way we can really help you on this. You should either use the official Buildroot version (and ask the people who forked Buildroot to contribute their changes back to the official version), or ask for support from the authors of the derivative version. If you can reproduce this problem with the official Buildroot, then we can certainly look into it and help fixing the issue. Best regards, Thomas
I understand this, but I'm just asking if you know any cause which may lead to the behavior described.
I did nothing but download - make - clean - make (or even download again from repository).
My question is not related to the specific buildroot fork, but about the general use of it.
Anyway i thank you for your support
Mark