Re: teTeX/dvips
Ryan Johnson was heard to say: AFAIK, it's a tex thing and has little or no relation to anything linux or unix. Other than that I tend to agree with your assessment, tho. Just for the sake of completeness: most TeX implementations use the Kpathsea library for path searching. Its idiosyncrasies are well documented right here: http://www.tug.org/texinfohtml/kpathsea.html regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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
v*printf functions not available with g++ -std=c++0x
Hi all, I'm using the experimental gcc-4.5 package and hit a strange error: c++0x mode suppresses the definition of the v*printf() family of functions in stdio.h in c++0x mode. The offending code seems to be: #if !defined(__STRICT_ANSI__) || (__STDC_VERSION__ >= 199901L) #ifndef _REENT_ONLY ... int _EXFUN(vsnprintf, (char *, size_t, const char *, __VALIST) _ATTRIBUTE ((__format__ (__printf__, 3, 0; ... #endif #endif Running `g++ -std=c++0x -dM -E' indicates that __STRICT_ANSI__ is defined while _REENT_ONLY and __STDC_VERSION__ are not. Oddly, functions like _vsnprintf_r are still available for some strange reason (aren't they extensions?). I hope this is a bug rather than a requirement of the new standard; meanwhile, using std=gnu++0x works around the problem. 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
[ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-23.3-3
New releases of the emacs, emacs-X11, and emacs-el packages (23.3-3) are now available, leaving 23.3-2 as previous. This fixes the problem with memory management discussed starting at http://cygwin.com/ml/cygwin/2011-08/msg00167.html (see also http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9273). In addition, all executables have been made large address aware. It would be good if people could test this release with a recent Cygwin snapshot, since the problem mentioned above first showed up with the 2011-07-21 snapshot. CYGWIN NOTES Install the emacs-X11 package if you want to use the X11 GUI. You can then type 'emacs&' in an xterm window, and emacs will start in a new window. The script /usr/bin/make-emacs-shortcut can be used to create a shortcut for starting emacs. The shortcut starts emacs under X if an X server is running and in a mintty window otherwise. Edit the shortcut and/or the script if you want different behavior. You will need the cygutils package to run the script, and you will need mintty and run2 to use the shortcut. In addition, the user who runs the script needs to be able to write to /usr/local/bin. DESCRIPTION === Emacs is a powerful, customizable, self-documenting, modeless text editor. Emacs contains special code editing features, a scripting language (elisp), and the capability to read mail, news, and more without leaving the editor. To update your installation, click on the "Update Cygwin" link on the http://cygwin.com/ web page, and follow the instructions. Ken Brown Cygwin emacs maintainer *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL. -- 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
[ANNOUNCEMENT] Updated: libusb-win32 1.2.5.0-1
Version 1.2.5.0-1 of "libusb-win32" has been uploaded. This is a new upstream release, the filter installer is not shipped any more as it does not build on cygwin any more. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin AT cygwin DOT com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
screen uses /bin/sh
Hi, screen uses /bin/sh by default, not /bin/bash despite SHELL being set to /bin/bash. "screen -s /bin/bash" does the right thing. -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://ffii.org http://jihadwatch.org http://truepeace.org http://openvotingconsortium.org http://thereligionofpeace.com I'd give my right arm to be ambidextrous. -- 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
how to get into dos mode & run .bat or .cmd file
I want a bash / shell script that I can run that will go into dos mode, and from there run a .bat or a .cmd script automatically. After much googl'ing and experimenting, I cannot quite get it to run a dos shell and run a .bat or .cmd. any help would be appreciated. J.V. -- 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: how to get into dos mode & run .bat or .cmd file
On 8/17/2011 4:26 PM, J.V. wrote: I want a bash / shell script that I can run that will go into dos mode, and from there run a .bat or a .cmd script automatically. After much googl'ing and experimenting, I cannot quite get it to run a dos shell and run a .bat or .cmd. any help would be appreciated. If you have a .bat file named foo.bat, then you can run simply by: foo.bat from a bash command line or shell script file. You can pass arguments as well. There is no automatic conversion between Windows and cygwin/Unix-style paths, so you may find the cygpath utility helpful. I am not sure what "going into dos mode" would mean, but you can also run cmd.exe from the command line by typing: cmd In the case of both cmd and foo.bat, their directories need to be in your search path, or else offered explicitly. Best wishes -- Eliot Moss -- 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
Help debugging signal sources with gdb
Hi all,
Signals seem to really confuse gdb under cygwin (win7-x64), usually
leading to stack traces somewhere in kernelbase.dll or ntdll.dll with no
hint of the actual code responsible for the error. In particular,
SIGABRT and SIGSEGV would be nice to catch a little closer to the source.
SIGABRT example (workaround: set a breakpoint on the abort() function):
$ cat > sigabrt.c < #include
> int main() { assert(0); }
> EOF
[Ryan@ryan-cms-utsc] ~/experiments
$ gcc -g sigabrt.c
[Ryan@ryan-cms-utsc] ~/experiments
$ gdb --quiet a
Reading symbols from /home/Ryan/experiments/a...done.
(gdb) r
Starting program: /home/Ryan/experiments/a
[New Thread 10060.0x18b4]
warning: cYg 61184840
[New Thread 10060.0x2970]
warning: cYgstd 28ccf5 d 3
Program received signal SIGABRT, Aborted.
0x76eaf8c1 in ntdll!RtlUpdateClonedSRWLock () from
/cygdrive/c/Windows/system32/ntdll.dll
(gdb) bt
#0 0x76eaf8c1 in ntdll!RtlUpdateClonedSRWLock () from
/cygdrive/c/Windows/system32/ntdll.dll
#1 0x76eaf8c1 in ntdll!RtlUpdateClonedSRWLock () from
/cygdrive/c/Windows/system32/ntdll.dll
#2 0x76350a91 in WaitForSingleObjectEx () from
/cygdrive/c/Windows/syswow64/KERNELBASE.dll
#3 0x0218 in ?? ()
#4 0x in ?? ()
(gdb)
SIGSEVG example (no known workaround; I'm pretty sure sigsegv.c does
*not* corrupt the stack):
$ cat > sigsegv.c < #include
> int main() { return atoi(0); }
> EOF
$ gcc -g sigsegv.c
$ gdb --quiet a
Reading symbols from /home/Ryan/experiments/a...done.
(gdb) r
Starting program: /home/Ryan/experiments/a
[New Thread 11932.0x2c40]
warning: cYg 61184840
[New Thread 11932.0x2ca0]
warning: cYgstd 28ccf5 d 3
Program received signal SIGSEGV, Segmentation fault.
0x7634b9bc in RaiseException ()
from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
(gdb) bt
#0 0x7634b9bc in RaiseException ()
from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
#1 0x76352ad6 in OutputDebugStringA ()
from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
#2 0x40010006 in ?? ()
#3 0x in ?? ()
(gdb)
Running either toy program with cygwin1.dbg available adds some details
(like arguments and line numbers for some functions) but still doesn't
give a stack trace that includes main().
About half the time the seg faulting example puts _strtol_r()
(strtol.c:152) at the top of the bogus stack trace instead of
RaiseException (no sign of its ancestors: strtol, atoi and main);
independently, there's a 50/50 chance of a STATUS_ACCESS_VIOLATION and a
stack dump, but it's patchy. I'm pretty sure the seg fault isn't due to
a corrupted stack, because all the code does is try to access *s when s==0:
151 do {
152 c = *s++;
153 } while (isspace(c));
I know I'm probably the only cygwin user that writes code that seg
faults, but does anybody have a suggestion on how to work around this?
The relevant package versions are:
binutils2.21.53-1
cygwin 1.7.9-1
gcc44.5.0-1
gcc4-core 4.5.0-1
gcc4-g++4.5.0-1
gdb 7.3.50-1
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
install on win7 enterprise, can't modify bash start up shortcut
I have just installed 1.7 on win7 enterprise 64 bit and I tried to modify the shortcut that starts the bash window and I get a windows error message, "can't modify the shortcut . make sure it has not been deleted or renamed" I currently have cygwin installed at E:/cygwin and I also tried "reinstall using the recommended windows settings", as well as installing at C:/cygwin. I get the same error every time. I have installed on this OS before and I don't remember this issue, so I'm not sure what is going on. Do I need to change permissions on the cygwin folder, the cygwin installer, change windows permissions, install it in a different location, etc? I have had non-windows programs on the C drive not be able to write to their log files and such,!@#*&^%&, but this was always correctable by installing elsewhere. I have also done, mkpasswd -l > /etc/passwd and mkgroup -l > /etc/group if that matters to anyone. This was also an offline install, which I have never had any issue with before. Thanks for the suggestions, LMH -- 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
i686-XXX-mingw32 compilers and __MINGW32_MINOR_VERSION macro: 3.18 or 3.11?
Using cygwin 1.7.9(0.237/5/3) 2011-03-29 10:10.
The following program:
#include
int main() {
std::cout<<__MINGW32_MAJOR_VERSION<<'.'<<__MINGW32_MINOR_VERSION<<'\n';
return 0;
}
outputs:
- 3.18 when built with i686-pc-mingw32-g++
- 3.11 when built with i686-w64-mingw32-g++
why?
I have mingw-runtime version 3.18 installed. Is it used only by i686-pc-mingw32?
I found that:
$ grep -r "#define *__MINGW32_MINOR_VERSION" /usr/i686-pc-mingw32/
/usr/i686-pc-mingw32/sys-root/mingw/include/_mingw.h:#define
__MINGW32_MINOR_VERSION 18
and
$ grep -r "#define *__MINGW32_MINOR_VERSION" /usr/i686-w64-mingw32/
/usr/i686-w64-mingw32/sys-root/mingw/include/_mingw_mac.h:#define
__MINGW32_MINOR_VERSION 11
This seems to be one of the reasons that prevents me to use boost on cygwin 1.7.
Regards,
Frédéric
--
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: install on win7 enterprise, can't modify bash start up shortcut
* LMH (Wed, 17 Aug 2011 21:59:12 -0400) > I have just installed 1.7 on win7 enterprise 64 bit and I tried to > modify the shortcut that starts the bash window and I get a windows > error message, > > "can't modify the shortcut > . > make sure it has not been deleted or renamed" Why on earth and in which way would you want to modify a shortcut?? If it points to a non-existing target than delete it and re-create manually. Or run setup again which should do the same. Thorsten -- 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
