Hi, okay, that was already the next test armv5-nommu-arm, which OpenADK needs to learn, as the default is fdpic now.
Will you sent a complete patch with sob for the previous error? best regards Waldemar > Am 19.07.2018 um 18:31 schrieb Christophe Lyon <[email protected]>: > > On Thu, 19 Jul 2018 at 14:33, Waldemar Brodkorb > <[email protected]> wrote: >> >> Hi, >> Christophe Lyon wrote, >> >>>> On Wed, 18 Jul 2018 at 18:37, Waldemar Brodkorb <[email protected]> wrote: >>>> >>>> Hi, >>>> Christophe Lyon wrote, >>>> >>>>>> On Wed, 18 Jul 2018 at 09:37, Waldemar Brodkorb <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi Christophe, >>>>>> Waldemar Brodkorb wrote, >>>>>> >>>>>>> Hi Christophe, >>>>>>> >>>>>>> i am doing a large testrun for the global changes and hopefully push on >>>>>>> monday or at least have some news. i am afk atm with just little access >>>>>>> to a computer. >>>>>>> >>>>>> >>>>>> ARM v5 soft eabi arm mode fails to compile, see the attached error >>>>>> log. You can check with embedded-test.sh if you like. >>>>>> >>>>>> Any idea? All patches appliend on top of master, >>>>> >>>>> Thanks for testing this configuration. >>>>> >>>>> I left FDPIC-only code activated unconditionally. >>>>> >>>>> Can you try the attached small patch? >>>> >>>> Even fixing this small typo in #endf it errors out. >>>> >>> OK, here is an updated version of the previous patch. >> >> Works for the ldso, but I think we need a symbol to differentiate >> between ELF and FDPIC. >> See attached error. > > Strange, the build succeeded for me. I don't understand where this > -mfdpic option comes from? > It is not part of the patches I sent, unless I'm mistaken: it would be > "embedded" in GCC if configured for FDPIC, which is not the case in > this build for armv5. > > >> >>>>> I have an embedded-test.sh build running now. Sorry, I didn't know >>>>> about this script, I have used armv5 as arch, is it the one you meant? >>>> >>>> somthing like this, uclibc-ng is a directory including all patches: >>>> mksh embedded-test.sh --libc=uclibc-ng --libc-source=uclibc-ng >>>> --arch=armv5 --verbose >>> >>> Is there a way to avoid (re)creating all the source tarballs? It's taking >>> ages >> >> It only recreates uclibc-ng tarball. (or any git ones). > OK... I use git trees for binutils, gcc and linux ;( > >> You can do on a failure: >> cd openadk >> make v >> >> best regards >> Waldemar > _______________________________________________ devel mailing list [email protected] https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel
