From: Jose Isaias Cabrera <jicman@outlook.com>
To: Michael Soegtrop <MSoegtrop@yahoo.de>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Creating the sqlite3.exe stand-alone w/o cygwin dependency
Date: Sat, 10 Dec 2022 18:00:40 +0000 [thread overview]
Message-ID: <DB9P251MB0063D46AB1B34F75B4FAB365DE1F9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <77194e33-0dcb-f0b0-906b-0e75c38b98de@yahoo.de>
On December 10, 2022 10:20 AM, Michael Soegtrop expressed:
>
> > The problem happens after I move that sqlite3.exe to C:\bin directory.
>
> very likely quite a few of the MinGW shared libraries supplied by cygwin are
> missing - you need to copy these as well. You can use the `ldd` tool on the
Very interesting:
$ ldd sqlite3.exe
ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffc1d6f0000)
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x778c0000)
wow64.dll => /cygdrive/c/Windows/System32/wow64.dll (0x7ffc1c830000)
wow64win.dll => /cygdrive/c/Windows/System32/wow64win.dll (0x7ffc1d540000)
Why are there two ntdll.dll files? Never mind. :-)
These reported DLL are in the search path, and also moving these to the executable folder still gives the same error. I also moved the sqlite3.exe file from the built folder to the previous folder in the Cygwin environment, and the same problem happens:
jcabrera@JIC ~/build/sqlite/SQLite-060eb284
$ mv sqlite3.exe ..
jcabrera@JIC ~/build/sqlite/SQLite-060eb284
$ cd ..
jcabrera@JIC ~/build/sqlite
$ ./sqlite3
jcabrera@JIC ~/build/sqlite
$ ./sqlite3.exe
jcabrera@JIC ~/build/sqlite
Well, let's say that nothing happens. So, it's something to do with the built command that only allows the sqlite3.exe to be run in the folder built folder and no-where else.
next prev parent reply other threads:[~2022-12-10 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 21:34 Jose Isaias Cabrera
2022-12-09 23:33 ` Eliot Moss
2022-12-10 2:43 ` Jose Isaias Cabrera
2022-12-10 14:47 ` Eliot Moss
2022-12-10 15:36 ` Cristobal Escamilla Cavazos
2022-12-10 16:35 ` Jose Isaias Cabrera
2022-12-10 14:42 ` Ken Brown
2022-12-10 15:20 ` Michael Soegtrop
2022-12-10 18:00 ` Jose Isaias Cabrera [this message]
2022-12-11 3:31 ` Jose Isaias Cabrera
2022-12-11 10:23 ` Michael Soegtrop
2022-12-11 20:03 ` Jose Isaias Cabrera
2022-12-11 20:41 ` Michael Soegtrop
2022-12-12 23:22 ` Jose Isaias Cabrera
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=DB9P251MB0063D46AB1B34F75B4FAB365DE1F9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM \
--to=jicman@outlook.com \
--cc=MSoegtrop@yahoo.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).