Toolchain And Sources For 3.5.1?

[radioz]

I have a poodle (5600) that I've installed 3.5.1 on. I'd like to try compiling some apps but need to get the toolchain. The OE website has been down for several days, so I can't get it from there.

Does anyone know of a mirror for the development tools and kernel sources? How about a feed for the 5600?

thanks,
radioz

[Windrose]

Right. What he just said.
W.

[radioz]

Ok, the oe website is still down but I found that the ftp site is still working:
   ftp://handhelds.org

There seems to be a huge amount of material here. I think I've found the toolchain(s), kernel sources, feeds, apps, etc.

radioz

[ninsei]

is that the toolchain to use for compiling for 3.5.1?  looks like that only has gcc 3.4.1 and i think OZ stuff is 3.4.2.

[radioz]

I'm not really sure what is needed. I thought that the ftp site might have the right tools and sources, but now I'm not so sure.

Anybody else know where the latest toolchain and OZ/OE sources might be found (and yes, the website is still down after 6 days)?

thanks,
radioz

[Teletubbie]

Hi,
Openembedded will come back, we have to wait.
The toolchain issue is that openembedded builds it itself. It gets the source of every part of the toolchain it needs, then it compiles it on your machine.
But for setting up Openembedded you will need the documentation on the openembedded wiki, that is down at moment.
Cheers,
Sam

[ninsei]

is there any gcc 3.4.2 toolchain binaries and libs (already compiled) for a general linux machine out there?

[adf]

this touches on somethingI haven't quite understood.
If I, for example, downloaded the toolchain that builds 3.5.1, on a monday and 3.5.2 is released on a wednesday , will my toolchain(?)build enviromnent(?) oe stuff update iteslf to keep current, or must I more or less rip it out and start from scratch if I want to build a new 3.5.2 initrd and zimage on thursday?
wouldthis be a no brainer if i just got started?
adf

[lardman]

OE consists of two main parts: The OE python files which actually do the processing and issue the commands to get stuff built, and a packages directory which contains the instructions for how each file (applications, kernels, toolchains, etc. - everything) should be downloaded, processed, compiled, used and packaged, etc.

Both of these sections are available via bitkeeper and are constantly updated. If you were to download them today (via bitkeeper, or the snapshots) then did an 'oemake opie-image' you'd produce version 3.5.2-rc? of OZ (BTW a cross-toolchain would be compiled automatically from source).

Then you can do a 'bk pull' to update both the python files and the packages whenever you need to (before you do a build, so you have the lastest versions).

Any changes will cause any affected packages to be re-built automatically. If you use snapshots, you just delete the old oe and packages directories and place the new ones in their place.


Simon