OESF Portables Forum

Everything Else => Zaurus - Everything Development => Distros, Development, and Model Specific Forums => Archived Forums => Open Embedded => Topic started by: ShiroiKuma on June 22, 2006, 05:40:50 pm

Title: Oe Build System Fundamentally Flawed?
Post by: ShiroiKuma on June 22, 2006, 05:40:50 pm
I don't know if this has been anyone else's experience, but I've found that building packages in OE with their dependencies and then installing them. More often than not results in a GPE system that will not allow you to log in - which is a big problem.

During the past three weeks I average I think three reflashes a day, this is getting totally ridiculous.

Basically, when building anything more than simple, the way it builds the packages is that I end up having to upgrade many other dependencies, and then it runs, but only until a reboot.

Then I get to the point where the login screen flashes briefly, it goes back to the black screen with a cursor, then a login screen flash and so on and so on.

Last thing that really pissed me off is I took the whole deploy/ipk directory from OE, made it a feed, and simply ran ipkg upgrade and voila - the same result, no way it would let me login...

Is this only me and have I set up something wrongly? Anyone else see this behavior?
Title: Oe Build System Fundamentally Flawed?
Post by: Mickeyl on June 22, 2006, 06:46:28 pm
Sounds like you shouldn't use the .dev branch and/or a floating SRCDATE.

Although OpenEmbedded gives you the power to build complete distributions with just one command, it progresses too fast for anyone to guarantee that it always builds something working for all machine/distribution configurations. That's why we have release branches.
Title: Oe Build System Fundamentally Flawed?
Post by: ShiroiKuma on June 23, 2006, 03:41:34 am
Quote
Sounds like you shouldn't use the .dev branch and/or a floating SRCDATE.

Although OpenEmbedded gives you the power to build complete distributions with just one command, it progresses too fast for anyone to guarantee that it always builds something working for all machine/distribution configurations. That's why we have release branches.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132459\"][{POST_SNAPBACK}][/a][/div]
Can you point me info about SRCDATE, if that'll solve the prob. I'd like to use the dev branch and I'm not building the whole system. The only thing I'm doing is building indiv. packages, which build their dependencies, and then install should work right? I don't see a reason why this should mess up the whole system.
Title: Oe Build System Fundamentally Flawed?
Post by: Hrw on June 23, 2006, 04:33:34 am
Use .oz354x and DISTRO="openzaurus-3.5.4.1" if you want something which build and work for sure. Leave .dev for people which know how to use OE, what SRCDATE is etc.

In other words: If you are OE newbie and want to 'just build something for my Z' then .oz354x with DISTRO="openzaurus-3.5.4.1" is for you.
Title: Oe Build System Fundamentally Flawed?
Post by: ShiroiKuma on June 23, 2006, 05:04:47 am
Quote
Use .oz354x and DISTRO="openzaurus-3.5.4.1" if you want something which build and work for sure. Leave .dev for people which know how to use OE, what SRCDATE is etc.

In other words: If you are OE newbie and want to 'just build something for my Z' then .oz354x with DISTRO="openzaurus-3.5.4.1" is for you.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132521\"][{POST_SNAPBACK}][/a][/div]
OK, will try this then.
Title: Oe Build System Fundamentally Flawed?
Post by: lardman on June 23, 2006, 03:15:45 pm
Quote
Then I get to the point where the login screen flashes briefly, it goes back to the black screen with a cursor, then a login screen flash and so on and so on.

Sounds like the x server is crashing.

FWIW, my gpe-image which I built this week from .dev works, but touch screen calibration is broken (xtscal segfaults), other than that it's fine.


Si