Hi Andrew, On 15/12/15 02:11, Andrew Cagney wrote: > On 13 December 2015 at 20:35, Greg Ungerer <g...@uclinux.org> wrote: >> On 12/12/15 03:03, Andrew Cagney wrote: >>> I came up with the attached. The existing libgmp configuration in >>> lib/Kconfig would need removing. >> >> Just a heads up... But some other targets in the tree that >> currently have libgmp enabled no longer compile with this >> in place. >> >> For example building an ARM target fails at: >> >> ... >> Executing: /bin/sh -c 'ucfront-gcc' 'arm-linux-gnueabi-20150104-gcc' >> '-std=gnu99' '-DHAVE_CONFIG_H' '-I.' '-D__GMP_WITHIN_GMP' '-O1' '-pipe' >> '-fno-common' '-fno-builtin' '-Wall' '-Dlinux' '-D__linux__' '-Dunix' >> '-DEMBED' '-c' 'tal-reent.c' '-fPIC' '-o' 'tal-reent.o' >> Executing: touch tal-reent.lo >> make[5]: *** No rule to make target `mpn/add_n.lo', needed by `libgmp.la'. >> Stop. >> make[5]: Leaving directory >> `/home/gerg/uclinux-dist.foo/lib/libgmp/build/gmp-6.1.0' >> make[4]: *** [all-recursive] Error 1 > > What happens if you point the URL at 5.x series, for instance: > https://gmplib.org/download/gmp/gmp-5.1.3.tar.xz
Same result. Fails to build with same error. > This thread: > http://stackoverflow.com/a/16726435/1357163 > lead me to this patch: > https://gmplib.org/repo/gmp-5.1/rev/2347fd4901ad > which I don't seem to be able to find in 6.x's ChangeLog. The problem doesn't appear to be ARM specific. I tried a compile of an x86_64 target and it failed in a similar way: make[5]: *** No rule to make target `mpn/invert_limb_table.lo', needed by `libgmp.la'. Stop. Regards Greg > (and of course, just my luck that --disable-assembly was only added in 6.x) > > >> Regards >> Greg >> >> >> >>> On 9 December 2015 at 17:35, David McCullough <ucde...@gmail.com> wrote: >>>> >>>> Andrew Cagney wrote the following: >>>>> On 8 December 2015 at 07:03, Greg Ungerer <g...@uclinux.org> wrote: >>>>>> Hi Andrew, >>>>>> >>>>>> On 08/12/15 04:23, Andrew Cagney wrote: >>>>>>> >>>>>>> The libgmp bundled with uClinux, by default, doesn't build for the >>>>>>> M5208 - the m68k assembler uses instructions dropped from early >>>>>>> Coldfires. >>>>>>> The hack I'm using locally is to configure with --host=none (I got >>>>>>> this trick second hand from somewhere). >>>>>>> >>>>>>> Anyway I noticed that libgmp is, er, a little out-of-date. The latest >>>>>>> version has --disable-assembly which looks to be a cleaner way to >>>>>>> handle the assembler problem. >>>>>>> (How to decide when to configure with that option is an open question, >>>>>>> a Kconfig option). >>>>>>> >>>>>>> As anyone looked at updating this; or to turn the question round, is >>>>>>> there anything needed in the existing version that would prevent this? >>>>>> >>>>>> >>>>>> Nothing stopping updating as far as I know. >>>>>> >>>>>> Can I suggest that if you do decide to update it that you convert >>>>>> it to automake building. >>>>> >>>>> Yes, that's the plan. I've noticed that the framework's improved >>>>> significantly over the years and I've been able to drop some of my >>>>> local hacks. >>>>> >>>>>> The trend over the last couple of years >>>>>> is that if we are updating a package then convert it. There >>>>>> are quite a few examples to follow in the lib directory. Just >>>>>> look for directories that contain a "makefile" and optionally a >>>>>> patches directory and not much else. >>>>> >>>>> Any pointers for how to handle --disable-assembly configure option? >>>>> For instance, since libreswan requires libgmp, it would have: >>>>> select LIB_LIBGMP >>>>> but libreswan doesn't know if --disable-assembly is required, that >>>>> would be set by a vendor/platform files? >>>> >>>> Yep, make that part of the libgmp setup. If you switch to automake you >>>> can add that option to a Kconfig in the libgmp directory, again, there >>>> are quite a few examples in the tree. some have their own Kconfig files: >>>> >>>> grep -l automake lib/*/makefile user/*/makefile >>>> >>>> ls lib/*/Kconfig user/*/Kconfig >>>> >>>> to find them all. >>>> >>>> Cheers, >>>> Davidm >>>> >>>> -- >>>> David McCullough, dav...@spottygum.com, Ph: 0410 560 763 >>>> _______________________________________________ >>>> uClinux-dev mailing list >>>> uClinux-dev@uclinux.org >>>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev >>>> This message was resent by uclinux-dev@uclinux.org >>>> To unsubscribe see: >>>> http://mailman.uclinux.org/mailman/options/uclinux-dev >>>> >>>> >>>> _______________________________________________ >>>> uClinux-dev mailing list >>>> uClinux-dev@uclinux.org >>>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev >>>> This message was resent by uclinux-dev@uclinux.org >>>> To unsubscribe see: >>>> http://mailman.uclinux.org/mailman/options/uclinux-dev >> >> _______________________________________________ >> uClinux-dev mailing list >> uClinux-dev@uclinux.org >> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev >> This message was resent by uclinux-dev@uclinux.org >> To unsubscribe see: >> http://mailman.uclinux.org/mailman/options/uclinux-dev > _______________________________________________ > uClinux-dev mailing list > uClinux-dev@uclinux.org > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by uclinux-dev@uclinux.org > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
