Hello,
I'm trying to add a new processor type (lexra), but having
trouble patching the config.sub, that checks for recognizable
cpu-os-kernel identifier, used in some packages.
More specifically, I want the config.sub in iptables-1.4.10 to
recognize the 'lexra-openwrt-linux'.
I'm working on the trunk r29839.
In the first place, I thought I can do this as a piece of cake
by adding a patch file that adds couple of lines to the config.sub,
in ${BUILDROOT}/package/iptables/patches.
Then, after few attempts, I found out that the autoreconf or a similar
mechanism replaces
${BUILDROOT}/build_dir/${TARGETSPEC}/iptables-1.4.10/config.sub
during the build process so that it points (symlinks) to
${BUILDROOT}/staging_dir/host/share/automake-1.11/config.sub.
At this point, I turned around and added a similar patch to
${BUILDROOT}/tools/automake/patches.
I checked my result immediately after the automake build,
and confirmed that the config.sub was patched appropriately.
But, ...the next "make V=99" only revealed that the
${BUILDROOT}/staging_dir/host/share/automake-1.11/config.sub
was magically overwritten to the original unpatched state.
Here's my question:
I'm not an expert on OpenWrt build system, and therefore
I believe this is some kind of magic, and I also believe that
I need a same kind of magic to overcome this problem.
Is there any?
Thanks in advance,
--- shinoda
P.S.
Here's some discussion:
Is the behavior of "Modifying a generic build tool during a build
process for a single target" considered legitimate?
Wouldn't it introduce some unexpected side effects?
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
