custom initrd

[zenyatta]

Stubear: I've only flashed OE once and it was about a month ago, so take my advice with a grain of salt, but the trick is to use gcc 2.95.3 only for the kernel and nothing else. This is an excerpt from my conf/local.conf:

Code: [Select]

# Uncomment this if you want to use a prebuilt toolchain.  You will need to
# provide packages for toolchain and additional libraries yourself You will
# definitely need to say:
ASSUME_PROVIDED = "virtual/arm-linux-gcc-2.95"
# to build any of two Linux 2.4 Embedix kernels,
# i.e. openzaurus-sa-2.4.18 and openzaurus-pxa-2.4.18.
# ASSUME_PROVIDED = "virtual/${TARGET_PREFIX}gcc virtual/libc"I also had problems with oemake failing at opie-libs, and I believe it was when both of those ASSUME_PROVIDED lines were uncommented. So the trick is to uncomment only the first one.

After I had succeeded in flashing OE I expressed ambiguity here at ZUG as to whether a newbie-friendly Howto would make sense or not (fearing actual newbies might flash OE and expect things to actually work). It seems my doubts were foolish indeed. I am re-freshing my OE setup and if I can repeat my success I will definitely post a Howto.

z.

[Stubear]

No - I didn't suggested that OE is the way to create a root file system for the SharpRom because the original poster said:

so to diagnose what was happen I'm trying to make my custom initrd based on OZ.

I apologize - I missed the reference to OZ.

Stu

[Stubear]

Stubear: I've only flashed OE once and it was about a month ago, so take my advice with a grain of salt, but the trick is to use gcc 2.95.3 only for the kernel and nothing else.
<snip>
z.

Zenyatta,
thanks for the tip, but the problem is I want to use gcc-2.95.3 for everything to compile apps that are compatible with the Sharp Rom. OZ doesn't meet my needs at the moment - I need a Japanese input system and the CRIM that comes standard with the Sharp Rom (along with the dictionary and translator) make it very easy to find the meaning of Kanji I can draw but don't know the readings/meanings of.

There are a number of apps I'd like to compile/package using OE, but till I get qtopia or opie compiled with 2.95.3 I can't even test them on Z. I've compiled some of them for OZ using gcc 3.4 but they don't work with the standard Sharp ROM (wrong glibc to start)

Guess it's back to cross-compiling everythnig by hand

Stu

[Mickeyl]

This may be a good point to make a recommendation here:

If someone would take the plunge and add a 2.95.3 toolchain as well as a glibc 2.2.x to OpenEmbedded, all the SharpROM customizers would benefit - because you could use OpenEmbedded to build SharpROM compatible packages.

I'm not interested and no one of the OE core people is - however we will be glad to assist (via IRC and mailing list) if someone of you would take a shot at it.