Hi, Stafford Horne wrote, > On Tue, Aug 27, 2019 at 09:37:32PM +0200, Romain Naour wrote: > > Hi Stafford, > > > > Le 26/08/2019 à 22:58, Stafford Horne a écrit : > > > This symbol was causing a build failure with the new toolchain. It > > > looks like it has always been wrong. > > > > > > The main issue was checking for PIC rather than __PIC__. > > > > Indeed, I also noticed this. > > I've made a similar/simpler patch but the system doesn't boot (init program > > is > > stuck after "Run /init as init process") > > > > Sadly, the system doesn't boot even with your patch. > > Have you successfully runtime tested uClibc-ng build with your patch? > > > > Hello, > > No, I haven't got it booting. > > I have only been able to successfully compile using this. I don't have an > environment setup right now to boot a uclibc-ng target. What are you using > qemu, or1ksim, fpga? > > In terms of possible issues, I did just fix 2 bugs that caused glibc to not > build: > - gcc bug - could not read GOT due to clobbering r9 > https://gcc.gnu.org/ml/gcc-patches/2019-08/msg01549.html > - binutils bug - issue with PLT entries and lazy symbol resolution > (Already upstream) > https://sourceware.org/ml/binutils/2019-08/msg00214.html Patch applied and pushed. With the binutils/gcc patch the system boots fine in Qemu. The testsuite does show also good results, just 6-7 test failures.
best regards Waldemar _______________________________________________ devel mailing list [email protected] https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel
