Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Holcomb <jeffh@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [Patch] updated ltcf-*.sh, ltconfig, ltmain.sh
Date: Mon, 05 Nov 2001 11:27:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1011114112437.27587k-100000@taarna.cygnus.com> (raw)
In-Reply-To: <3BF22763.6090001@cygnus.com>

On Wed, 14 Nov 2001, Andrew Cagney wrote:

> Is there a reason for pulling in GCC's hacks rather than going to the 
> official version per src/MAINTAINERS:
> 
> ltconfig; ltmain.sh
>          libtool: http://gnu.org
>          Changes need to be done in tandem with the official LIBTOOL
>          sources or submitted to the master file maintainer and brought
>          in via a merge.

It was my impression from Alexandre that he had already imported these 
changes from the official sources into gcc's tree.  For some reason, they 
weren't imported into the binutils/gdb tree at that time.

> If we pull in a GCC hack such as:
> 
> >  2001-07-21  Michael Chastain  <chastain@redhat.com>
> > * ltconfig: Set max_cmd_len to a maximum of 512Kb, as it seems some
> >         HPUX 11.0 systems have trouble with 1MB.  Mark as gcc-local.
> >         * ltmain.sh: Mark as gcc-local.
> 
> then (no offence to MichaelC) we're taking on the responsibility of 
> carrying that patch forward everytime a further import occures.

I understand this is in the official sources now, so it's not actually a 
gcc-local hack.  Perhaps the entry should be changed.

I do need this to be able to configure on our HPUX 11.0 systems.

--
Jeff Holcomb
jeffh@redhat.com
GDB Engineering
Red Hat, Inc.


  reply	other threads:[~2001-11-14 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05  7:17 Jeff Holcomb
2001-11-05  8:58 ` Andrew Cagney
2001-11-05 11:27   ` Jeff Holcomb [this message]
2001-11-06 14:38     ` Andrew Cagney
2001-11-10 13:15       ` Alexandre Oliva
2001-11-05 10:42 Michael Elizabeth Chastain
2001-11-06  8:12 ` Alexandre Oliva

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=Pine.SOL.3.91.1011114112437.27587k-100000@taarna.cygnus.com \
    --to=jeffh@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=binutils@sources.redhat.com \
    --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