This is the mail archive of the
insight-prs@sources.redhat.com
mailing list for the Insight project.
insight/220: Can't build Insight on cygwin
- From: thomasdr at us dot ibm dot com
- To: insight-gnats at sources dot redhat dot com
- Date: 22 Apr 2003 14:38:51 -0000
- Subject: insight/220: Can't build Insight on cygwin
- Reply-to: thomasdr at us dot ibm dot com
>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: