public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: cygwin@cygwin.com
Subject: Re: running self compiled 32 bit binary on 64 bit Windows?
Date: Fri, 08 Jun 2018 13:42:00 -0000	[thread overview]
Message-ID: <20180608134248.GC20898@rus.uni-stuttgart.de> (raw)
In-Reply-To: <ec20b090-01b8-c6fd-71a3-32165e11bed4@gmail.com>

On Wed 2018-06-06 (16:12), cyg Simple wrote:

> > On Windows 7 32 bit I have compiled some binaries by myself.
> 
> Help us help you by giving us how you compiled these and with what set
> of tools.

jed comes with a BIG makefile.
When I start it, it outputs:

/sw/src/jed-0.99.20-116: make
cd src; make jed
make[1]: Entering directory '/sw/src/jed-0.99.20-116/src'
gcc -O -I/sw/cygwin-7_32/slang-2.3.1-88/include -L/sw/cygwin-7_32/slang-2.3.1-88/lib   -DSLANG_DLL=1 -Dunix -DJED  -I/sw/cygwin-7_32/slang-2.3.1-88/include  /sw/src/jed-0.99.20-116/src/chkslang.c -o /sw/src/jed-0.99.20-116/src/objs/chkslang   -L/sw/cygwin-7_32/slang-2.3.1-88/lib -lslang    -lutil  -lm -ldl
if /sw/src/jed-0.99.20-116/src/objs/chkslang jed 20203 ;\
then exit 0; else rm -f /sw/src/jed-0.99.20-116/src/objs/chkslang; exit 1; fi
cd /sw/src/jed-0.99.20-116/src/objs; gcc -c -O -I/sw/cygwin-7_32/slang-2.3.1-88/include -L/sw/cygwin-7_32/slang-2.3.1-88/lib   -DSLANG_DLL=1 -Dunix -DJED  -I/sw/cygwin-7_32/slang-2.3.1-88/include  /sw/src/jed-0.99.20-116/src/buffer.c
(...)


> > I can run them there but not on a Windows 8 64 bit: no (error) message,
> > nothing happens.
> > 
> 
> In what shell are you running these (Cygwin bash, cmd.exe, etc)?

Cygwin bash


> What happens if you use cmd.exe?

Currently I cannot run cmd.exe, it crashes.
Maybe there is the problem?


> > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
> > CYGWIN_NT-6.3 WIN-7T5P92ALEEB 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
> > 
> > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ll jed
> > -rwxr-xr-x  admin    None     480,235 2018-04-10 11:58:59 jed
> > 
> > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: file jed
> > jed: PE32 executable (console) Intel 80386, for MS Windows
> > 
> > admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed
> >         ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffe0e520000)
> >         ??? => ??? (0x77330000)
> >         wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d0000)
> >         wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x77260000)
> >         wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x77320000)
> >         
> 
> No mention of Cygwin in this list so you must have used a non-cygwin
> tool to build the package.

No, I have used cygwin gcc, I have no other compilers!


> Try:
> cmd /c start cmd

A windows pops up and immediatelly closes.



-- 
Ullrich Horlacher              Server und Virtualisierung
Rechenzentrum TIK         
Universitaet Stuttgart         E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    http://www.tik.uni-stuttgart.de/
REF:<ec20b090-01b8-c6fd-71a3-32165e11bed4@gmail.com>

--
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

  reply	other threads:[~2018-06-08 13:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 11:50 Ulli Horlacher
2018-06-06 12:05 ` Markus Hoenicka
2018-06-06 16:05 ` Andrey Repin
2018-06-06 16:42   ` Ulli Horlacher
2018-06-06 17:50     ` Andrey Repin
2018-06-06 16:25 ` Soegtrop, Michael
2018-06-06 16:29   ` Soegtrop, Michael
2018-06-06 17:50   ` Andrey Repin
2018-06-06 20:26     ` cyg Simple
2018-06-06 22:05       ` Andrey Repin
2018-06-08 13:31         ` Ulli Horlacher
2018-06-08 13:37           ` cyg Simple
2018-06-08 13:45             ` Ulli Horlacher
2018-06-08 13:52               ` Soegtrop, Michael
2018-06-08 13:56               ` cyg Simple
2018-06-08 16:50               ` Andrey Repin
2018-06-08 18:20               ` Csaba Raduly
2018-06-08 13:43           ` Ulli Horlacher
2018-06-08 13:43           ` Soegtrop, Michael
2018-06-08 13:52             ` Ulli Horlacher
2018-06-08 16:50               ` Andrey Repin
2018-07-09  0:21                 ` Ulli Horlacher
2018-07-09  2:20                   ` Andrey Repin
2018-07-09  6:22                     ` Brian Inglis
2018-07-09  6:29                     ` Ulli Horlacher
2018-07-14 15:41                   ` Achim Gratz
2018-08-17 10:29                     ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Ulli Horlacher
2018-08-17 10:58                       ` distributing preconfigured cygwin john doe
2018-08-17 17:05                       ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Andrey Repin
2018-08-17 19:49                       ` distributing preconfigured cygwin Achim Gratz
2018-08-29 11:09                         ` Ulli Horlacher
2018-08-29 11:31                           ` Andrey Repin
2018-08-29 12:08                           ` john doe
2018-08-30 12:35                     ` running self compiled 32 bit binary on 64 bit Windows? Ulli Horlacher
2018-08-30 13:55                       ` Marco Atzeri
2018-08-30 13:59                       ` Andrey Repin
2018-08-30 19:20                         ` Ulli Horlacher
2018-08-30 21:06                           ` Ulli Horlacher
2018-08-31  8:58                             ` Andrey Repin
2018-08-31  8:35                       ` Achim Gratz
2018-06-08 13:19     ` Ulli Horlacher
2018-06-08 13:28       ` Soegtrop, Michael
2018-06-08 13:34       ` cyg Simple
2018-06-08 13:54         ` Ulli Horlacher
2018-06-08 19:05       ` Achim Gratz
2018-06-06 20:13 ` cyg Simple
2018-06-08 13:42   ` Ulli Horlacher [this message]
2018-06-08 17:44     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180608134248.GC20898@rus.uni-stuttgart.de \
    --to=framstag@rus.uni-stuttgart.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).