Yeah, I looked in the directory to try and find what the missing file should like like, I then searched the oem firmware and oem internal openwrt build and I could not find the missing variables anywhere, there's probably a number of patches that I still need to integrate still from those builds, maybe it is generated on the fly by some package. I've rolled back the Ubicom32 removal from a year ago but I think it was missing a lot of patches and was more incomplete than I originally thought. Should I start submitting patches as soon as I can get it to stop breaking the build system? I mirrored the latest oem and internal sources I have here https://github.com/Lightsword1942/ubicom32 although I have older ones with more device configs, that one I mirrored should have support for the dir-655 B variant. I have most of the other device profile configs as well so that shouldn't be too big an issue. Ill look into this more tomorrow and start integrating the patches from the internal openwrt sources.
On Sat, Oct 19, 2013 at 5:36 AM, Jonas Gorski <j...@openwrt.org> wrote: > On Sat, Oct 19, 2013 at 11:04 AM, James Hilliard > <james.hillia...@gmail.com> wrote: > > I've now based off of trunk and have integrated some actual hardware > > specific configs/patches, I've made progress on a number of other needed > > changes but am stuck on one particular error : > > ERROR: Missing site config for target "ubicom32-openwrt-linux-uclibc" ! > > The missing file will cause configure scripts to fail during > > compilation. > > Please provide a > > "/home/james/openwrt/include/site/ubicom32-openwrt-linux-uclibc" file and > > restart the build. > > make[2]: *** [prereq] Error 1 > > make[1]: *** [prereq] Error 2 > > make: *** [depends] Error 2 > > I have no idea what configure scripts actually need this and how to fix > it. > > It does not exist in the oem ubicom buildroot directory as far as I can > tell > > so I think I just need to kill off whatever is asking for the file since > it > > is probably not needed there. > > Have a look at the other files in this directory. They provide the > defaults for many standard configure script tests (ac_cv_*). Several > of these are usually only found out by running a test program (after > compiling it), which fails badly when cross compiling, thus breaking > the configure step and therefore compilation. > > So in conclusion you will need it, and you need to provide the > appropriate defaults in it. > > > Regards > Jonas > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
