Re: setup and mintty (was Re: New setup.exe release?)
On 24 May 2011 10:50, Corinna Vinschen wrote:
On May 24 11:15, Corinna Vinschen wrote:
On May 23 21:14, Andy Koppe wrote:
On 23 May 2011 12:50, Corinna Vinschen wrote:
And who's going to create the patches?
I suppose that should be me, but my spare time is rather limited at
the moment and I still owe a patch or two for other things.
I'm just trying a setup.exe patch which creates Cygwin Terminal
desktop and start menu entries which point to mintty -. I just
have to get rid of my build environment problems...
Ok, here's my patch. It just replaces the Desktop and Start Menu
entries with Cygwin Terminal entries pointing to mintty - and
leaves Cygwin.bat untouched. Is that ok with everyone?
Index: desktop.cc
===
RCS file: /cvs/cygwin-apps/setup/desktop.cc,v
retrieving revision 2.55
diff -u -p -r2.55 desktop.cc
--- desktop.cc 19 Nov 2010 15:49:54 - 2.55
+++ desktop.cc 24 May 2011 09:47:51 -
@@ -78,7 +78,8 @@ DesktopSetupPage::DesktopSetupPage ()
static void
make_link (const std::string linkpath,
const std::string title,
- const std::string target)
+ const std::string target,
+ const std::string arg)
{
std::string fname = linkpath + / + title + .lnk;
@@ -93,10 +94,10 @@ make_link (const std::string linkpath,
std::string exepath;
std::string argbuf;
- if (!is_legacy)
+ if (IsWindowsNT ())
{
exepath = target;
- argbuf = ;
+ argbuf = arg;
}
else
{
@@ -105,6 +106,8 @@ make_link (const std::string linkpath,
GetWindowsDirectory (windir, sizeof (windir));
exepath = std::string(windir) + \\command.com;
argbuf = /E:4096 /c + target;
+ if (arg.size ())
+ argbuf += + arg;
}
msg (make_link_2 (%s, %s, %s, %s),
@@ -115,7 +118,8 @@ make_link (const std::string linkpath,
}
static void
-start_menu (const std::string title, const std::string target)
+start_menu (const std::string title, const std::string target,
+ const std::string arg)
{
LPITEMIDLIST id;
int issystem = (root_scope == IDC_ROOT_SYSTEM) ? 1 : 0;
@@ -137,11 +141,12 @@ start_menu (const std::string title, co
}
// end of Win95 addition
path += /Cygwin;
- make_link (path, title, target);
+ make_link (path, title, target, arg);
}
static void
-desktop_icon (const std::string title, const std::string target)
+desktop_icon (const std::string title, const std::string target,
+ const std::string arg)
{
char path[MAX_PATH];
LPITEMIDLIST id;
@@ -161,7 +166,7 @@ desktop_icon (const std::string title,
msg (Desktop directory for deskop link changed to: %s, path);
}
// end of Win95 addition
- make_link (path, title, target);
+ make_link (path, title, target, arg);
}
static void
@@ -243,15 +248,17 @@ do_desktop_setup ()
make_cygwin_bat ();
+ std::string target;
+
+ target = is_legacy ? batname : backslash (cygpath (/bin/mintty));
+
if (root_menu)
- {
- start_menu (Cygwin Bash Shell, batname);
- }
+ start_menu (is_legacy ? Cygwin Bash Shell : Cygwin Terminal, target,
+ is_legacy ? : -);
if (root_desktop)
- {
- desktop_icon (Cygwin, batname);
- }
+ desktop_icon (is_legacy ? Cygwin : Cygwin Terminal, target,
+ is_legacy ? : -);
}
static int da[] = { IDC_ROOT_DESKTOP, 0 };
@@ -425,8 +432,11 @@ DesktopSetupPage::OnActivate ()
else
{
root_menu =
- check_startmenu (Cygwin Bash Shell,
- backslash (cygpath (/cygwin.bat)));
+ is_legacy
+ ? check_startmenu (Cygwin Bash Shell,
+ backslash (cygpath (/cygwin.bat)))
+ : check_startmenu (Cygwin Terminal,
+ backslash (cygpath (/bin/mintty)));
}
if (NoDesktopOption)
@@ -436,7 +446,10 @@ DesktopSetupPage::OnActivate ()
else
{
root_desktop =
- check_desktop (Cygwin, backslash (cygpath (/cygwin.bat)));
+ is_legacy
+ ? check_desktop (Cygwin, backslash (cygpath (/cygwin.bat)))
+ : check_desktop (Cygwin Terminal,
+ backslash (cygpath (/bin/mintty)));
}
}
Ah, sorry, I didn't realise that the desktop shortcut at the moment
was simply called Cygwin rather than Cygwin Bash Shell. I suppose
that could just stay like that actually.
Also, since the start menu shortcut already is inside the Cygwin
folder, just Terminal rather than Cygwin Terminal would be nice
and crisp there.
Andy
Re: setup and mintty (was Re: New setup.exe release?)
Am 25.05.2011 09:43, schrieb Andy Koppe: ... Ah, sorry, I didn't realise that the desktop shortcut at the moment was simply called Cygwin rather than Cygwin Bash Shell. I suppose that could just stay like that actually. Also, since the start menu shortcut already is inside the Cygwin folder, just Terminal rather than Cygwin Terminal would be nice and crisp there. I think common usage is to give shortcuts rather a complete name. That's also better if people move them around, placing a copy on the desktop etc. And since bash shell runs in both command windows (is that a common name?), I think the previous proposal Cygwin Console and Cygwin Terminal is the best to distinguish them. -- Thomas
src/winsup/cygwin ChangeLog posix.sgml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-05-25 06:10:25 Modified files: winsup/cygwin : ChangeLog posix.sgml Log message: * posix.sgml (std-notes): Add missing para. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5370r2=1.5371 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/posix.sgml.diff?cvsroot=srcr1=1.67r2=1.68
src/winsup/doc ChangeLog legal.sgml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-05-25 06:29:23 Modified files: winsup/doc : ChangeLog legal.sgml Log message: * legal.sgml: Drop an old paragraph. Reactivate copyright note for documentation. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.350r2=1.351 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/legal.sgml.diff?cvsroot=srcr1=1.9r2=1.10
src/winsup/cygwin ChangeLog init.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-05-25 11:33:30 Modified files: winsup/cygwin : ChangeLog init.cc Log message: * init.cc (dll_entry): Reinstantiate wow64_test_stack_marker and previous stack tests. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5371r2=1.5372 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/init.cc.diff?cvsroot=srcr1=1.82r2=1.83
src/winsup/cygwin ChangeLog cygtls.h errno.cc ...
CVSROOT:/cvs/src Module name:src Changes by: er...@sourceware.org2011-05-25 18:47:32 Modified files: winsup/cygwin : ChangeLog cygtls.h errno.cc tlsoffsets.h Log message: perror: fix POSIX compliance and work with recent newlib change * cygtls.h (strerror_r_buf): New buffer. * errno.cc (strerror): Move guts... (_strerror_r): ...to new function demanded by newlib. (strerror_r): Don't clobber strerror buffer. (_user_strerror): Drop unused declaration. * tlsoffsets.h: Regenerate. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5372r2=1.5373 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygtls.h.diff?cvsroot=srcr1=1.70r2=1.71 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/errno.cc.diff?cvsroot=srcr1=1.83r2=1.84 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/tlsoffsets.h.diff?cvsroot=srcr1=1.45r2=1.46
src/winsup/doc ChangeLog new-features.sgml
CVSROOT:/cvs/src Module name:src Changes by: er...@sourceware.org2011-05-25 19:08:46 Modified files: winsup/doc : ChangeLog new-features.sgml Log message: * new-features.sgml (ov-new1.7.10): Document strerror changes. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.351r2=1.352 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/new-features.sgml.diff?cvsroot=srcr1=1.84r2=1.85
Re: fix perror POSIX compliance
On 05/24/2011 04:09 AM, Corinna Vinschen wrote: On May 23 17:28, Eric Blake wrote: This depends on the newlib patch: http://sourceware.org/ml/newlib/2011/msg00215.html In fact, if that patch goes in, then this one is required to avoid a link failure; this one can probably go in first but makes no difference to perror without the newlib patch. You can apply this together with the newlib patch. But please make sure that you also tested the newlib-only implementation. Yep, tested both, and now pushed. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: 1.7.9: Problem with line endings of Perl output redirected to a file with textmode mounting
Tue, 24 May 2011, Reini Urban wrote: Yes, this looks like a PerlIO buffering bug for MSWin32 and cygwin. The last char of the buffer is not stored when checking the first char of the new buffer. I think first we have to provide a sample test case to perl core. Thank you for your response. Sven -- Mit freundlichen Grüßen Dipl. Inform. Sven Severus Softwareentwicklung -- HIMA Paul Hildebrandt GmbH + CO KG Abt: Entwicklung Software Albert-Bassermann-Strasse 28 68782 Bruehl Germany Tel: +49 6202 709-289 Fax: +49 6202 709-299 E-Mail: s.seve...@hima.com Internet: www.hima.de -- HIMA Paul Hildebrandt GmbH + Co KG, Albert-Bassermann-Str. 28, 68782 Bruehl bei Mannheim Kommanditgesellschaft, Sitz Bruehl, Deutschland - Registergericht Mannheim HRA 421017 Ust-ID: DE 144286400, St.Nr: 43038 00190 Persoenlich haftende Gesellschafterin Paul Hildebrandt Verwaltungsgesellschaft mbH, Sitz Bruehl, Deutschland - Registergericht Mannheim HRB 420588 Geschaeftsfuehrer: Dipl.-Betriebswirt Steffen Philipp -- 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
Re: Using Cygwin Emacs
On 16.05.2011 4:27, Sayth Renshaw wrote:
Before I venture down this path are there many people using
this package? Is it advantageous to use this package(cygwin)?
Advantage is in full integration of Emacs and Cygwin tools.
Watching this list I found that many people use Cygwin Emacs package.
Or is there not much upside to a user using the default 23.2 zip package?
I use native GNU Emacs. It's GIU look more pretty and Emacs understand
Windows-style path is good thing when you need goto-error feature
for MSVC compiler, etc...
With cygwin-mount.el native Emacs understand Cygwin-style path.
Also I use:
(when (eq system-type 'windows-nt)
;; Workaround for Cygwin shell, when set 'CYGWIN=noglob'. By default
'shell-quote-argument'
;; quoted by double '\' chars, this cause failure.
(defun shell-quote-argument (argument)
(concat ' argument ')
)
;; Workaround for Cygwin when 'shell-file-name' is 'bash'.
(setq null-device /dev/null)
)
;; Use shell from Cygwin/MinGW.
(setq shell-file-name bash)
(setenv SHELL /bin/bash)
(setq explicit-bash-args '(-i))
(setq explicit-sh-args '(-i))
and some utils like hg require wrapper to make it .exe. Just compile:
#include stdio.h
#include stdlib.h
#include string.h
#include unistd.h
#define MAX_STR_LEN 500
int main(int argc, char **argv)
{
char cmd[MAX_STR_LEN] = ;
char **cmdarg = malloc((argc+1) * sizeof(char *));
char *start, *end;
start = strrchr(*argv, '/');
if (start)
start++;
else
start = *argv;
end = strrchr(start, '.');
if (end) {
memcpy(cmd, start, end - start);
cmd[end - start] = '\0';
} else
strcpy(cmd, start);
for (int i = 0; i argc; i++)
cmdarg[i] = argv[i];
cmdarg[argc] = NULL;
return execvp(cmd, cmdarg);
}
and take name to executable as shell/perl/python/... script
with .exe suffix.
Also I have troubles with quoting of and {. For example
to make vc-hg.el work properly I patch it:
--- vc-hg.el2011-01-08 19:45:14.0 +0200
+++ vc-hg-new.el2011-03-17 17:20:26.18750 +0200
@@ -218,7 +218,7 @@
vc-hg-program nil t nil
--config alias.parents=parents
--config defaults.parents=
-parents --template {rev} (file-relative-name
file)))
+parents --template \\{rev\\} (file-relative-name
file)))
;; Some problem happened. E.g. We can't find an `hg'
;; executable.
(error nil)))
@@ -324,7 +324,7 @@
(defun vc-hg-revision-table (files)
(let ((default-directory (file-name-directory (car files
(with-temp-buffer
- (vc-hg-command t nil files log --template {rev} )
+ (vc-hg-command t nil files log --template \\{rev\\} )
(split-string
(buffer-substring-no-properties (point-min) (point-max))
That's all you need to friend native Emacs with Cygwin.
I am happy with this setup for 3 year with native Emacs from 22.1 to 23.3.
--
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
Re: Error building run2 from source package in win7
On Tue, May 24, 2011 at 05:10:37PM -0400, Charles Wilson wrote:
On 5/24/2011 3:53 PM, David Sastre wrote:
On Tue, May 24, 2011 at 02:59:11PM -0400, Charles Wilson wrote:
A-ha!
Don't set -Werror as part of $CC, set it in $CFLAGS instead.
Which is what is defined in the *.cygport's src_compile func:
src_compile() {
cd ${S}
cygautoreconf
cd ${B}
cygconf CFLAGS=-Wall -Werror
cygmake
}
And I'm doing nothing but running 'cygport *.cygport all'.
Well, Eric is the real expert, and he says don't set the warning flags
until the cygmake line, so that's first. However, I assume the
incantation above worked in the past for the original author of the
.cygport(5) file, so why's it breaking for you?
Second, why does the STC below not work for you, when it worked for me?
for the same reasons (config.log):
configure:2563: gcc -c -Wall -Werror conftest.c 5
cc1: warnings being treated as errors
conftest.c: In function 'main':
conftest.c:38:10: error: 't' is used uninitialized in this function
conftest.c:54:23: error: 'b' may be used uninitialized in this
function
configure:2563: $? = 1
Well, looking at my config.log, I too have:
configure:2498: checking for an ANSI C-conforming const
configure:2563: gcc -c -Wall -Werror conftest.c 5
^
configure:2563: $? = 0
configure:2570: result: yes
but we already know that this conftest.c is not -Wall -Werror clean --
or, at least, that YOUR conftest.c is not clean.
Digging deeper in my configure, I find that the test uses the shell
function ac_fn_c_try_compile(), and that shell function has an
interesting bit of code:
1340 test -z $ac_c_werror_flag ||
1341 test ! -s conftest.err
1342} test -s conftest.$ac_objext; then :
1343 ac_retval=0
Hmmm...it's checking something to do with a Werror flag! Maybe there's
a workaround, but (a) is only activated if the -Werror is in CFLAGS, not
CC -- otherwise *I* would have passed the STC with CC='gcc -Wall
-Werror' but I didn't, and (b) its only present in specific (newer?)
versions of autoconf, and you and I are using different versions.
Here's the first 3 lines of my configure script:
1 #! /bin/sh
2 # Guess values for system-dependent variables and create Makefiles.
3 # Generated by GNU Autoconf 2.68.
What's yours say?
Autoconf version matches yours:
$ cygcheck -c autoconf2.5
Cygwin Package Information
Package VersionStatus
autoconf2.5 2.68-1 OK
$ head -3 configure
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.68 for run2 0.4.0.
Moving the -Werror flag to the cygmake step did the trick:
$ diff -u run2-0.4.0-1.cygport.orig run2-0.4.0-1.cygport
--- run2-0.4.0-1.cygport.orig 2009-12-29 07:30:19.0 +0100
+++ run2-0.4.0-1.cygport2011-05-25 11:11:51.13920 +0200
@@ -11,7 +11,7 @@
cd ${S}
cygautoreconf
cd ${B}
- cygconf CFLAGS=-Wall -Werror
- cygmake
+ cygconf CFLAGS=-Wall
+ cygmake CFLAGS=-Werror
}
checking for an ANSI C-conforming const... yes
I've been able to compile without problems.
Thanks for your time.
--
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56
signature.asc
Description: Digital signature
Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong
On 29/04/2011 2:35 PM, John Dong wrote: Reproducing this seems nondeterministic -- sometimes I can get it to happen in 5 minutes, other times it takes overnight. I've tried using a different shell (like dash), but it doesn't make a difference, leading me to suspect this to be a lower-level issue within the Cygwin DLL. It also seems to not happen for non-zero exit codes (e.g. checking that exiter.exe 1 returns 1 always seems to succeed), though I'm not 100% confident that I've tested this thoroughly enough. Again, I've not been able to reproduce this under Windows XP using any version of Cygwin, but I have been able to reproduce it on both 32-bit and 64-bit Windows 7. I'm not running anything special on this machine -- it's a fresh install of Windows 7 Professional, just with Cygwin installed. FWIW, we've been running into this as well. It appears to NOT be a problem with Cygwin 1.5 on Windows 7. It only started happening on Cygwin 1.7. As a result, we haven't had a reliable Windows 7 build machine for a while now because we use a Cygwin gmake process that compiles with MSVC. -Edward -- 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
Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong
On Wed, May 25, 2011 at 10:16:03AM -0400, Edward Lam wrote: On 29/04/2011 2:35 PM, John Dong wrote: Reproducing this seems nondeterministic -- sometimes I can get it to happen in 5 minutes, other times it takes overnight. I've tried using a different shell (like dash), but it doesn't make a difference, leading me to suspect this to be a lower-level issue within the Cygwin DLL. It also seems to not happen for non-zero exit codes (e.g. checking that exiter.exe 1 returns 1 always seems to succeed), though I'm not 100% confident that I've tested this thoroughly enough. Again, I've not been able to reproduce this under Windows XP using any version of Cygwin, but I have been able to reproduce it on both 32-bit and 64-bit Windows 7. I'm not running anything special on this machine -- it's a fresh install of Windows 7 Professional, just with Cygwin installed. FWIW, we've been running into this as well. It appears to NOT be a problem with Cygwin 1.5 on Windows 7. It only started happening on Cygwin 1.7. As a result, we haven't had a reliable Windows 7 build machine for a while now because we use a Cygwin gmake process that compiles with MSVC. As always: http://cygwin.com/acronyms#PTC -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ Good work. What mintty version is that though? It seems to be missing the fallback scheme to (rough) ASCII equivalents for the VT100 graphics characters. mintty-0.9.8-1 The difference MAY be that I didn't actually cat xgraphics each time after changing the font. I merely changed the font, while the earlier xgraphics result was viewable in the terminal. If the fallback scheme relies on actually changing the internally-stored character code, rather than changing which glyph is used to draw that character, then my technique would bypass the fallback. Consolas on Windows 7 indeed is much improved. Looks that way. -- Chuck -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. -- Cheers, Kein-Hong Man (esq.) Kuala Lumpur, Malaysia -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 25/05/2011 11:54 AM, KHMan wrote: On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Even unchecking 'hide fonts based on language settings' in 'font settings' didn't help (made a lot of other fonts appear, tho). (For now I'm using Lucida Console) Thanks, Ryan -- 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
can't compile under cygwin anymore, /usr/bin/ld: cannot find crt2.o etc
I have been compiling software under gcc3.4 under cygwin for some time now. I was having an issue, so I decided to re-install gcc in cygwin. All I did was select the three gcc packages for re-install. After the re-install, I am getting the following errors from the linker, /usr/bin/ld: cannot find crt2.o: No such file or directory /usr/bin/ld: cannot find -lmingw32 /usr/bin/ld: cannot find -lmoldname /usr/bin/ld: cannot find -lmingwex /usr/bin/ld: cannot find -lmsvcrt /usr/bin/ld: cannot find -lmingw32 /usr/bin/ld: cannot find -lmingw32 /usr/bin/ld: cannot find -lmoldname /usr/bin/ld: cannot find -lmingwex /usr/bin/ld: cannot find -lmsvcrt It's like the linker can't find the libraries anymore. I haven't changed my make, or anything else. I had this happen yesterday on another computer where all I did was to update cygwin in the normal fashion. I have the following packages installed, binutils 2.20.51-2 gcc-core 3.4.4-3 gcc-g++ 3.4.4-3 gcc-g77 3.4.4-3 gcc-mingw-core20050522-3 gcc-mingw-g++ 20050522-3 gcc-mingw-g77 20050522-3 libgcc1 4.3.4-4 libstdc++64.3.4-4 libstdc++6-devel 4.3.4-4 mingw-runtime 3.18-1 make Do you see anything that I'm missing. The cygwin package manager is pretty good, so I would be surprised if a re-install removed some required dependency, but anything is possible I guess. I would guess that it is more likely that the problem is having the version 4 libs, which may not be compatible with gcc3. The only options are 4.3.4 or 4.3.3. I will check an older machine and see if I can figure out what is different. LMHmedchem -- View this message in context: http://old.nabble.com/can%27t-compile-under-cygwin-anymore%2C--usr-bin-ld%3A-cannot-find-crt2.o-etc-tp31700534p31700534.html Sent from the Cygwin list mailing list archive at Nabble.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
Re: setup and mintty (was Re: New setup.exe release?)
On 5/26/2011 12:13 AM, Ryan Johnson wrote: On 25/05/2011 11:54 AM, KHMan wrote: On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Even unchecking 'hide fonts based on language settings' in 'font settings' didn't help (made a lot of other fonts appear, tho). Sorry, I'm on XP, did it the traditional copy-and-paste-in-Explorer way. Perhaps someone else has tried it on Win7... -- Cheers, Kein-Hong Man (esq.) Kuala Lumpur, Malaysia -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 25 May 2011 16:26, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ Good work. What mintty version is that though? It seems to be missing the fallback scheme to (rough) ASCII equivalents for the VT100 graphics characters. mintty-0.9.8-1 The difference MAY be that I didn't actually cat xgraphics each time after changing the font. I merely changed the font, while the earlier xgraphics result was viewable in the terminal. If the fallback scheme relies on actually changing the internally-stored character code, rather than changing which glyph is used to draw that character, then my technique would bypass the fallback. Yep, that explains it. Andy -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 25 May 2011 17:13, Ryan Johnson wrote: On 25/05/2011 11:54 AM, KHMan wrote: On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. Andy -- 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
Can't talk to X server through ssh tunnel after ~ 18 minutes
I ssh from my Cygwin box to a Linux machine (happens with Solaris machines too) and I can run X applications back to Cygwin/X without a problem. However, after a few minutes something happens to the tunnel and I can no longer put up any X windows: $ cat checks.sh #!/bin/bash while true; do date xclock sleep 2 killall xclock if [ $? != 0 ]; then echo Cannot talk to X Server anymore else sleep 60 fi done $ checkx.sh Tue May 24 09:48:43 PDT 2011 ./checkx.sh: line 12: 10927 Terminated xclock Tue May 24 09:49:45 PDT 2011 ./checkx.sh: line 12: 11393 Terminated xclock Tue May 24 09:50:47 PDT 2011 b./checkx.sh: line 12: 11592 Terminated xclock Tue May 24 09:51:49 PDT 2011 ./checkx.sh: line 12: 11782 Terminated xclock Tue May 24 09:52:51 PDT 2011 ./checkx.sh: line 12: 11977 Terminated xclock Tue May 24 09:53:53 PDT 2011 ./checkx.sh: line 12: 12161 Terminated xclock Tue May 24 09:54:55 PDT 2011 ./checkx.sh: line 12: 12345 Terminated xclock Tue May 24 09:55:57 PDT 2011 ./checkx.sh: line 12: 12534 Terminated xclock Tue May 24 09:56:59 PDT 2011 ./checkx.sh: line 12: 12723 Terminated xclock Tue May 24 09:58:01 PDT 2011 ./checkx.sh: line 12: 12912 Terminated xclock Tue May 24 09:59:03 PDT 2011 ./checkx.sh: line 12: 13142 Terminated xclock Tue May 24 10:00:05 PDT 2011 ./checkx.sh: line 12: 13345 Terminated xclock Tue May 24 10:01:07 PDT 2011 ./checkx.sh: line 12: 13578 Terminated xclock Tue May 24 10:02:09 PDT 2011 ./checkx.sh: line 12: 13843 Terminated xclock Tue May 24 10:03:11 PDT 2011 ./checkx.sh: line 12: 14074 Terminated xclock Tue May 24 10:04:13 PDT 2011 ./checkx.sh: line 12: 14260 Terminated xclock Tue May 24 10:05:16 PDT 2011 ./checkx.sh: line 12: 14455 Terminated xclock Tue May 24 10:06:18 PDT 2011 X connection to localhost:15.0 broken (explicit kill or server shutdown). xclock: no process killed Cannot talk to X Server anymore After this I cannot re-establish an X connection until I exit the ssh session and ssh back in again. Any ideas? (I'm gonna post this to both Cygwin and Cygwin-X as I'm not sure if this is a problem with ssh or a problem with X). -- a href=http://defaria.com;Andrew DeFaria/abr smallfont color=#99If a man says something in the woods and there are no women there, is he still wrong?/font/small -- 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
Re: Can't talk to X server through ssh tunnel after ~ 18 minutes
On 5/25/2011 12:43 PM, Andrew DeFaria said this: I ssh from my Cygwin box to a Linux machine (happens with Solaris machines too) and I can run X applications back to Cygwin/X without a problem. However, after a few minutes something happens to the tunnel and I can no longer put up any X windows: What arguments are you using to start the ssh session? -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 25/05/2011 12:55 PM, Andy Koppe wrote: On 25 May 2011 17:13, Ryan Johnson wrote: On 25/05/2011 11:54 AM, KHMan wrote: On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. I tried to say before that I have done that (I saw the closed bug about this and made sure to follow the instructions there). Unchecking that setting about language-specific hiding made a whole bunch of other (presumably Asian) fonts show up in mintty, but still no Liberation Mono. The font is officially installed, officially showing, and usable by just about everything except mintty. Most apps (like Word) picked it up immediately. Very odd... Ryan Ryan -- 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
Re: can't compile under cygwin anymore, /usr/bin/ld: cannot find crt2.o etc
On 5/25/2011 12:20 PM, LMHmedchem2 wrote: I have the following packages installed, gcc-mingw-core20050522-3 gcc-mingw-g++ 20050522-3 gcc-mingw-g77 20050522-3 Read the following announcement: http://cygwin.com/ml/cygwin-announce/2011-04/msg00015.html You'll need to do either 'CHOICE ONE' or 'CHOICE TWO' described there...or wait until next Monday/Tuesday when the new mingw-runtime, mingw-w32api, and other related packages are released. Also, if you go with choice one, you'll need to undo that (by re-installing gcc-mingw-core) after next week. -- Chuck -- 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
PostgreSQL Maintainer (Reini Urban)
Renei, Any chance that we'd see a PostgreSQL 9.x Cygwin package anytime soon? It's understood that all package maintainers are volunteers. If that isn't on your packaging list, do you have a set of detailed instructions for how a Cygwin user could get the PG 9.x source and produce an installable package on our own? Seems that most or all maintainers use Cygport, perhaps a general set of instructions already exists? Thank you. ==Keith -- 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
mintty fonts (was: Re: setup and mintty)
On 25 May 2011 19:05, Ryan Johnson wrote: How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. I tried to say before that I have done that (I saw the closed bug about this and made sure to follow the instructions there). Unchecking that setting about language-specific hiding made a whole bunch of other (presumably Asian) fonts show up in mintty, but still no Liberation Mono. I actually wasn't talking about that option, but the abilily to show/hide each font separately. But it doesn't sound like that's the issue anyway. The font is officially installed, officially showing, and usable by just about everything except mintty. Most apps (like Word) picked it up immediately. Right, I'm afraid that leaves me stumped, given it's fine here. Do you fancy messing with the mintty source code to see which flag on ChooseFont() is excluding that font? It's in select_font() in winctrls.c. I guess CF_FIXEDPITCHONLY is the prime candidate. Andy -- 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
Re: setup and mintty (was Re: New setup.exe release?)
Am 25.05.2011 20:05, schrieb Ryan Johnson: On 25/05/2011 12:55 PM, Andy Koppe wrote: On 25 May 2011 17:13, Ryan Johnson wrote: On 25/05/2011 11:54 AM, KHMan wrote: On 5/25/2011 11:26 PM, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ [snip snip] Consolas on Windows 7 indeed is much improved. Liberation Mono should get a mention too. It is hinted for the small font sizes, great for those who prefer old-style crisp hinted glyphs. I use it on mintty for Cygwin. How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. I tried to say before that I have done that (I saw the closed bug about this and made sure to follow the instructions there). Unchecking that setting about language-specific hiding made a whole bunch of other (presumably Asian) fonts show up in mintty, but still no Liberation Mono. The font is officially installed, officially showing, and usable by just about everything except mintty. Most apps (like Word) picked it up immediately. Very odd... I don't see it in the menu either, on XP. However, mintty -o Font=Liberation Mono works. -- Thomas -- 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
Re: mintty fonts (was: Re: setup and mintty)
On 25/05/2011 3:48 PM, Andy Koppe wrote: On 25 May 2011 19:05, Ryan Johnson wrote: How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. I tried to say before that I have done that (I saw the closed bug about this and made sure to follow the instructions there). Unchecking that setting about language-specific hiding made a whole bunch of other (presumably Asian) fonts show up in mintty, but still no Liberation Mono. I actually wasn't talking about that option, but the abilily to show/hide each font separately. But it doesn't sound like that's the issue anyway. The font is officially installed, officially showing, and usable by just about everything except mintty. Most apps (like Word) picked it up immediately. Right, I'm afraid that leaves me stumped, given it's fine here. Do you fancy messing with the mintty source code to see which flag on ChooseFont() is excluding that font? It's in select_font() in winctrls.c. I guess CF_FIXEDPITCHONLY is the prime candidate. Removing CF_FIXEDPITCHONLY indeed allows the font to show (and a whole pile of non fixed-pitch friends). Apparently the font version I downloaded (liberation-fonts-ttf-1.06.0.20100721) doesn't mark itself as fixed-pitch? When I select liberation mono, ChooseFont populates the LOGFONT with lfPitchAndFamily=0x32. MSDN says: The two low-order bits specify the pitch of the font and can be one of the following values. DEFAULT_PITCH FIXED_PITCH VARIABLE_PITCH Sure enough, grep-find over /usr/include/w32api shows: wingdi.h:380:#define VARIABLE_PITCH 2 I guess somebody needs to file a bug with fedorahosted.org, but I didn't see an obvious way to request an account with them. Do you have one by chance? Ryan -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 5/25/2011 1:17 AM, Andy Koppe wrote: Consolas on Windows 7 indeed is much improved. In the original thread over on cygwin-apps, I had written: Yep, works fine with Lucida Console. I was using Consolas, which IMO looks better...but yep, it appears to be missing the glyphs -- although rumor has it that MS added the glyphs in their W7 version of this font. Since I'm running Vista and XP, well... I probably knew that at one point. Maybe. I guess I *did* know this at one point: http://cygwin.com/ml/cygwin/2009-10/msg00226.html FWIW, compare the various versions of consolas: 5.00 -- shipped with Vista http://www.microsoft.com/typography/fonts/font.aspx?FMID=1537 1.00 -- included in the Office 2007 compatibility pack http://www.microsoft.com/downloads/details.aspx?familyid=941B3470-3AE9-4AEE-8F43-C6BB74CD1466displaylang=en http://www.microsoft.com/typography/fonts/font.aspx?FMID=1293 and 5.22, Windows7's version: http://www.microsoft.com/typography/fonts/font.aspx?FMID=1723 which is not, AFAICT, available gratis. -- Chuck -- 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
Re: Can't talk to X server through ssh tunnel after ~ 18 minutes
On 5/25/2011 11:01 AM, Tim Daneliuk wrote: On 5/25/2011 12:43 PM, Andrew DeFaria said this: I ssh from my Cygwin box to a Linux machine (happens with Solaris machines too) and I can run X applications back to Cygwin/X without a problem. However, after a few minutes something happens to the tunnel and I can no longer put up any X windows: What arguments are you using to start the ssh session? The only argument is -X. Like I said, I was able to put up X windows through the ssh tunnel. Then, after some, it stops working - consistently. -- Andrew DeFaria http://defaria.com I didn't climb to the top of the food chain to be a vegetarian. -- 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
Re: setup and mintty (was Re: New setup.exe release?)
On 5/25/2011 12:52 PM, Andy Koppe wrote: On 25 May 2011 16:26, Charles Wilson wrote: On 5/25/2011 1:17 AM, Andy Koppe wrote: On 25 May 2011 05:32, Charles Wilson wrote: Maybe when I get home I'll test out a few... Consolas Andale Mono Courier New Lucida Console Vera Sans Mono (or DejaVu LGC Sans) Droid Sans Mono Inconsolata ... FYI: http://cygutils.fruitbat.org/mintty-font-test/ Good work. What mintty version is that though? It seems to be missing the fallback scheme to (rough) ASCII equivalents for the VT100 graphics characters. mintty-0.9.8-1 The difference MAY be that I didn't actually cat xgraphics each time after changing the font. I merely changed the font, while the earlier xgraphics result was viewable in the terminal. If the fallback scheme relies on actually changing the internally-stored character code, rather than changing which glyph is used to draw that character, then my technique would bypass the fallback. Yep, that explains it. Ok, I redid the screenshots, but this time I made sure to cat the xgraphics file again after changig the font. And, you can see the G0/G1 VT100 line drawing modes, for the less-complete fonts, are getting the ASCII fallbacks. Except for Terminus, for some reason. I also added the Consolas-W7 snap you sent, and a new entry for Liberation Mono. -- Chuck -- 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
Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong
Hi Chris, It's nice to hear from Edward that we're not the only ones to notice this behavior. Of course, patches would be nice, and I would be interested in digging in into this if someone familiar with Cygwin's codebase would be willing to enlighten me as to the codepath for grabbing Win32 process exit codes and how it differs from Cygwin processes. John On May 25, 2011, at 7:19 AM, Christopher Faylor wrote: On Wed, May 25, 2011 at 10:16:03AM -0400, Edward Lam wrote: On 29/04/2011 2:35 PM, John Dong wrote: Reproducing this seems nondeterministic -- sometimes I can get it to happen in 5 minutes, other times it takes overnight. I've tried using a different shell (like dash), but it doesn't make a difference, leading me to suspect this to be a lower-level issue within the Cygwin DLL. It also seems to not happen for non-zero exit codes (e.g. checking that exiter.exe 1 returns 1 always seems to succeed), though I'm not 100% confident that I've tested this thoroughly enough. Again, I've not been able to reproduce this under Windows XP using any version of Cygwin, but I have been able to reproduce it on both 32-bit and 64-bit Windows 7. I'm not running anything special on this machine -- it's a fresh install of Windows 7 Professional, just with Cygwin installed. FWIW, we've been running into this as well. It appears to NOT be a problem with Cygwin 1.5 on Windows 7. It only started happening on Cygwin 1.7. As a result, we haven't had a reliable Windows 7 build machine for a while now because we use a Cygwin gmake process that compiles with MSVC. As always: http://cygwin.com/acronyms#PTC -- 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 -- 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
Re: mintty fonts (was: Re: setup and mintty)
On 25 May 2011 22:00, Ryan Johnson wrote: On 25/05/2011 3:48 PM, Andy Koppe wrote: On 25 May 2011 19:05, Ryan Johnson wrote: How do you get mintty to see Liberation Mono? I downloaded the family from redhat, installed it on my w7-x64 machine, made sure it was set to 'show,' and started a fresh mintty, but it still can't find the font. Works for me, on w7-x64. Make sure the font shows up in the Fonts control panel and that it isn't hidden, i.e. not appearing greyed out. There's a 'Show' button along the top of the panel in case it is. I tried to say before that I have done that (I saw the closed bug about this and made sure to follow the instructions there). Unchecking that setting about language-specific hiding made a whole bunch of other (presumably Asian) fonts show up in mintty, but still no Liberation Mono. I actually wasn't talking about that option, but the abilily to show/hide each font separately. But it doesn't sound like that's the issue anyway. The font is officially installed, officially showing, and usable by just about everything except mintty. Most apps (like Word) picked it up immediately. Right, I'm afraid that leaves me stumped, given it's fine here. Do you fancy messing with the mintty source code to see which flag on ChooseFont() is excluding that font? It's in select_font() in winctrls.c. I guess CF_FIXEDPITCHONLY is the prime candidate. Removing CF_FIXEDPITCHONLY indeed allows the font to show (and a whole pile of non fixed-pitch friends). Apparently the font version I downloaded (liberation-fonts-ttf-1.06.0.20100721) doesn't mark itself as fixed-pitch? When I select liberation mono, ChooseFont populates the LOGFONT with lfPitchAndFamily=0x32. MSDN says: The two low-order bits specify the pitch of the font and can be one of the following values. DEFAULT_PITCH FIXED_PITCH VARIABLE_PITCH Sure enough, grep-find over /usr/include/w32api shows: wingdi.h:380:#define VARIABLE_PITCH 2 Thanks very much for investigating. I guess somebody needs to file a bug with fedorahosted.org, but I didn't see an obvious way to request an account with them. Do you have one by chance? Nope, sorry. Clicking at the first hopeful-looking Google result for Liberation Mono, I'd downloaded it from a site called dafont.com. Apparently I picked up an old version without that problem: 1.04. Andy -- 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
mintty fonts (was: Re: setup and mintty)
On 26 May 2011 02:42, Charles Wilson wrote: http://cygutils.fruitbat.org/mintty-font-test/ Ok, I redid the screenshots, but this time I made sure to cat the xgraphics file again after changig the font. Thanks very much for putting in all that effort, and congratulations to test winner DejaVu Sans Mono. :) And, you can see the G0/G1 VT100 line drawing modes, for the less-complete fonts, are getting the ASCII fallbacks. Except for Terminus, for some reason. I guess it maps codepoints it doesn't support to an empty glyph instead of leaving them undefined, thereby preventing substitution. Dishonourable mentions also for Envy Code R, Inconsolata, and Liberation Mono for having empty default glyphs instead of the usual box that at least shows that something is amiss. Andy -- 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
Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong
On Wed, May 25, 2011 at 07:20:35PM -0700, John Dong wrote: It's nice to hear from Edward that we're not the only ones to notice this behavior. Of course, patches would be nice, and I would be interested in digging in into this if someone familiar with Cygwin's codebase would be willing to enlighten me as to the codepath for grabbing Win32 process exit codes and how it differs from Cygwin processes. Look in pinfo.cc and sigproc.cc. cgf -- 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
