Re: Problem with execution of binary file

> Mark Geisert (that's me) wrote: > > I haven't yet diff'd the two cygchecks > > you sent but maybe that'll lead somewhere. > > I've now done that. The 'good' cygcheck shows many more packages installed > than > the 'bad' cygcheck. But the only package version differences I found were for > bz

Re: Problem with execution of binary file

> bzr, find and mercurial; the 'good' cygcheck paradoxically shows earlier ^ bzr, file and mercurial ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: h

Re: Problem with execution of binary file

Mark Geisert (that's me) wrote: > I haven't yet diff'd the two cygchecks > you sent but maybe that'll lead somewhere. I've now done that. The 'good' cygcheck shows many more packages installed than the 'bad' cygcheck. But the only package version differences I found were for bzr, find and mercur

Re: Problem with execution of binary file

Edvardsen Kåre writes: > The well working installation was kept on the HD in it's own renamed (C: > \cygwin.good) folder when I installed the latest version. The > installation went through like it was the first time I installed cygwin, > I hope this is ok? First, kindly

Re: Problem with execution of binary file

On Fri, Nov 04, 2011 at 06:20:50PM +, Mark Geisert wrote: > Eliot Moss writes: > > I would add that having more than one cygwin installation > > on the same system can be tricky, since you need to insure > > that each program gets the right dlls, etc. > > Sheesh, it's so tricky that I assumed

Re: Problem with execution of binary file

Eliot Moss writes: > I would add that having more than one cygwin installation > on the same system can be tricky, since you need to insure > that each program gets the right dlls, etc. Sheesh, it's so tricky that I assumed the OP meant he had separate VMs for his two Cygwin installations. If the

Re: Problem with execution of binary file

I would add that having more than one cygwin installation on the same system can be tricky, since you need to insure that each program gets the right dlls, etc. Regards -- Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documenta

Re: Problem with execution of binary file

> Anyway, I've installed two versions of cygwin on the same machine - the > first was installed around Oct. 3 and the second one from a few days > ago. Compiling exactly the same software on both versions gives success > on the older installation and failure on the newer one. Could it be that [...]

Re: Problem with execution of binary file

On fr., 2011-11-04 at 05:50 -0500, Eliot Moss wrote: > On 11/4/2011 3:50 AM, Edvardsen Kåre wrote: > > > >> On 11/3/2011 4:56 PM, Eliot Moss wrote: > >> Ok, so here's one thing about bash: to get it to > >> run an *executable* (as opposed to a *script*), > >> you need to

Re: Problem with execution of binary file

On 11/4/2011 3:50 AM, Edvardsen Kåre wrote: On 11/3/2011 4:56 PM, Eliot Moss wrote: Ok, so here's one thing about bash: to get it to run an *executable* (as opposed to a *script*), you need to say "bash -c FLEXPART_GFORTRAN". You might try strace on that. In

Re: Problem with execution of binary file

> On 11/3/2011 4:56 PM, Eliot Moss wrote: > Ok, so here's one thing about bash: to get it to > run an *executable* (as opposed to a *script*), > you need to say "bash -c FLEXPART_GFORTRAN". > You might try strace on that. In addition to the > objdump suggest

Re: Problem with execution of binary file

On 11/3/2011 4:56 PM, Eliot Moss wrote: Ok, so here's one thing about bash: to get it to run an *executable* (as opposed to a *script*), you need to say "bash -c FLEXPART_GFORTRAN". You might try strace on that. In addition to the objdump suggestion. I have a moment to expand on this a little.

Re: Problem with execution of binary file

Ok, so here's one thing about bash: to get it to run an *executable* (as opposed to a *script*), you need to say "bash -c FLEXPART_GFORTRAN". You might try strace on that. In addition to the objdump suggestion. Regards -- EM -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Problem with execution of binary file

Edvardsen Kåre writes: > Here is a few lines of "od -b" output from both the working and bad > binary, respectively. [...] Maybe more fruitful would be 'objdump -fp' run on both good and bad versions? ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http

Re: Problem with execution of binary file

On to., 2011-11-03 at 08:21 -0500, Eliot Moss wrote: > Someone more expert than I am may be able to say more > (or correct me if I'm wrong), but it appears that bash > opened the file, read 80 bytes, and didn't like what it > saw. So: What does "file FLEXPART_GFORTRAN.exe" say > about the file? Or

Re: Problem with execution of binary file

Someone more expert than I am may be able to say more (or correct me if I'm wrong), but it appears that bash opened the file, read 80 bytes, and didn't like what it saw. So: What does "file FLEXPART_GFORTRAN.exe" say about the file? Or maybe you could give us the first few lines from "od -b FLEXPA

Re: Problem with execution of binary file

On to., 2011-11-03 at 14:01 +0100, Edvardsen Kåre wrote: > On Nov 3 12:20, Edvardsen KÃre wrote: > > I keep getting the "cannot execute binary file" and don't understand > > why. I have compiled same software on two different machines, but only > > one of the binaries work (it works on both machin

Re: Problem with execution of binary file

On Nov 3 12:20, Edvardsen Kåre wrote: > I keep getting the "cannot execute binary file" and don't understand > why. I have compiled same software on two different machines, but only > one of the binaries work (it works on both machines). The successful > machine is a HP laptop with W7 Pro, the oth