public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jonathan Kelly <jonkelly@fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Mingw build problem for TCL
Date: Sun, 21 Jul 2013 07:11:00 -0000	[thread overview]
Message-ID: <51EB6CE3.9050403@fastmail.fm> (raw)
In-Reply-To: <20130720110044.GN20871@calimero.vinschen.de>

On 20/07/2013 9:00 PM, Corinna Vinschen wrote:
> On Jul 20 08:08, Jonathan Kelly wrote:
>> On 19/07/2013 5:55 PM, Corinna Vinschen wrote:
>>> On Jul 19 11:47, Jonathan Kelly wrote:
>>>> Hi,
>>>>
>>>> sorry if this isn't the correct place. I have previously used the
>>>> mingw-* packages to create a Windows compile of tcl8.6.0, but
>>>> currently it doesn't work. It compiles without error as far as I can
>>>> see, but when you try to run the executable (tclsh8.6.0.exe) it
>>>> returns immediately with code 127.
>>>> (PS ... I have tried it with the current mingw/msys system directly,
>>>> and that compiles OK.)
>>>> -------
>>>> $ uname -a
>>>> CYGWIN_NT-6.1-WOW64 jon-Z930 1.7.21(0.267/5/3) 2013-07-15 12:17 i686 Cygwin
>>>>
>>>> $ cygcheck -c | fgrep mingw
>>>> mingw-binutils           2.23.1-1             OK
>>>> mingw-gcc-core           4.7.3-1              OK
>>>> mingw-gcc-g++            4.7.3-1              OK
>>>> mingw-pthreads           20110507-2           OK
>>>> mingw-runtime            4.0-1                OK
>>>> mingw-w32api             4.0-1                OK
>>>>
>>>> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-mingw32 --prefix=/Tcl
>>>> ... cut ...
>>>>
>>>> $ make binaries
>>>> ... cut ...
>>>> i686-pc-mingw32-gcc -O2 -fomit-frame-pointer -DUNICODE -D_UNICODE
>>>> tclAppInit.o libtcl86.a libtclstub86.a -lnetapi32 -lkernel32
>>>> -luser32 -ladvapi32 -lws2_32
>>>> /cygdrive/c/src/tcl8.6.0/compat/zlib/win32/zdll.lib \
>>>>          tclsh.res.o -o tclsh86.exe -mconsole  -pipe
>>>>
>>>> $ echo $?
>>>> 0
>>>>
>>>> $ ./tclsh86.exe
>>>>
>>>> $ echo $?
>>>> 127
>>> Does it run correctly when started from CMD?
>>>
>>>
>>> Corinna
>>>
>> Not. Comes up with error "The application was unable to start
>> correctly (0xc0000022).
> Then Earnie is right.  This has nothing to do with Cygwin itself, but
> with the Mingw stuff.  This is probably best discussed on a Mingw.Org
> ML.
> Alternatively you could try to build this with the mingw-w64 cross
> toolchains and if it doesn't work, discuss it on their MLs.
>
>
> Corinna
>
No, it's not - it compiles and runs as it should when I use the Mingw 
directly. It's what I'm using now. I was just trying to give back a 
little by reporting a problem.

Thanks anyway.

--
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:[~2013-07-21  5:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  6:18 Jonathan Kelly
2013-07-19 10:06 ` Corinna Vinschen
2013-07-20 11:00   ` Earnie Boyd
2013-07-20 18:40   ` Jonathan Kelly
2013-07-20 19:48     ` Corinna Vinschen
2013-07-21  7:11       ` Jonathan Kelly [this message]
2013-07-22 15:30         ` Charles Wilson
2013-07-22 15:46           ` Corinna Vinschen
2013-07-23  0:25 Jonathan Kelly
2013-07-23 12:49 ` Arjen Markus

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=51EB6CE3.9050403@fastmail.fm \
    --to=jonkelly@fastmail.fm \
    --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).