My OE env is building packages, whats next?

[bluey]

I was able to build a few packages, they\'re linking to libc 2.3.4.

Where to go next? I can\'t get opie packages to build yet, since there must be dependencies which I haven\'t built yet, and oemake isn\'t solving them for me... Must be something I\'m not doing right.

Can someone which is already doing something a step further of just having OE building packages give me a few hints or point me a place to go search for them?

Thank you.

[Mickeyl]

oemake opie-image builds a complete OZ-image which should be at least booting into the command line.
See http://openembedded.org/oe_wiki/index.php/OzTODO3.5.1 for what needs to be done before the next release can happen.

[bluey]

Hi

It seems that oemake makes use of the current gcc on the oe env, instead of 3.3.2 on /opt/cross, is it prone to problems? How do I define which compiler to use?

[EDIT] Is it a reason to get \"internal compiler errors\"? [/EDIT]

Thanks.

[Mickeyl]

glibc-cvs doesn\'t work at the moment. I use:

CVSDATE_glibc = \"20040525\"
CVSDATE_glibc-initial = \"20040525\"

in local.conf, which is the last known good version.

You can use prebuilt toolchains, but it\'s not recommended. Read local.conf.sample for how to do this.

[bluey]

Thank you!

For dropbear changes in the TODO there\'s a check in auth.c which needs to be changed, what is wanted? The check can be logged, but doesn\'t reports a failed login, or could be added a config option to permit or not empty passwords.

This check is hardcoded in an if:
        if (ses.authstate.pw-]pw_passwd[0] == \'\0\') {
                TRACE((\"leave checkusername: empty pword\"));
                dropbear_log(LOG_WARNING, \"user \'%s\' has blank password, rejected\",
                                ses.authstate.printableuser);
                send_msg_userauth_failure(0, 1);
                return DROPBEAR_FAILURE;
        }


As for a lightweight ssh client, isn\'t lsh a good option?

[Mickeyl]

could you check if the dropbear patch from buildroot still applies?

lsh is not really good and it requires bash. I\'m currently looking into putty.

The best option would be someone writing a new client based on matrixssl which is fast and tiny.

[bluey]

I never used buildroot, where can I see the patch?

Do you recall what it did? If it just removed that check or did something else?

[Mickeyl]

Nevermind, I added the patch.

[bluey]

It works. I was able to build dropbear without errors, so the patch still applies.