New Feed For Sharprom And Compatible Options

[enodr]

I built cron & bc yesterday in my spare time & just built mutt.  Only takes a few minutes.  Is it possible to upload ipk's made so they can be added to the feed?  Or Enodr, do you want to build these items yourself?  I don't care either way, I was just trying to save some duplication of work for people.  I'm only using these packages on my 5500 running a hybrid tkc/sharp rom.  On my 5600, I'm running OZ/Opie and GPE.  I'm using my 5500 more for PDA/Work usage right now, and my 5600 is a hack system.  Atleast till I get another a 3000/3100/3200.

Did you build these packages using Openembedded? If yes, did you push the recipes in OE (or maybe they are already here?).

If not, I may open a secondary (temporary)binary only feed which will contain packages which are not yet "buildable" with Openembedded (I won't have time to make recipes for everything. That's why I prefer spending time explaining how to setup Openembedded so that people can help by making recipes.

[kb7sqi]

I built cron & bc yesterday in my spare time & just built mutt.  Only takes a few minutes.  Is it possible to upload ipk's made so they can be added to the feed?  Or Enodr, do you want to build these items yourself?  I don't care either way, I was just trying to save some duplication of work for people.  I'm only using these packages on my 5500 running a hybrid tkc/sharp rom.  On my 5600, I'm running OZ/Opie and GPE.  I'm using my 5500 more for PDA/Work usage right now, and my 5600 is a hack system.  Atleast till I get another a 3000/3100/3200.

Did you build these packages using Openembedded? If yes, did you push the recipes in OE (or maybe they are already here?).

If not, I may open a secondary (temporary)binary only feed which will contain packages which are not yet "buildable" with Openembedded (I won't have time to make recipes for everything. That's why I prefer spending time explaining how to setup Openembedded so that people can help by making recipes.

So far all the packages I've built have been using the packages already in OE. I haven't tried adding anything yet. I'll be trying that soon as I want to change how a few packages are built for Sharp rom and for OpenZaurus. I guess I should've started off trying to build stuff for OpenZaurus first instead of sharprom-compatible. Yesterday, I setup another build setup for OpenZaurus, and built several items like my own kernel, etc. I liked how it automatically built the cross-compile tools automatically and setting everything up. While I was at it, I went ahead rebuilt my 5600 setup w/ OZ/Opie.

The reason I asked if it was possible to upload prebuilt packages was that way you didn't have to re-build stuff someone else already had. I understand everyone has other things to do, like work for a living, goto school etc. :-) I spend 95% of my time dealing w/ Sun hardware and Solaris . The other 5% I spend with my family and working on stuff like getting sofware to run on old *nix OS's like NeXTSTEP/Openstep, Apple A/UX, and my Z's. And I don't mind contributing time/effort in any small way to help.

[enodr]

So far all the packages I've built have been using the packages already in OE.

Great.

The reason I asked if it was possible to upload prebuilt packages was that way you didn't have to re-build stuff someone else already had.

That's fine. I want to rebuild everything by myself to be sure there is no bug in the recipes. If I find a bug I can try to solve it (or bug OE people for some help!!).

I am updating the feed tonight will all the packages mentioned above (mutt, bc, ...).

Please do post requests in this thread, I'll try to build as much packages as possible. Also I welcome the proposal to use a parallell "binary packages" only feed with packages that (for the moment) can't be built with OE. PM me if you want to help.

[koen]

I am updating the feed tonight will all the packages mentioned above (mutt, bc, ...).

2 days ago:

CODE

koen@serenity:~/public_html/sharprom$ php update.php
Updating Sharprom compatible unstable main: 407 packages
Added 407 packages in 0 days, 0 hours, 0 minutes and 7 seconds

5 minutes ago:

CODE

koen@serenity:~/public_html/sharprom$ php update.php
Updating Sharprom compatible unstable main: 722 packages
Added 722 packages in 0 days, 0 hours, 0 minutes and 13 seconds

[grog]

How about please compiling opie-camera & requirements? I found a working package here, but it'd be great to have it in what is now the main feed . thks

[rolf]

Enodr, nice project. Have you been able to compile perl recently?

BTW, make sure you don't get into trouble. Is all the stuff you have OK for republication? Do you publish sources for the GPL stuff?

[enodr]

Enodr, nice project.  Have you been able to compile perl recently?

CODE

arm-linux-ld: cannot find -lgcc_s

BTW, make sure you don't get into trouble.  Is all the stuff you have OK for republication?  Do you publish sources for the GPL stuff?

All the packages in the feed are built using OE, ie are under some Open Source licence. I don't publish the sources, I don't know how OE people deal with this matter (I guess every project built with OE has this problem).

[koen]

Enodr, nice project.  Have you been able to compile perl recently?

CODE

arm-linux-ld: cannot find -lgcc_s

BTW, make sure you don't get into trouble.  Is all the stuff you have OK for republication?  Do you publish sources for the GPL stuff?

All the packages in the feed are built using OE, ie are under some Open Source licence. I don't publish the sources, I don't know how OE people deal with this matter (I guess every project built with OE has this problem).

From the *front*page of openembedded.org: http://www.openembedded.org/gpl-causing-pr...e-linux-distros

[rolf]

Enodr, nice project.  Have you been able to compile perl recently?

CODE

arm-linux-ld: cannot find -lgcc_s

From the *front*page of openembedded.org: http://www.openembedded.org/gpl-causing-pr...e-linux-distros

As always, OE taking good care of you Which is why I asked, enodr. Don't get into trouble if it can be so easily avoided

But what about the stuff you mirror which you did not compile? Did you make sure you are OK to republish that stuff?

[markpmc]

A new feed for Sharprom and compatible distros (cacko, ...) is available here:

...snip...

enodr,
Thanks for the feed and the packages.

I've managed to rebuild Andy's (imasmith) cacko 1.23 beta from his original sources. I plan to update the kernel this week. My plan is to add squashfs and a few other patches to tetsu's latest kernel. Any words of warning? specific patches?

I'm fairly happy w/ the performance of Andy's beta, is there much to be gained from porting Cacko final 1.23 ROM to the C3000? I'm more than a little unclear on what's involved in porting Cacko 1.23 from the C3100 to the C3000. It should require some mount point and init script changes, but I tried this approach about a year ago and couldn't figure it out. Has anyone tried this particular approach?

Mark

[enodr]

But what about the stuff you mirror which you did not compile?  Did you make sure you are OK to republish that stuff?

No I didn't... I just looked at the mirror you are referring, I will remove the binary only feeds and leave only the documentation stuff (like docs.zaurus.com). The binary mirror were not meant to be public, but should be my private archive.

[rolf]

Just in case anyone was interested in compiling themselves. There are instructions on how to compile for Sharp ROM in the OE wiki.

[ogrefish]

Thanks rolf. Ive embarked on a journey of learning (much thanks to Speculatrix for the help) but its gonna take a while before i get to grips with anything worthwhile, although progress is steadily being made.

Its possible alot more people would produce stuff if there was, and i hate to put it like this, a spoonfed step by step tutorial on setting things up specifically for cacko to the end result. It would only help the cacko community im sure. those who have yet to get to grips with this side of the zaurus.

Im not sure if this is the right thread for 'a would like compiled question' but would anyone fancy kindly taking the time to compile the latest aircrack-ng with injection drivers for the 2.4.18 kernel, if so would be greatly appreciated.

thanks for the assistance so far people.

[rolf]

Its possible alot more people would produce stuff if there was, and i hate to put it like this, a spoonfed step by step tutorial on setting things up specifically for cacko to the end result.

My perspective on this is "If it is sinking, jump ship before you get drowned."

As far as spoon-fed goes, my above-link is spoon-fed. If not, feel free to improve it. There are also spoon-fed instructions for how to set up OE for yourself for a number of distros.