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.
On Fri, Oct 18, 2013 at 6:15 AM, James Hilliard
<[email protected]>wrote:
> Do I need to submit everything all at once or can I add things slowly so I
> can confirm all components are in compliance with openwrt formatting etc?
> The first thing to do would be to revert the removal of the ubicom32
> platform here https://dev.openwrt.org/wiki/ubicom32, from there I can
> work on integrating the device specific patches. Should I submit a patch
> for that removal?
>
>
> On Thu, Oct 17, 2013 at 6:50 AM, James Hilliard <[email protected]
> > wrote:
>
>> So, I think i more or less got the boot processes down, however I don't
>> have hardware with me right now. Boot goes from ultra>uboot>linux more or
>> less. From the looks of it getting a console on uboot should be fairly
>> straight forward. I'm going to attempt to compile an oem build with the
>> uboot console enabled that way we can debug and flash over Ethernet instead
>> of serial. Msg me on gtalk and ill send you some builds(this email).
>>
>>
>> On Thu, Oct 17, 2013 at 2:04 AM, [email protected] <
>> [email protected]> wrote:
>>
>>> Hi James
>>> AFAIR dir-657 soucecode has openwrt's port which compiles but has no
>>> ethernet switch enabled/ported. I's hard to test develop anything without
>>> flash programmer so i dropped testing. It would be nice if you could add
>>> this model to your work
>>>
>>> Thanks,
>>> Michal
>>>
>>>
>>> Dnia 16 października 2013 20:53 James Hilliard <
>>> [email protected]> napisał(a):
>>>
>>> > I think i'll attempt to support this and get some
>>> vendor/deviceconfigs integrated, can the changes that removed arch support
>>> bereverted easily in trunk? I've been working off of 12.09 here
>>> https://github.com/Lightsword1942/openwrtubicom and manually merging
>>> some things let me know if you have anysuggestions. I'm not sure what
>>> this is using for include/siteand that's what I'm currently hung up
>>> on.
>>> > On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli <
>>> [email protected]> wrote:
>>> > Hello,
>>> > 2013/9/16 James Hilliard <[email protected]>:
>>> > > Anyone interested in OpenWRT on Ubicom? They used OpenWRTinternally
>>> so
>>> > > there is already source ready(may be a little outdatedthough). Also
>>> have
>>> > > some router specific sources of both it and stock.
>>> > OpenWrt did "support" the ubicom32 architecture for awhile, but since
>>> > this is a very quirky architecture and nobody could step up as a
>>> > maintainer, it got removed. Unless you are willing to support that
>>> > architecture, I see no point in supporting it since it reallyrequired
>>> > a lot of quirks (special "hypervisor" software,bootloader and !MMU).
>>> > --
>>> > Florian
>>> > _______________________________________________
>>> > openwrt-devel mailing list
>>> > [email protected]
>>> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>> >
>>> > _______________________________________________
>>> > openwrt-devel mailing list
>>> > [email protected]
>>> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>> >
>>>
>>
>>
>
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
