cygwin | Business clients
Hi cygwin, Would you like to connect with Key Decision Makers from companies currently using VMware Software? The contacts were verified & updated last month for all marketing initiatives. Do let us know your current focus as requested below and I shall revert back with the volume of contacts, samples and a quote for your review; Target Technology:?, Target Job Titles:_?, Target Geography:___? Look forward to your feedback. Thanks & Regards, Bob Watkins Business Development -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [PATCH 0/2] Improvements in configure options for reducing dependencies
On Dec 14 17:30, Jon Turney wrote: > Jon Turney (2): > Cygwin: FAQ: Mention configure options to build with reduced > dependencies > Cygwin: configure: Add option to disable building 'dumper' > > winsup/configure.ac| 8 +--- > winsup/doc/faq-programming.xml | 16 > 2 files changed, 17 insertions(+), 7 deletions(-) LGTM. Thanks, Corinna
Re: [PATCH] Cygwin: Improve FAQ on early breakpoint for ASLR
On 11/12/2022 14:45, Johannes Schindelin wrote:
On December 11, 2022 2:54:02 PM GMT+01:00, Jon Turney
wrote:
On 05/12/2022 15:23, Johannes Schindelin wrote:
On Mon, 28 Nov 2022, Corinna Vinschen wrote:
On Nov 28 13:00, Jon Turney wrote:
On 15/11/2022 10:46, Corinna Vinschen wrote:
It would be great if we could get used to using the same syntax as the
Linux kernel project to document stuff. I'm trying to follow their lead
for a while. For fixes to former commits, it looks like this in the
kernel, at the end of the commit message:
Fixes: 123456789012 ("title of commit 123456789012")
Yeah, core.abbrev is 12 digits. I'm using this setting for quite some
time locally.
Sounds good. Is there some script to automate generating this kind of
comment from a commit-id?
I don't think so, at least I don't see anything like that in git docs...
It's note _quite_ what you asked for, but `git show --pretty=reference -s
` (https://git-scm.com/docs/git-show#_pretty_formats) gives you
_almost_ what you are looking for.
But you can always call `git show -s --format='%h ("%s")' `, and
even configure an alias for this:
git config --global alias.pretty-print-commit \
"-c core.abbrev=12 show -s --format='%h (\"%s\")'"
Thanks!
I added '-c core.pager=', but this is what I was looking for, to save a
bit of copying and pasting and editing.
Better use `git -P`, then... (see
https://git-scm.com/docs/git#Documentation/git.txt--P for full details)
I started off with that, but that fails when used with:
fatal: alias 'pretty-print-commit' changes environment variables.
You can use '!git' in the alias to do this
... which I'm sure tells me the right way to write this :)
[PATCH 1/2] Cygwin: FAQ: Mention configure options to build with reduced dependencies
--- winsup/doc/faq-programming.xml | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index 632d1a173..a24b781cf 100644 --- a/winsup/doc/faq-programming.xml +++ b/winsup/doc/faq-programming.xml @@ -679,14 +679,21 @@ rewriting the runtime library in question from specs... installed; you at least need gcc-g++, make, automake, autoconf, git, perl, +cocom and patch. + + + +Additionally, building the dumper utility requires gettext-devel, libiconv-devel -zlib-devel, cocom and patch. +zlib-devel. -Building for 64-bit Cygwin also requires -mingw64-x86_64-gcc-g++ and -mingw64-x86_64-zlib. +Building those Cygwin utilities which are not themselves Cygwin programs +(e.g. cygcheck and strace) also requires +mingw64-x86_64-gcc-g++ and mingw64-x86_64-zlib. +Building these programs can be disabled with the --without-cross-bootstrap +option to configure. -- 2.39.0
[PATCH 2/2] Cygwin: configure: Add option to disable building 'dumper'
Rather than guessing, based on just the presence of libbfd, add an explicit configuration option, to build dumper or not, defaulting to building it. This might have some use when bootstrapping Cygwin for a new architecture, or when building your own Cygwin-targetted cross-compiler, rather than installing one from the copr, along with the dependencies of libbfd. --- winsup/configure.ac| 8 +--- winsup/doc/faq-programming.xml | 3 ++- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/winsup/configure.ac b/winsup/configure.ac index 9205a8886..7a2121dae 100644 --- a/winsup/configure.ac +++ b/winsup/configure.ac @@ -111,10 +111,12 @@ AM_CONDITIONAL(CROSS_BOOTSTRAP, [test "x$with_cross_bootstrap" != "xyes"]) AC_EXEEXT -AC_CHECK_LIB([bfd], [bfd_init], [true], -AC_MSG_WARN([Not building dumper.exe since some required libraries or headers are missing])) +AC_ARG_ENABLE([dumper], + [AS_HELP_STRING([--disable-dumper], [do not build the 'dumper' utility])], + [build_dumper=$enableval], + [build_dumper=yes]) -AM_CONDITIONAL(BUILD_DUMPER, [test "x$ac_cv_lib_bfd_bfd_init" = "xyes"]) +AM_CONDITIONAL(BUILD_DUMPER, [test "x$build_dumper" = "xyes"]) AC_CONFIG_FILES([ Makefile diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index a24b781cf..24c7f928e 100644 --- a/winsup/doc/faq-programming.xml +++ b/winsup/doc/faq-programming.xml @@ -685,7 +685,8 @@ installed; you at least need gcc-g++, Additionally, building the dumper utility requires gettext-devel, libiconv-devel -zlib-devel. +zlib-devel. Building this program can be disabled with the +--disable-dumper option to configure. -- 2.39.0
[PATCH 0/2] Improvements in configure options for reducing dependencies
Jon Turney (2): Cygwin: FAQ: Mention configure options to build with reduced dependencies Cygwin: configure: Add option to disable building 'dumper' winsup/configure.ac| 8 +--- winsup/doc/faq-programming.xml | 16 2 files changed, 17 insertions(+), 7 deletions(-) -- 2.39.0
Re: Long lines in posts to this mailing list
On Wed, Dec 14, 2022 at 10:53:47AM +, Fergus Daly via Cygwin wrote: > What causes long lines without word wrap in posts to this list (such as the > immediately preceding > "gcc v.11.3.0 failing") and how can they be avoided? > (They are very inconvenient - sorry!) This is entirely down to your email client. The Cygwin mailing list won't be doing anything to change how text is wrapped. You'll need to either configure your mail client to properly wrap plain text emails, or switch to a mail client that has that configuration (or does it sensibly by default). Personally, I like Neomutt, but there are *lots* of other options. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Long lines in posts to this mailing list
What causes long lines without word wrap in posts to this list (such as the immediately preceding "gcc v.11.3.0 failing") and how can they be avoided? (They are very inconvenient - sorry!) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
gcc v.11.3.0 failing - possible cause gcc or libreadline.a?
In a gcc build script terminating with the instruction
gcc -w -static -o myexe -O3 ./myarchive.a -lreadline -lncurses -lm
I have suddenly started getting very many instances of both of
ld: /usr/src/debug/readline-8.2-2/terminal.c:nn various: undefined
reference to `{various}'
ld: /usr/src/debug/readline-8.2-2/display.c:nn various: undefined reference
to `{various}'
and the build fails.
It's a while since I attempted this build of myexe (myarchive has been
unaltered for years) and the attempt is triggered by a reported bug in gcc -pg
after update that has been corrected.
I don't know whether it is a change in readline (libreadline.a) or gcc that has
possibly caused the glitch (and obviously I cannot and do not expect anybody to
debug my build for me) but is this glitch familiar to anybody through current
or previous experience, or by appearance, that means you could point to cause
or possible cause?
Thank you!
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Strange behavior when executing programs
On Dec 14 06:38, Frank Redeker via Cygwin wrote: > > > Am 12/13/2022 um 10:51 AM schrieb Corinna Vinschen: > > On Dec 12 14:09, Corinna Vinschen via Cygwin wrote: > > > On Dec 12 13:46, Frank Redeker via Cygwin wrote: > > > > Am 12/12/2022 um 1:12 PM schrieb Corinna Vinschen: > > > > > On Dec 12 11:21, Frank Redeker via Cygwin wrote: > > > > > > $ pwd > > > > > > /cygdrive/s/ado > > > > > > > > > > > > $ realpath /cygdrive/s/ado/msadox.dll > > > > > > /cygdrive/s/ado/msadox.dll > > > > > > > > > > > > $ realpath msadox.dll > > > > > > /cygdrive/c/Program Files/Common Files/System/ado/msadox.dll > > > > > > [...] > > > However, a generic solution would be preferrable, and a local patch > > > to your scripts would be the better workaround for now. > > > > Please test cygwin-3.5.0-0.30.g5ba5e09b9d39. It contains a patch > > trying to workaround the problem. > > > > > > Thanks, > > Corinna > Hello Corinna, > > thanks for your patch. It works as expected. > > $ uname -a > CYGWIN_NT-10.0-22000 W11-DEVELOP 3.5.0-0.30.g5ba5e09b9d39.x86_64 2022-12-12 > 21:37 UTC x86_64 Cygwin > > $ pwd > /cygdrive/s/ado > > $ realpath msadox.dll > /cygdrive/s/ado/msadox.dll > > $ sample.exe msadox.dll > [msadox.dll] -> [S:\ado\msadox.dll] Great, thanks for testing! Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
