On Thu, Oct 11, 2018, 6:16 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote:
> Hello, > > it is always a pleasure to work on Windows via msys2. After my recent > Makefile.am changes the argument list to create the library is too long: > > in_cpuinfo.o libmisc/shell/main_profreport.o libmisc/utf8proc/utf8proc.o > libmd/sha256c.o libmd/sha512c.o score/cpu/no_cpu/cpuidle.o > score/cpu/powerpc/cpu.o score/cpu/powerpc/ppc-context-volatile-clobber.o > score/cpu/powerpc/ppc-context-validate.o > score/cpu/powerpc/ppc-isr-disable-mask.o > score/cpu/powerpc/ppc-isr-vector-install.o > make[4]: execvp: powerpc-rtems5-ar: Argument list too long > Since we would like to eventually move the legacy Network stack to another package entirely, would simply letting it and pppd be their in Makefile,am and separate library installed help. Eventually we may hit the limit again but we may be at waf by then. > > Some time ago we had the same problem with libbsd and got a fix for waf > due to that. What works is this manual hack: > > librtemscpu.a: $(librtemscpu_a_OBJECTS) $(librtemscpu_a_DEPENDENCIES) > $(EXTRA_librtemscpu_a_DEPENDENCIES) > -rm -f librtemscpu.a > echo "" > librtemscpu.txt > for i in $(librtemscpu_a_OBJECTS) ; do $$i >>librtemscpu.txt ; > done > $(librtemscpu_a_AR) librtemscpu.a @librtemscpu.txt > $(librtemscpu_a_LIBADD) > $(RANLIB) librtemscpu.a > > The standard Automake target is this: > > librtemscpu.a: $(librtemscpu_a_OBJECTS) $(librtemscpu_a_DEPENDENCIES) > $(EXTRA_librtemscpu_a_DEPENDENCIES) > -rm -f librtemscpu.a > $(librtemscpu_a_AR) librtemscpu.a $(librtemscpu_a_OBJECTS) > $(librtemscpu_a_LIBADD) > $(RANLIB) librtemscpu.a > > Is it possible to override a Automake generated target with a custom > variant? > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
