From: Neil MacMunn <neil@gumstix.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: EFL_SRCREV bump breaks GPE/enlightenment
Date: Sun, 30 Jan 2011 14:08:50 -0800 [thread overview]
Message-ID: <4D45E172.4030105@gumstix.com> (raw)
In-Reply-To: <20110117185830.GL21179@jama>
>
> does it segfault or something? I haven't seen it with illume2 profiles,
> but I'm not using gpe-dm..
I don't see any messages about what's happening but I seem to remember
something about a missing function in a .so. There was another EFL_SRCRV
change recently so I undid my revisions and accepted all of the upstream
changes. Unfortunately still no luck.
> Would be great if you can provide info and debug it with e devs
> (#edevelop on freenode), if you bisect which efl commit caused it, they will
> be able to fix it sooner.
>
> Regards,
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-01-30 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:29 EFL_SRCREV bump breaks GPE/enlightenment Neil MacMunn
2011-01-17 18:58 ` Martin Jansa
2011-01-30 22:08 ` Neil MacMunn [this message]
2011-01-31 13:09 ` Martin Jansa
2011-02-02 23:01 ` Neil MacMunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D45E172.4030105@gumstix.com \
--to=neil@gumstix.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox