I was the person who asked this question last august. We were compiling for Linux 3.2.17 using gcc 4.7.1 on a Ubuntu 12.04 Host. The problem appeared if I tried to turn debugging on from the make menuconfig. However, I was able to circumvent the problem by using -ggdb and making sure " # DOSTRIP is not set" in .config file. After this we were able to use the debugger .
Please let me know if you need more details and I can provide you. > -----Original Message----- > From: Sedat Dilek [mailto:sedat.di...@gmail.com] > Sent: Friday, March 08, 2013 9:47 AM > To: Alexey Zaytsev > Cc: Dubey, Abhishek; uclibc@uclibc.org > Subject: Re: uclibc 3.3.2 with gcc-4.7 > > On Fri, Mar 8, 2013 at 4:39 PM, Alexey Zaytsev <alexey.zayt...@gmail.com> > wrote: > > On Fri, Mar 8, 2013 at 4:33 PM, Sedat Dilek <sedat.di...@gmail.com> > wrote: > >> On Mon, Aug 27, 2012 at 8:17 PM, Dubey, Abhishek > >> <abhishek.du...@vanderbilt.edu> wrote: > >>> Building uclibc 3.3.2 with debugging and NPTL using the gcc 4.7.1 > compiler leads to the following unresolved symbols. > >>> > >>> libc/libc_so.a(lockf.os): In function `__GI_lockf': > >>> /home/f6/F6Dev/f6utils/IM/uClibc-0.9.33.2/libc/misc/file/lockf.c:73: > undefined reference to `_Unwind_Resume' > >>> > libc/libc_so.a(lockf.os):(.data.DW.ref.__gcc_personality_v0[DW.ref.__gcc_p > ersonality_v0]+0x0): undefined reference to `__gcc_personality_v0' > >>> collect2: error: ld returned 1 exit status > >>> make: *** [lib/libc.so] Error 1 > >>> > >>> Any suggestions on what is the cause of the problem. Has anyone else > faced this before? > >>> > >> > >> Hi, > >> > >> you forgot to give some useful details... like your uclibc-config or > >> infos to your build-environment. > >> What is your host/target arch? > >> > >> Why do you use gcc-4.7.1 when there is v4.7.2? > > > > You are replying to a message that was sent in August 2012 - gcc 4.7.2 > > was not released until September. > > > > I'm using 4.7.2, and the problem is still there. I'll try to reproduce > > with current uclibc and updated buildroot. > > > > Accidently, I replied to the initial email. > But, anyway, the people gave too less informations. > And vanilla toolchain IIRC will not work OOTB. > If you are on MIPS(el) you can have look at target-toolchain patches from > Freetz project or OpenWrt is also a good address. > > - Sedat - > > [1] http://freetz.org/browser/trunk/toolchain/make/target > [2] > http://git.mirror.nanl.de/?p=openwrt/trunk.git;a=tree;f=toolchain;hb=HEAD > > >> > >> I would recommend you in case of uclibc to see if the problems still > >> exist with 0.9.33 GIT branch [1]. > >> Bernhard said there will be soon a v0.9.33.3 release. > >> > >> Also, have a look at gcc-4.7.x and uclibc-0.9.33.x patches of > >> buildroot/openembedded/openwrt (or even Freetz) projects. > >> > >> Have fun! > >> > >> Regards, > >> - Sedat - > >> > >> [1] http://git.busybox.net/uClibc/log/?h=0.9.33 > >> > >>> Regards > >>> Abhishek > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> uClibc mailing list > >>> uClibc@uclibc.org > >>> http://lists.busybox.net/mailman/listinfo/uclibc > >> _______________________________________________ > >> uClibc mailing list > >> uClibc@uclibc.org > >> http://lists.busybox.net/mailman/listinfo/uclibc _______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
