Michael 'Mickey' Lauer wrote:
> Note: This is more something for oe_at_handhelds.org
>
>
>>I then tried the more ambitious
>>oemake world
>
>
> Don't use world. I put a sixpack of your favourite beer that there will
> be no point in the next 12 months where world is supposed to compile
> through.
Ah well, at least I know I'm not to blame :)
> There are just too many packages without maintainers for this
> to happen.
Shame.
Is there a way to allow oemake to continue after merely removing the
failed package?
Maybe the -k option comes close?
> oemake meta-opie-static will build most of the opie packages in oe.
bootstrap-image & then opie-image were fine.
I tried meta-opie-static after that, but ended up with a segmentation
fault during do_compile of opie-odict. This didn't happen when I ran the
oemake a second time, though it did later fault elsewhere.
I'm guessing my system isn't stable :/
I've had no trouble with this hardware in the past. I can only assume
it's down to the recent SuSE 9.1 install, as that does have a young
2.6.5 kernel. Darn or words to that effect :(
...
<more fiddling>
On several occasions the machine's locked solid. I was using KDE & had
oemake running under vty2. Pointer frozen, keyboard unresponsive &
unable to switch to a vty. ssh from another machine got no response. Had
to reset.
I thought ReiserFS could cope with this kind of behaviour & although it
unrolled a dozen transactions upon reboot, it didn't make any further
complaints...
However I then found running oemake produced seg faults after an
intermittent time of the order of ten seconds, so something was very wrong.
fsck.reiserfs now tells me there are serious corruptions, so I'm
currently doing a fsck with --rebuild-tree :/
I wonder if the original problem had anything to do with me enabling the
kde screensaver option to inform the screensaver about power management.
Will have to google for suse 9.1 kernel problems.
<sulk>
>
>>Unfortunately this failed after only 14 minutes, in task do_compile for
>>package gs-8.01-r0, with a "cannot find -lXt" fatal error.
>
> Sounds like ghostscript needs a few more dependencies.
>
What would I need to know to resolve such problems myself? Assuming the
answer is very long, could you just point me in a direction? Ta.
-- Michael m r o z a t u k g a t e w a y d o t n e tReceived on Sun Sep 12 2004 - 11:56:27 EDT
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:31:19 EDT