Martin Jansa writes:
> On Mon, Mar 01, 2010 at 05:22:55PM +0100, David Lanzendörfer wrote:
>> PREFERRED_VERSION_ffalarms="0.2.2"
>> in conf/local.conf fixed the error.
>> But GIT version isnt building.
>> WTF?
>> Anyway. Built trough now. But it shouldn't happen.
>> Should it?
>>
>> leviathan
>
>
Am Montag 01 März 2010 schrieb Michael Moroni:
> I got segfault by upgrading (opkg update && opkg upgrade) in
> task-shr-minimal-base...
>
> Downloading
> http://build.shr-project.org/shr-unstable/ipk//om-gta02/task-shr-minimal-ba
>se_2.0-r25.4_om-gta02.ipk. Segmentation fault
It does not matter w
2010/3/1 Martin Jansa
> due to somehow broken build
>
> This is diff between working and segfaulting libopkg.so.0.0.0, no idea
> why gcc generated that (maybe there is problem with ram in buildhost,
> because all builds segfault a lot today from /usr/bin/python).
>
> To fix your opkg you can use
due to somehow broken build
This is diff between working and segfaulting libopkg.so.0.0.0, no idea
why gcc generated that (maybe there is problem with ram in buildhost,
because all builds segfault a lot today from /usr/bin/python).
To fix your opkg you can use binary from here
mv /usr/lib/libopkg
On Mon, Mar 01, 2010 at 05:22:55PM +0100, David Lanzendörfer wrote:
> PREFERRED_VERSION_ffalarms="0.2.2"
> in conf/local.conf fixed the error.
> But GIT version isnt building.
> WTF?
> Anyway. Built trough now. But it shouldn't happen.
> Should it?
>
> leviathan
replace next(rev item) with get_ne
PREFERRED_VERSION_ffalarms="0.2.2"
in conf/local.conf fixed the error.
But GIT version isnt building.
WTF?
Anyway. Built trough now. But it shouldn't happen.
Should it?
leviathan
signature.asc
Description: This is a digitally signed message part.
___
S
On Monday 01 March 2010 10:51:09 David Wagner wrote:
> Hi
>
> The buildhost for both SHR and hackable:1 went Out Of Memory yesterday
> evening, that's why it was unreachable.
> It was rebooted this morning and it is accessible again.
Please. take a look at this issue:
r...@om-gta02 ~ $ opkg updat
On Mon, Mar 01, 2010 at 11:14:10AM +0200, Tom Hacohen wrote:
> What if I installed a fresh image?(boots now) will something break in the
> future?
It depends if opkg package was upgraded for you or not.
If you flashed fresh image (but not the one which will be built today) and
you had opkg upgrad
Hi
The buildhost for both SHR and hackable:1 went Out Of Memory yesterday
evening, that's why it was unreachable.
It was rebooted this morning and it is accessible again.
Have a good day.
___
Shr-devel mailing list
Shr-devel@lists.shr-project.org
http:/
On Mon, Mar 1, 2010 at 9:37 AM, Martin Jansa wrote:
> If you have this version of opkg 0.1.6+svnr522-r19* and seen busybox
> upgrade
>
> Then your image won't probably start after reboot!
>
> There is fix for it already
>
> http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=09a79a497f9c
On Mon, Mar 01, 2010 at 08:34:50AM +, Rui Miguel Silva Seabra wrote:
> Upgraded yesterday and the Freerunner booted into SHR-u.
>
> However, ipkg was a dir of it's own, so I did the link.
That's normal for "older" images and situation like this was expected in
that opkg postinst, which means
Upgraded yesterday and the Freerunner booted into SHR-u.
However, ipkg was a dir of it's own, so I did the link.
However, alternatives has 215 files (rather a lot more than
alternatives-backup).
However, my init has the sysvinit and busybox lines in reverse order
than you show there.
r...@om-gt
12 matches
Mail list logo
