public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: thomasdr@us.ibm.com
To: insight-gnats@sources.redhat.com
Subject: insight/220: Can't build Insight on cygwin
Date: Tue, 22 Apr 2003 14:43:00 -0000	[thread overview]
Message-ID: <20030422143851.19931.qmail@sources.redhat.com> (raw)


>Number:         220
>Category:       insight
>Synopsis:       Can't build Insight on cygwin
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 22 14:43:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dave Thomas
>Release:        unknown-1.0
>Organization:
>Environment:
Cygwin
>Description:
Trying to build from development sources to pick up Tcl8.4 for a cygwin version of Insight (rather that doing the patch thing).

I configure in a seperate build directory using ../../src/configure --prefix=/usr/local.

Everything appears to configure fine, but when I try compiling (using make in the build directory), a failure occurs when attempting to build bfd.

Apparently, a libtool has been built that tries to use "lib" when libtool --mode=link is used.  I tried setting up the PATH environment variable so that the Microsoft "lib" tool is in the path (and the dll it required).  Now bfd builds O.K., but when gdb tries to link it doesn't find the libbfd.a it's looking for (a .lib was built instead).  gdb is also looking for libopcodes.a when a .lib was built there also.

>How-To-Repeat:
Build bfd on a cygwin platform.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-04-22 14:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030422143851.19931.qmail@sources.redhat.com \
    --to=thomasdr@us.ibm.com \
    --cc=insight-gnats@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).