X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.4 required=5.0	tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,TW_BJ
X-Spam-Check-By: sourceware.org
Message-ID: <40061A22EBC6455991351C55D9C2FD26@desktop2>
From: "Sisyphus" <sisyphus1 AT optusnet DOT com DOT au>
To: <tomdean AT speakeasy DOT org>, <cygwin AT cygwin DOT com>
References: <1313874009 DOT 16574 DOT 15 DOT camel AT asus>
In-Reply-To: <1313874009.16574.15.camel@asus>
Subject: Re: x86_64-w64-ming32-g++ file not recognized by objdump
Date: Sun, 21 Aug 2011 12:09:49 +1000
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="UTF-8";	reply-type=original
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


----- Original Message ----- 
From: "Thomas D. Dean"

> #include <vector>
> #include <string>
> using namespace std;
> int main() {
>  vector<string> vs;
>  vs.push_back("asdf");
> }
>
> If I compile with g++, I get an executable that works, i.e. runs without
> error.  This file is recognized by objdump and cygcheck.
>
> If I compile with x86_64-w64-ming32-g++ -m64 t.cc -o t

I presume the 'ming32' is a typo.
Is the '-m64' necessary ?
What happens if you remove it from the command ?

I can't reproduce the error you get (either with or without '-m64'), though 
I'm just running mingw in the cmd.exe shell - not under Cygwin.

> the resulting executable produces an error message
>> ./t.exe
> t.exe: error while loading shared libraries: ?: cannot open shared
> object file: no such file or directory.
>> objdump -p ./t.exe
> objdump: ./t.exe: File format not recognized

I think that's to be expected - objdump expects to look at a 32-bit 
executable.
I get the same error when I run objdump on a 64-bit executable.
Try:
x86_64-w64-mingw32-objdump -p ./t.exe

Cheers,
Rob 


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