public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Peter Shoebridge" <peter@zeecube.com>
To: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: libtool and lib?
Date: Fri, 06 Aug 1999 12:13:00 -0000	[thread overview]
Message-ID: <039801bee03f$908f6270$4e01020a@netdelivery> (raw)
In-Reply-To: <199908061747.MAA06106@mercury.xraylith.wisc.edu>

I found libtool and will try again tonight. I'm trying to build a m68k-coff
version of the debugger otherwise I would use your bineries.

Thanks

Peter

----- Original Message -----
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Keith Seitz <keiths@cygnus.com>
Cc: Peter Shoebridge <peter@zeecube.com>; Insight (GDB GUI)
<insight@sourceware.cygnus.com>
Sent: Friday, August 06, 1999 11:47 AM
Subject: Re: libtool and lib?


> Keith Seitz <keiths@cygnus.com> writes:
> > On Thu, 5 Aug 1999, Peter Shoebridge wrote:
> >
> > > I'm trying to build the latest snapshot of insight under cygwin b20.1
and
> > > get the following error about libtool and lib, plus something about
> > > cygpath.
> > >
> > > Anyone have a clue what I'm missing?
> >
> > As I recall, libtool has changed. The insight snapshot uses the newer
> > libtool. I am uncertain if B20.1 can be used to build the debugger:
B20.1
> > is quite old. It _should_ be possible to hack around this problem.
> > (You could try, for example, installing a newer libtool or hacking
> > makefiles to support older libtool.)
> >
> > Mumit Kahn has managed to build Insight for cygwin native using the
cygwin
> > snapshots. If you would just like a prebuilt binary, take a look at the
> > insight archives on sourceware. This message was cross-posted to the
win32
> > mailing list:
> >
> > http://sourceware.cygnus.com/ml/insight/1999-q3/msg00005.html
> >
>
> Actually, I never build anything on a windows box if I can help it. I
> cross-compiled Insight on a linux box, and had to make a few tweaks to
> fix minor configuration buglets when building for x86-win32 host. To
> be strictly correct, I should use the term canadian cross here, not
> just cross (the target and host machines were both different than build
> machine).
>
> Unfortunately, I blew away my source tree before I had a chance to commit
> the changes. I'll hopefully retry this in the near future and forward the
> patches to the list.
>
> Insight *should* build on Cygwin b20.1, but I doubt if you can do that
> without working around various, albeit minor, configuration issues.
>
> Unless you have strong need for building it yourself (eg., to fix
problems),
> just use the binaries.
>
> Regards,
> Mumit
>

      reply	other threads:[~1999-08-06 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-05 20:01 Peter Shoebridge
1999-08-06  6:59 ` Keith Seitz
1999-08-06 11:57   ` Mumit Khan
1999-08-06 12:13     ` Peter Shoebridge [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='039801bee03f$908f6270$4e01020a@netdelivery' \
    --to=peter@zeecube.com \
    --cc=insight@sourceware.cygnus.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).