Jow, > Yes, patch scripts/config.sub - that is whats fored upon each package.
Yikes!!! Thanks a billion!!! I've been caught in this trap for half a day. Packages were built flawlessly. >> Is the behavior of "Modifying a generic build tool during a build >> process for a single target" considered legitimate? > > Modifying the generic build tool to accept a new platform is certainly > legitimate, nobody wants to patch a new CPU definition into each single > package. Ah, then, automake's config.sub should be patched once when it is built? :-) (There's no argument, just my personal thoughts.) --- shinoda On 2012/01/23, at 3:33, Jo-Philipp Wich wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi. > > >> I need a same kind of magic to overcome this problem. >> Is there any? > > Yes, patch scripts/config.sub - that is whats fored upon each package. > >> Is the behavior of "Modifying a generic build tool during a build >> process for a single target" considered legitimate? > > Modifying the generic build tool to accept a new platform is certainly > legitimate, nobody wants to patch a new CPU definition into each single > package. > >> Wouldn't it introduce some unexpected side effects? > > Its autohell so nobody can tell :) > > > ~ Jow > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk8cVnkACgkQdputYINPTPOmHQCeK+HDFGdXAfX8QjM4trm9B1uM > RDoAoIB1Gu3rRoaRs3OVkviYxsET6qLx > =7I17 > -----END PGP SIGNATURE----- > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
