Re: PHP error
Greetings, wynfi...@gmail.com! > While checking to see what verions of php I had I ran php --version and > received the following warning regarding mysqli: > $ php --version >PHP Warning: Module 'mysqli' already loaded in Unknown on line 0 >PHP Warning: Module 'mysqli' already loaded in Unknown on line 0 >PHP 5.4.19 (cli) (built: Aug 23 2013 14:32:19) >Copyright (c) 1997-2013 The PHP Group >Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies > Is this a problem or simply an annoying message that should be ignored? I'm pretty sure this is a problem with your PHP configuration, that have nothing to do with Cygwin. Most likely, you have mysqli module mentioned multiple times in PHP configuration. -- WBR, Andrey Repin (anrdae...@yandex.ru) 17.12.2013, <13:33> Sorry for my terrible english... -- 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
locale "de_DE.UTF-8", fscanf problem?
Hello,
There seems to be an "unbalance" with fprintf and fscanf when using the
"de_DE.UTF-8" locale.
The following program correctly writes "2,5" (decimal comma) to a file. But
reading with fscanf fails - the decimal comma is treated as "end of number".
Regards,
Tilman
--
#include
#include
#include
int main(void)
{
double test;
setlocale(LC_NUMERIC, "de_DE.UTF-8");
FILE* fp = fopen("test.txt", "w");
fprintf(fp, "%f", 2.5);
fclose(fp);
printf("fprintf writes:\n");
system("cat test.txt");
fp = fopen("test.txt", "r");
fscanf(fp, "%lf", &test);
fclose(fp);
printf("\nfscanf reads:\n%f\n", test);
return 0;
}
--
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: cannot execute binary file
Greetings, Gerry Reno! > I just got finished installing Cygwin on another machine and this time the -c > does work. So I went back and looked at > the original machine. There are 2 cygwin installations on that machine in > different directories. I had forgotten that > Cygwin got installed a while back on this machine to support some app that > needed it. So somehow having 2 different > installations breaks this mintty -e capability. Does this qualify as a bug? > Is Cygwin supporting 2 independent > installations? It do support two _independent_ installations. This means, each of them have no way to find out about existence of the other, barring the full disk search. Yours were not that independent. Likely, them both were listed in $PATH. -- WBR, Andrey Repin (anrdae...@yandex.ru) 17.12.2013, <13:31> Sorry for my terrible english... -- 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: semget() API fails when run from CMD.exe but works from SH.exe
Please don't http://cygwin.com/acronyms/#TOFU Thanks. On Dec 16 12:11, Steven Bardwell wrote: > OK -- I rewrote the test program using the POSIX IPC routine sem_open() > and the program runs in SH.exe (and mintty.exe) but gives this message > when run from a DOS box: > > Warning: '/dev/shm' does not exists or is not a directory. > > POSIX semaphores require the existance of this directory. > Create the directory '/dev/shm' and set the permissions to 01777. > For instance on the command line: mkdir -m 01777 /dev/shm Yes, that's what I meant by writing "if you set up a matching environment." Looks like you don't just run tools from CMD, you're trying to run the tools outside of the Cygwin distro with its own Cygwin DLL. If you do that, you have to set up the environment around that DLL. And you should make sure to follow http://cygwin.com/licensing.html, should you release your efforts to third parties. Corinna > Steve > --- > On Dec 14 08:04, Steven Bardwell wrote: > > I would like my Cygwin programs to work from a DOS (CMD.exe) window, but I > > am > > having problems with some API calls. Here is a simple program that tries to > > create > > a semaphore – it works fine when it is run from sh.exe (or in a mintty > > window), but > > it crashes when run in a DOS window. (The Cygwin service is running.) > > > > Is there a way to make it work in both environments? > > That's not the intention of the IPC calls. They usually only work > if you set up a matching environment. > [...] -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpBtm1CtH57W.pgp Description: PGP signature
Re: locale "de_DE.UTF-8", fscanf problem?
On Dec 17 10:09, Tilman Kuepper wrote: > Hello, > > There seems to be an "unbalance" with fprintf and fscanf when using > the "de_DE.UTF-8" locale. > > The following program correctly writes "2,5" (decimal comma) to a > file. But reading with fscanf fails - the decimal comma is treated > as "end of number". > > Regards, > Tilman > > -- > [...testcase...] Weird. I was pretty sure that scanf is doing the right thing, but apparently it doesn't. Thanks a lot for the testcase, I'll have a look into this issue. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpY_BjcWhk4_.pgp Description: PGP signature
Re: PHP error
Andrey Thanks for replying. You were right. I found the problem and fixed it. Andrey Repin wrote: > Greetings, wynfield! > > > > While checking to see what verions of php I had I ran php --version and > > received the following warning regarding mysqli: > > > $ php --version > >PHP Warning: Module 'mysqli' already loaded in Unknown on line 0 > >PHP Warning: Module 'mysqli' already loaded in Unknown on line 0 > >PHP 5.4.19 (cli) (built: Aug 23 2013 14:32:19) > >Copyright (c) 1997-2013 The PHP Group > >Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies > > > > Is this a problem or simply an annoying message that should be ignored? > > I'm pretty sure this is a problem with your PHP configuration, that have > nothing to do with Cygwin. > Most likely, you have mysqli module mentioned multiple times in PHP > configuration. > > Andrey Repin > -- 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: cannot execute binary file
On 12/17/2013 4:32 AM, Andrey Repin wrote: Greetings, Gerry Reno! I just got finished installing Cygwin on another machine and this time the -c does work. So I went back and looked at the original machine. There are 2 cygwin installations on that machine in different directories. I had forgotten that Cygwin got installed a while back on this machine to support some app that needed it. So somehow having 2 different installations breaks this mintty -e capability. Does this qualify as a bug? Is Cygwin supporting 2 independent installations? It do support two _independent_ installations. This means, each of them have no way to find out about existence of the other, barring the full disk search. Yours were not that independent. Likely, them both were listed in $PATH. This thread reminded me that I faced the similar problem. Being lazy and not figuring out how to include the path to cygwin1.dll when running Intel VTune profiler, I copied the .dll to the existing PATH, thus breaking the installation when next running setup. -- Tim Prince -- 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: chere-1.3-1 (x86 and x86_64)
Version 1.3-1 of "chere" has been uploaded and should be available from mirrors shortly. chere is a script allowing you to add Explorer context menus to start cygwin in the selected directory. This version of the script supports x86 and x86_64. If you have 32 and 64 bit cygwin installed on the same machine, you can add separate context menu entries to start 32 or 64 bit terminals. The default menu text does not differentiate between 32 and 64 bit, so if you do this you should use the -e option. Changes: * Add background context menus on Windows 7 and later * Support 64 bit cygwin Fixes: * Change to appropriate drive when shell is cmd * Quote path for cmd correctly * Uninstall correctly when cygwin not in path *** 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.com 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
Re: Are there any plans to add chere in the x64 version?
On 12/12/2013 17:01, klonos wrote: Is there a feature request filed and any link to it so I can follow? Thanx in advance. In case you missed it, I've just released an initial version of chere for x86_64 Dave. -- 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: [ANNOUNCEMENT] Updated: gcc-4.7.3-1
JonY <10walls gmail.com> writes: > > * Previous gcc4-4.5.3 has been renamed to gcc and placed as previous. > I have some program that use gcc4 packet (like NS2), so, how can I rename gcc back to gcc4 -- 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: cannot execute binary file
On 12/17/2013 07:44 AM, Tim Prince wrote: > > On 12/17/2013 4:32 AM, Andrey Repin wrote: >> Greetings, Gerry Reno! >> >>> I just got finished installing Cygwin on another machine and this time the >>> -c does work. So I went back and looked at >>> the original machine. There are 2 cygwin installations on that machine in >>> different directories. I had forgotten that >>> Cygwin got installed a while back on this machine to support some app that >>> needed it. So somehow having 2 different >>> installations breaks this mintty -e capability. Does this qualify as a >>> bug? Is Cygwin supporting 2 independent >>> installations? >> It do support two _independent_ installations. >> This means, each of them have no way to find out about existence of the >> other, >> barring the full disk search. >> Yours were not that independent. Likely, them both were listed in $PATH. >> >> > This thread reminded me that I faced the similar problem. Being lazy and not > figuring out how to include the path to > cygwin1.dll when running Intel VTune profiler, I copied the .dll to the > existing PATH, thus breaking the installation > when next running setup. > I checked the PATH and I don't see any cygwin1.dll on the PATH: C:\Documents and Settings\Administrator>which cygwin1.dll which: no cygwin1.dll in (.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\W bem) -- 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: locale "de_DE.UTF-8", fscanf problem?
On Dec 17 11:04, Corinna Vinschen wrote: > On Dec 17 10:09, Tilman Kuepper wrote: > > Hello, > > > > There seems to be an "unbalance" with fprintf and fscanf when using > > the "de_DE.UTF-8" locale. > > > > The following program correctly writes "2,5" (decimal comma) to a > > file. But reading with fscanf fails - the decimal comma is treated > > as "end of number". > > > > Regards, > > Tilman > > > > -- > > [...testcase...] > > Weird. I was pretty sure that scanf is doing the right thing, but > apparently it doesn't. Thanks a lot for the testcase, I'll have a look > into this issue. A generic solution for this problem is much more complex than I anticipated. I'll be looking into getting this into the next Cygwin release, but it will take at least a couple of days to get this right, so don't hold your breath for testing a fix within... uhm... the year 2013, I guess. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpibqRr9f5nd.pgp Description: PGP signature
Re: [ANNOUNCEMENT] Updated: gcc-4.7.3-1
Il 12/17/2013 4:57 PM, Trong Nguyen ha scritto: JonY <10walls gmail.com> writes: * Previous gcc4-4.5.3 has been renamed to gcc and placed as previous. I have some program that use gcc4 packet (like NS2), so, how can I rename gcc back to gcc4 in your ~/bin or /usr/local/bin ln -s /usr/bin/gcc gcc4 -- 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: Odd command line recall problem
On 12/17/2013 2:22 PM, buggsy2 wrote: Latest cygwin64 release as of posting on Windows 7x64 GNU bash, version 4.1.11(2)-release Running in the cygwin terminal (C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico ) The several commands I use all recall correctly using the up-arrow key. That is, I type a command, it executes, I can recall it via up-arrow. Duplicate commands are collapsed to one command. However, this command seems to disappear from the history: *tac gman.out | gawk -f ../../findStuckPestJobs.awk* Immediately after issuing the command, up-arrow brings back the command prior to the tac... command. Further experimentation shows, for instance, that a simple *tac --help* command disappears also. Issuing a history command within the shell doesn't list it! cygwin problem? Or is this a bash problem? Hard to say with the information so far. It at least works fine for me with a quick test on 32-bit Cygwin. If you're still looking for help, please read the problem reporting guidelines found at the link below prior to your follow-up with the list. Problem reports: http://cygwin.com/problems.html -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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
Odd command line recall problem
Latest cygwin64 release as of posting on Windows 7x64 GNU bash, version 4.1.11(2)-release Running in the cygwin terminal (C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico ) The several commands I use all recall correctly using the up-arrow key. That is, I type a command, it executes, I can recall it via up-arrow. Duplicate commands are collapsed to one command. However, this command seems to disappear from the history: *tac gman.out | gawk -f ../../findStuckPestJobs.awk* Immediately after issuing the command, up-arrow brings back the command prior to the tac... command. Further experimentation shows, for instance, that a simple *tac --help* command disappears also. Issuing a history command within the shell doesn't list it! cygwin problem? Or is this a bash problem? -- View this message in context: http://cygwin.1069669.n5.nabble.com/Odd-command-line-recall-problem-tp105022.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: cannot execute binary file
On 12/17/2013 11:27 AM, Gerry Reno wrote: > On 12/17/2013 07:44 AM, Tim Prince wrote: >> On 12/17/2013 4:32 AM, Andrey Repin wrote: >>> Greetings, Gerry Reno! >>> I just got finished installing Cygwin on another machine and this time the -c does work. So I went back and looked at the original machine. There are 2 cygwin installations on that machine in different directories. I had forgotten that Cygwin got installed a while back on this machine to support some app that needed it. So somehow having 2 different installations breaks this mintty -e capability. Does this qualify as a bug? Is Cygwin supporting 2 independent installations? >>> It do support two _independent_ installations. >>> This means, each of them have no way to find out about existence of the >>> other, >>> barring the full disk search. >>> Yours were not that independent. Likely, them both were listed in $PATH. >>> >>> >> This thread reminded me that I faced the similar problem. Being lazy and >> not figuring out how to include the path to >> cygwin1.dll when running Intel VTune profiler, I copied the .dll to the >> existing PATH, thus breaking the installation >> when next running setup. >> > I checked the PATH and I don't see any cygwin1.dll on the PATH: > > C:\Documents and Settings\Administrator>which cygwin1.dll > > which: no cygwin1.dll in > (.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\W > bem) > > > > I went and wiped BOTH of these Cygwin installations off the machine and went and installed 2 new installations in the same directory locations and now both installations work when invoking mintty -e. So it might have been that one of the installations was much older and was causing some problem with independent installations. -- 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: Odd command line recall problem
Greetings, buggsy2! > Latest cygwin64 release as of posting on Windows 7x64 > GNU bash, version 4.1.11(2)-release > Running in the cygwin terminal (C:\cygwin64\bin\mintty.exe -i > /Cygwin-Terminal.ico ) > The several commands I use all recall correctly using the up-arrow key. That > is, I type a command, it executes, I can recall it via up-arrow. Duplicate > commands are collapsed to one command. > However, this command seems to disappear from the history: > *tac gman.out | gawk -f ../../findStuckPestJobs.awk* > Immediately after issuing the command, up-arrow brings back the command > prior to the tac... command. > Further experimentation shows, for instance, that a simple > *tac --help* > command disappears also. Issuing a history command within the shell doesn't > list it! > cygwin problem? Or is this a bash problem? Check your HISTIGNORE ? -- WBR, Andrey Repin (anrdae...@yandex.ru) 18.12.2013, <05:10> Sorry for my terrible english... -- 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
Change in behavior of bash / if [
Today, a script that I use every day stated giving me the following error message. (I grant that it might have started earlier and I didn't notice.) Note that although it gave the error message, the script seems to still have worked. ./lddir: line 77: [: too many arguments Line 77 was as follows. I'm testing whether $1 is "clip". if [ x$1 = xclip ] I fixed it with this. if [ "x$1" = xclip ] 32-bit, everything was up to date. I've solved my problem, but the change was unexpected and, for me, inexplicable, so I thought that I'd report it. Let me know if you want/need more information. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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: grep sometimes hang on 1.7.25
On Mon, Dec 16, 2013 at 03:39:26PM -0500, Christopher Faylor wrote: >On Sun, Dec 15, 2013 at 02:00:00AM +0100, Marcin J. wrote: >> `ps | cat` will hang too. > >I can duplicate this problem. I'm looking into it. This should be fixed in the upcoming cygwin snapshot. http://cygwin.com/snapshots/ What a pain that was to track down... -- 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: grep sometimes hang on 1.7.25
On Tue, Dec 17, 2013 at 10:59:13PM -0500, Christopher Faylor wrote: >On Mon, Dec 16, 2013 at 03:39:26PM -0500, Christopher Faylor wrote: >>On Sun, Dec 15, 2013 at 02:00:00AM +0100, Marcin J. wrote: >>> `ps | cat` will hang too. >> >>I can duplicate this problem. I'm looking into it. > >This should be fixed in the upcoming cygwin snapshot. > >http://cygwin.com/snapshots/ > >What a pain that was to track down... !#@($& Nevermind. The hang should be gone but the ps output is still wrong. Still checking. -- 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: moving pty master by dup()/close() causes read() to fail
On Mon, Dec 16, 2013 at 03:39:54PM -0500, Christopher Faylor wrote: >On Mon, Dec 16, 2013 at 10:21:12PM +0900, Jun T. wrote: >>Hi all. I'm new to this list. >> >>The test code at the end of this post has some problem on Cygwin. > >Thanks for the test code. I can duplicate the problem and am looking >into it. This should be fixed in the upcoming snapshot and, of course, in the next release. http://cygwin.com/snapshots/ Thanks again for the test case. That always helps immensely when tracking down problems. 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
Re: Change in behavior of bash / if [
On 12/17/2013 08:02 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: > Today, a script that I use every day stated giving me the following > error message. (I grant that it might have started earlier and I > didn't notice.) Note that although it gave the error message, the > script seems to still have worked. > > ./lddir: line 77: [: too many arguments > > Line 77 was as follows. I'm testing whether $1 is "clip". > > if [ x$1 = xclip ] What was $1 at the time? > > I fixed it with this. > > if [ "x$1" = xclip ] Yes, this is the correct fix for the improper quotation of the earlier example. > > 32-bit, everything was up to date. > > I've solved my problem, but the change was unexpected and, for me, > inexplicable, so I thought that I'd report it. Your quoting error would produce the same message on Linux; it is not cygwin-specific. > > Let me know if you want/need more information. Without knowing how $1 was set, I can only guess that it contained something with characters in $IFS and therefore the word-splitting of the unquoted use caused too many arguments to [. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: grep sometimes hang on 1.7.25
On Tue, Dec 17, 2013 at 11:02:21PM -0500, Christopher Faylor wrote: >On Tue, Dec 17, 2013 at 10:59:13PM -0500, Christopher Faylor wrote: >>On Mon, Dec 16, 2013 at 03:39:26PM -0500, Christopher Faylor wrote: >>>On Sun, Dec 15, 2013 at 02:00:00AM +0100, Marcin J. wrote: `ps | cat` will hang too. >>> >>>I can duplicate this problem. I'm looking into it. >> >>This should be fixed in the upcoming cygwin snapshot. >> >>http://cygwin.com/snapshots/ >> >>What a pain that was to track down... > >!#@($& Nevermind. The hang should be gone but the ps output is still >wrong. > >Still checking. Ok, now it should really be fixed. 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
