in a nutshell, trying to build firmwarehotplug on a fedora system is
doomed to failure since, even if the fedora "sdcc" package is
installed, it doesn't provide specifically an "sdcc" command, as
firmwarehotplug requires:

  $(eval $(call BuildPackage,firmwarehotplug))

  $(eval $(call RequireCommand,sdcc, \
        $(PKG_NAME) requires the SDCC Cross Compiler (sdcc). \
  ))

  the reason is that there is (apparently) a fedora package conflict
between sdcc and something else (i don't know what), so what the
fedora sdcc package *does* provide is:

$ ls -1 /usr/bin/sdcc*
/usr/bin/sdcc-as-gbz80
/usr/bin/sdcc-as-hc08
/usr/bin/sdcc-aslink
/usr/bin/sdcc-asx8051
/usr/bin/sdcc-as-z80
/usr/bin/sdcc-link-gbz80
/usr/bin/sdcc-link-hc08
/usr/bin/sdcc-link-z80
/usr/bin/sdcc-makebin
/usr/bin/sdcc-packihx
/usr/bin/sdcc-s51
/usr/bin/sdcc-savr
/usr/bin/sdcc-sdcc
/usr/bin/sdcc-sdcclib
/usr/bin/sdcc-sdcdb
/usr/bin/sdcc-sdcpp
/usr/bin/sdcc-shc08
/usr/bin/sdcc-sz80
$

where the "sdcc-" prefixes were added to (obviously) avoid the
conflict.  however, each of the above is nothing more than a wrapper
as in:

$ cat /usr/bin/sdcc-sdcc
#!/bin/sh
PATH=/usr/libexec/sdcc:$PATH
/usr/libexec/sdcc/sdcc "$@"
$

where:

$ ls -1 /usr/libexec/sdcc
as-gbz80
as-hc08
aslink
asx8051
as-z80
link-gbz80
link-hc08
link-z80
makebin
packihx
s51
savr
sdcc
sdcclib
sdcdb
sdcpp
shc08
sz80
$

  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.

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

Reply via email to