On 2014-10-08 21:05, Robert P. J. Day wrote:
> On Wed, 8 Oct 2014, Felix Fietkau wrote:
>
>> On 2014-10-08 20:44, Robert P. J. Day wrote:
>> > On Wed, 8 Oct 2014, Felix Fietkau wrote:
>> >
>> >> On 2014-10-08 19:51, Robert P. J. Day wrote:
>> >> >
>> >> > tried a "make V=s DUMP=1" and encountered precisely this bug:
>> >> >
>> >> > https://dev.openwrt.org/ticket/14697
>> >> >
>> >> > this is on a fully-updated, fedora rawhide system for which all my
>> >> > non-DUMP openwrt makes have been working pretty well so far.
>> >
>> >> This is not a bug - overriding a random internal build system
>> >> variable on the command line isn't exactly a good idea. :) Where did
>> >> you get the idea of putting DUMP=1 on the command line?
>> >
>> > it's mentioned in the old kamikaze documentation here:
>> >
>> > https://downloads.openwrt.org/kamikaze/docs/openwrt.html#x1-490002.1.5
>> >
>> > and an admittedly ancient openwrt users mailing list post here:
>> >
>> > https://lists.openwrt.org/pipermail/openwrt-users/2008-May/000316.html
>
>> Ah okay, so you just took a small part of that command without
>> checking the context. By the way, if you use the DUMP=1 command as
>> described in that old document, it still works.
>
> fair enough ... it's just not clear from that doc what part of the
> context is actually *required*.
It's a specific command for a specific use (checking why a particular
package does not show up in menuconfig), not something that's in any way
meant to be run globally.
It says:
If you find your package doesn’t show up in menuconfig, try the
following command to see if you get the correct description:
TOPDIR=$PWD make -C package/<name> DUMP=1 V=99
Which part of this is unclear, and how could we change the wording to
make it more clear?
- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
