Date: Wed, 4 Jan 2006 20:32:55 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Ping
Message-ID: <20060105013255.GD26391@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <43BC6BAD DOT 8080907 AT pacbell DOT net> <20060105005032 DOT GA26391 AT trixie DOT casa DOT cgf DOT cx> <43BC6F9C DOT 3060002 AT pacbell DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43BC6F9C.3060002@pacbell.net>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Jan 04, 2006 at 05:00:12PM -0800, Ivan Godard wrote:
>Thank you! Both the binutils from the distribution (as downloaded using 
>your standard tool) and the binutils direct from the gnu web site fail 
>in exactly the same way. I need to compile from source because we are 
>modifying that source to cross-target a new processor. The UNmodified 
>sources compile fine on assorted Unices, but fail on Cygwin, as 
>previously reported.
>
>Could you (or someone) do a source pull of binutils and see if it builds 
>for you under Cygwin? Absolutely vanilla: "./configure; make". At this 
>point I suspect that the source files in the distro do not actually 
>match the binaries in the distro, which should be something you would 
>want to fix if true. I again attach my cygcheck.out.

Your theory that there must be something wrong with the cygwin binutils
distribution because you can't build binutils from either the cygwin
sources or the "gnu.org" source doesn't make a lot of sense to me.

I wonder if this is just a problem of building in the source directory
when tools like binutils, gcc, and gdb are usually built in a separate
build directory.  I'd suggest creating a directory and then doing a

/path/to/source/configure

I did just build binutils that way with no problem.

If that doesn't fix things for you then, I don't know what the problem
is but it seems like there are some obvious things you could do to
track things down, like google for the information, or maybe even try
to actively debug it.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/