public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@debian.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: [Fwd: Please update libtool]
Date: Tue, 17 Aug 2004 16:06:00 -0000	[thread overview]
Message-ID: <20040817160458.GA7215@khazad.dyndns.org> (raw)
In-Reply-To: <20040817155436.GK11588@redhat.com>

On Tue, Aug 17, 2004 at 11:54:36AM -0400, Frank Ch. Eigler wrote:
> > Date: Tue, 17 Aug 2004 01:47:47 +0200
> > From: Robert Millan <rmh@debian.org>
> > To: gdb@sources.redhat.com
> > Cc: glibc-bsd-hackers@nongnu.org
> > Subject: Please update libtool
> >
> > Hi,
> > 
> > Please, could you update libtool in the following directory:
> >   src/sid/component/cfgroot/libltdl/
> > An up-to-date libtool is necessary for proper GNU/k*BSD support.
> 
> Could you provide more information about what problems you are 
> encountering, and why you think updating libltdl/libtool would
> help them?

I'm porting gdb to GNU/k*BSD systems.  Since only libtool 1.5.x or later
supports these systems, building gdb fails because of uninitialised shlib_ext
variable (I can dig up the exact error if you need it).  

Updating the local copy of libtool in that directory would solve the problem.
Could you do that for me?

Appreciated,

-- 
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))

  reply	other threads:[~2004-08-17 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4122249F.9070206@redhat.com>
2004-08-17 15:54 ` Frank Ch. Eigler
2004-08-17 16:06   ` Robert Millan [this message]
2004-08-17 16:20     ` Frank Ch. Eigler
2004-08-17 22:57       ` Robert Millan

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=20040817160458.GA7215@khazad.dyndns.org \
    --to=rmh@debian.org \
    --cc=fche@redhat.com \
    --cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).