Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Patch to imported readline to allow DJGPP build
Date: Mon, 29 Dec 2003 22:32:00 -0000	[thread overview]
Message-ID: <16368.43916.468843.207711@localhost.redhat.com> (raw)
In-Reply-To: <7137-Mon29Dec2003100055+0200-eliz@elta.co.il>

Eli Zaretskii writes:
 > The current imported readline is broken for DJGPP.  The following
 > patch is needed to allow GDB to build the DJGPP port.  Okay to commit?
 > 
 > Btw, I don't understand what is going on with Readline: I looked at
 > its official home page (to figure out how to submit the patches below
 > to the Readline maintainer) and found there an old version 4.3 of
 > Readline where the DJGPP-specific code is ripped out.  The version
 > that we have in the GDB repository seems a newer one, but it also has
 > the DJGPP-specific code in it.  Can someone please tell me what is the
 > story behind this?  TIA
 > 

I remember having exchanged some mail with Chet and you about this,
but I don't remember the outcome. I can't find anything in my old mbox
either.  The readline in our tree includes some patches on top of pure
4.3.  One of the patches is this one, which I kept from the previous
version:

2000-07-10  Eli Zaretskii  <eliz@is.elta.co.il>
                                                                                
        * terminal.c (_rl_get_screen_size) [__DJGPP__]: Determine screen
        size via DJGPP-specific calls.
        (_rl_init_terminal_io) [__MSDOS__]: DJGPP-specific terminal
        initialization.
        (_rl_backspace) [__MSDOS__]: Don't call tputs.
        (ding) [__MSDOS__]: Use DJGPP-specific calls to support visible
        bell.
        * display.c (_rl_move_vert) [__MSDOS__]: Support cursor movement
        upwards with DJGPP-specific calls.
        (_rl_clear_to_eol) [__MSDOS__]: Don't call tputs.
        (_rl_clear_screen) [__MSDOS__]: Support clear-screen with
        DJGPP-specific calls.
        (insert_some_chars) [__MSDOS__]: Don't call tputs.
        (delete_chars) [__MSDOS__]: Don't call tputs.

Other changes are those listed in ChangeLog.gdb. You can do a diff
with a pristine 4.3 readline. There are some other local changes that
I keep integrating at each import.  I should probably have specified
that in the changelog entry at the time.

the files with local changes are:
 ./aclocal.m4
 ./config.h.in
 ./configure
 ./configure.in
 ./display.c
 ./Makefile.in
 ./rlmbutil.h
 ./rltty.c
 ./shell.c
 ./signals.c
 ./terminal.c


You changes are OK. I think you should audit the current diffs,
though, to see if they are all still needed for DJGPP.

On top of that there are some 'official' patches that are advertised
on the readline home page, which I have not merged. 

elena


  reply	other threads:[~2003-12-29 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29  8:03 Eli Zaretskii
2003-12-29 22:32 ` Elena Zannoni [this message]
2003-12-30  6:16   ` Eli Zaretskii
2004-01-15 19:03     ` Elena Zannoni
2004-01-17 18:27       ` Eli Zaretskii
2003-12-30  7:26   ` Eli Zaretskii
2003-12-29 19:57 Michael Elizabeth Chastain
2003-12-29 21:48 ` Eli Zaretskii

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=16368.43916.468843.207711@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /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