All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: xterm: either fix it, or remove it. please.
Date: Thu, 12 Nov 2009 06:51:27 -0500	[thread overview]
Message-ID: <4AFBF6BF.9030204@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911120045170.1265@localhost>

On 11/12/2009 12:47 AM, Robert P. J. Day wrote:
>
>    seriously, either the build of xterm_207 should be fixed, or that
> package should be dropped in its entirety.  it's been at least three
> weeks since i pointed out that it doesn't build, and even explained in
> detail *why* it doesn't build and how to fix it.  to no avail.
>
>    so, a humble suggestion -- either fix it, or remove it from OE
> entirely.

Current status, dev changes aren't building at all for me and now the 
machine I work decided to hang in grub. Yah, this recipe is cursed.

You could remove it locally for your build.

Philip


>
> rday
> --
>
> ========================================================================
> Robert P. J. Day                               Waterloo, Ontario, CANADA
>
>              Linux Consulting, Training and Kernel Pedantry.
>
> Web page:                                          http://crashcourse.ca
> Twitter:                                       http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



      parent reply	other threads:[~2009-11-12 11:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  5:47 xterm: either fix it, or remove it. please Robert P. J. Day
2009-11-12  5:56 ` Holger Hans Peter Freyther
2009-11-12  6:22   ` Robert P. J. Day
2009-11-12  6:22   ` Holger Hans Peter Freyther
2009-11-12  6:36     ` Robert P. J. Day
2009-11-12  7:20       ` Holger Hans Peter Freyther
2009-11-12  7:32         ` Holger Hans Peter Freyther
2009-11-12  7:34         ` Robert P. J. Day
2009-11-12  8:33           ` Michael 'Mickey' Lauer
2009-11-12  8:28         ` Graeme Gregory
2009-11-12  8:15       ` Frans Meulenbroeks
2009-11-12 12:28         ` Robert P. J. Day
2009-11-12 12:47           ` Frans Meulenbroeks
2009-11-12 12:58             ` Robert P. J. Day
2009-11-12 13:05               ` Graeme Gregory
2009-11-12 15:37                 ` Robert P. J. Day
2009-11-12 13:11               ` Holger Hans Peter Freyther
2009-11-13  8:43                 ` Robert P. J. Day
2009-11-13  8:55                 ` Robert P. J. Day
2009-11-13  9:32                   ` Graeme Gregory
2009-11-12 13:15             ` Robert P. J. Day
2009-11-12 18:49             ` Mike Westerhof
2009-11-12 21:42               ` GNUtoo
2009-11-12 21:59                 ` Philip Balister
2009-11-12 22:17                   ` Graeme Gregory
2009-11-13  4:38                   ` Robert P. J. Day
2009-11-12 11:51 ` Philip Balister [this message]

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=4AFBF6BF.9030204@balister.org \
    --to=philip@balister.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.