On Sun, 16 Mar 2008, Florian Fainelli wrote:
> Hi Robert,
>
> Le dimanche 16 mars 2008, Robert P. J. Day a écrit :
> > so there you have it -- the actual commands live in
> > /usr/libexec/sdcc. so, how does one deal with this? should i
> > just arrange to extend my openwrt build search path with
> > /usr/libexec/sdcc? or should i patch the Makefile(s) of any
> > package that needs sdcc to be a little more flexible and be
> > prepared to look elsewhere? what's the correct approach here?
> > thanks.
>
> Since Fedora uses, say non-standard ways of packaging sdcc. I would
> suggest extending the existing RequireCommand macro to check for
> additionnal sdcc commands.
but that's not really going to solve the problem on a project-wide
level, is it? in cases like this, it seems that there should be some
kind of mechanism to specify an alternate search directory for openwrt
for commands that it requires.
in the case of fedora, there *is* an "sdcc" command -- it's just in
the wrong place. so how easy would it be to take that possibility
into account? i'd rather do that than start accommodating the usage
of "sdcc-sdcc".
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================_______________________________________________
openwrt-devel mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
