[SOLVED] buildroot problem rasbery: hidden symbol `_fpioconst_pow10' isn't defined
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
buildroot problem rasbery: hidden symbol `_fpioconst_pow10' isn't defined
I would like to make an image for rasbery with buildroot. I configures it with manuconfig and ran make , everything goes fine until here that I got error:
find_exidx.c.text+0xbce28): undefined reference to `__GI_strtol'
/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build/libc_pic.os: In function `__ptsname_internal':
find_exidx.c.text+0xbd22c): undefined reference to `_itoa_word'
/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build/libc_pic.os: In function `ext_wmatch':
find_exidx.c.text.unlikely+0x274): undefined reference to `__GI_getenv'
/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build/libc_pic.os: In function `ext_match':
find_exidx.c.text.unlikely+0x9a0): undefined reference to `__GI_getenv'
/home/ehsand/saedteach/buildroot-2013.11/output/host/usr/lib/gcc/arm-buildroot-linux-gnueabi/4.8.2/../../../../arm-buildroot-linux-gnueabi/bin/ld: /home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build/libc.so: hidden symbol `_fpioconst_pow10' isn't defined
/home/ehsand/saedteach/buildroot-2013.11/output/host/usr/lib/gcc/arm-buildroot-linux-gnueabi/4.8.2/../../../../arm-buildroot-linux-gnueabi/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make: *** [/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build/libc.so] Error 1
make: Leaving directory `/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/libc/elf'
make: *** [elf/subdir_lib] Error 2
make: Leaving directory `/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/libc'
make: *** [all] Error 2
make: Leaving directory `/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/build'
make: *** [/home/ehsand/saedteach/buildroot-2013.11/output/build/glibc-2.17-svnr22064/.stamp_built] Error 2
my system info is as follow:
Linux ehsand-pc 3.10.2 #3 SMP Wed Jan 15 10:59:08 IRST 2014 x86_64 x86_64 x86_64 GNU/Linux
what is your buildroot version? I always got random errors with a buildroot 2011 version, which just disappeared with the latest version, so i can hardly recommend to upgrade, if you are not set to that particular version.
have you tryed rebuilding from scratch? If not this can cause many (misleading) errors. To be sure, it's better to "make clean" when you change some items in buildroot.