Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Sun, 18 Jun 2000 20:52:47 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: [ANNOUNCEMENT] Updated: termcap-20000618
Message-ID: <20000618205247.A10258@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cygwin@sourceware.cygnus.com
References: <01bfd95c$eca5a300$de86b3d1@deschutes>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <01bfd95c$eca5a300$de86b3d1@deschutes>; from goudey@earthlink.net on Sun, Jun 18, 2000 at 12:39:31PM -0700

On Sun, Jun 18, 2000 at 12:39:31PM -0700, Dale Goudey wrote:
>Linking with libtermcap.a fails, and objdump does not recognize the object
>file format of the object files in the library.  I am using the latest
>gcc/binutils
>
>error message (the same for any of the 6 object files in libtermcap.a):
>  objdump: tputs.o: File format not recognized
>
>After restoring the previous libtermcap.a things work fine.

Or, rebuilding the termcap from sources.

The problem was that I build these things on linux and a botched
configure script ended up causing a native libtermcap.a library to be
built rather than a cygwin one.  I never noticed before because this is
the first time that I built libtermcap with my nifty new "mknetrel"
script which checks out a fresh copy and builds everything with standard
parameters.

Anyway, a new version has been uploaded.  I'm not going to announce
this again on cygwin-announce, though.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com