Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michel (BusError) <buildroot.atmel.com@pollet.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] SCREEN: Added support for GNU Screen
Date: Wed, 9 Apr 2008 11:26:44 +0100	[thread overview]
Message-ID: <200804091126.44251.buildroot.atmel.com@pollet.net> (raw)
In-Reply-To: <1207718113.6817.282.camel@nigel-x60>

On Wednesday 09 April 2008, Nigel Kukard wrote:
> > > > --- /dev/null
> > > > +++ b/package/screen/screen-4.0.2-100-cross-compile.patch
> > > > @@ -0,0 +1,967 @@
> > > > +diff -c screen.orig/configure screen-4.0.2/configure
> > > > +*** screen.orig/configure	2003-12-05 13:46:53.000000000 +0000
> > > > +--- screen-4.0.2/configure	2008-04-05 18:48:27.000000000 +0100
> > >
> > > <snip>
> > >
> > > Can we not modify configure.ac/in and autoreconf?  (assuming configure
> > > is originally built from configure.in or configure.ac)
> > >
> > > -N
> >
> > You can't. I spent a lot of time trying. This configure relies /a lot/ on
> > testing the hosts libraries, and all of these test fail with these
> > exit(1). Unless you know of a magic auto*.* setting that skips the 'cross
> > compile' tests and/or errors, this is the only way I found to have it
> > working...
>
> I really don't like adding a 40k patch, which will more than likely
> break on each version bump. :)
>
> Could you show me how to reproduce the errors when cross-compiling,
> maybe send me your .config and I'll see what I can do?
>
> -N

Hi Nigel;

I think the easiest way is to apply the patch on a 'temp' tree, remove the 
package/screen/*.patch file, 'make oldconfig' in buildroot, select 
the 'screen' package, then 'make'. You will immediately see the dreaded 
configure problems...

'screen' is very rarely updated tho, it's not a fast moving trendy package, 
just a one that's indispensable once you grok it's power :-)

Michel

      reply	other threads:[~2008-04-09 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 19:41 [Buildroot] [PATCH] SCREEN: Added support for GNU Screen Michel
2008-04-08 19:41 ` [Buildroot] [PATCH] NCURSES: Added config support for copying ncurses 'extra' libraries to the target Michel
2008-04-08 19:41   ` [Buildroot] [PATCH] IPTRAF: Added Interactive Colorful IP LAN Monitor Michel
2008-04-08 19:41     ` [Buildroot] [PATCH] U-BOOT: A patch to fix the fw_printenv compilation Michel
2008-04-08 19:41       ` [Buildroot] [PATCH] U-BOOT: Added support for linux userland environmnet access Michel
2008-04-09  7:02   ` [Buildroot] [PATCH] NCURSES: Added config support for copying ncurses 'extra' libraries to the target Nigel Kukard
2008-04-08 19:57 ` [Buildroot] [PATCH] SCREEN: Added support for GNU Screen Nigel Kukard
2008-04-08 20:16   ` Michel
2008-04-09  5:15     ` Nigel Kukard
2008-04-09 10:26       ` Michel [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=200804091126.44251.buildroot.atmel.com@pollet.net \
    --to=buildroot.atmel.com@pollet.net \
    --cc=buildroot@busybox.net \
    /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