From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 3/5] emacs: Un-blacklist, seems to work fine with new qemu
Date: Thu, 12 Feb 2015 17:53:19 +0100 [thread overview]
Message-ID: <20150212165319.GE2272@jama> (raw)
In-Reply-To: <CACS+7ZSv+hsBjSjfYMFmkT8D9SL=JGYpAbe1oDe35t4T__uqCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On Thu, Feb 12, 2015 at 07:51:39AM -0600, Dan McGregor wrote:
> On 5 Feb 2015 14:10, "Nicolas Dechesne" <nicolas.dechesne@linaro.org> wrote:
> >
> > On Thu, Feb 5, 2015 at 5:10 PM, Dan McGregor <danismostlikely@gmail.com>
> wrote:
> > > In my testing I explicitly disabled x11 in PACKAGECONFIG. I suspect
> > > there may be something broken in its X11 support, maybe I should
> > > remove x11 from the default PACKAGECONFIG set?
> >
> > indeed, without X11 emacs now works fine in non X11 environment. i am
> > not sure what to say then... if i use debian or ubuntu on the same
> > board, emacs works fine with or without X11, so we must be doing
> > something wrong in the recipe..
>
> I figured it out. There's a known bug in the emacs-23 branch that was
> distro patched in several other distros. Basically glib fixed a bug the
> emacs relied upon to function. I have a new patch I'll post later today
> that fixes this issue and some others identified in Martin's bitbake world
> run.
Did you notice that qemu segfaulted in qemux86* world builds?
It looks like the original issue with pixman/pci is still there.
> The proper fix is to import emacs 24, but that'll take longer. When I'm
> done I'll also post that.
>
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-02-12 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 20:29 [meta-oe][PATCH 0/5] Fixes for display managers, emacs, and dracut Dan McGregor
2015-02-04 20:29 ` [meta-oe][PATCH 1/5] xserver-nodm-init: only enable for runlevel 5 Dan McGregor
2015-02-04 20:29 ` [meta-oe][PATCH 2/5] lxdm: RDEPEND on libsvg-gtk Dan McGregor
2015-02-04 20:29 ` [meta-oe][PATCH 3/5] emacs: Un-blacklist, seems to work fine with new qemu Dan McGregor
2015-02-05 13:43 ` Nicolas Dechesne
2015-02-05 16:10 ` Dan McGregor
2015-02-05 20:08 ` Nicolas Dechesne
2015-02-12 13:51 ` Dan McGregor
2015-02-12 16:53 ` Martin Jansa [this message]
2015-02-04 20:29 ` [meta-gnome][PATCH 4/5] gdm: Only start in runlevel 5 Dan McGregor
2015-02-04 20:29 ` [meta-initramfs][PATCH 5/5] dracut: recipe cleanup Dan McGregor
-- strict thread matches above, loose matches on Subject: below --
2015-02-04 18:40 [meta-oe][PATCH 3/5] emacs: Un-blacklist, seems to work fine with new qemu Dan McGregor
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=20150212165319.GE2272@jama \
--to=martin.jansa@gmail.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