Re: ls -t changes the cygwin-access time of a file
On Apr 11 07:15, Ronald Fischer wrote: > I'm running on Windows 7 64bit, the disk has NTFS, and I have Windows > enabled to track the correct file access time. > > With Cygwin, I see the following oddity: > > -0-1- ~/gitwrk/vp5 > ls -lu c:/tmp/x* > -rw-r--r-- 1 FISRONA Domain Users 10 Apr 11 06:59 c:/tmp/xx > (waiting a couple of minutes) > -0-1- ~/gitwrk/vp5 > ls -lut c:/tmp/x* > -rw-r--r-- 1 FISRONA Domain Users 10 Apr 11 07:01 c:/tmp/xx > > I didn't touch the file in between, but the reported access time > changed. Further experimentation shows, that the reported access time > changes as soon as I use the -t option with ls. As long as I just do ls > -lu, the access time does not change. No, it changes every time you do an ls -l. Yes, this is a bug, but it's a bug in Windows, as old as Windows NT itself. To fetch stat(2)-like meta information on a file, the caller has to open the file (NtOpenFile), read the meta data (NtQueryInformationFile / NtQuerySecurityObject) and close the file again (NtClose). The problem is this: Even if you open the file explicitely with only metadata access rights (READ_CONTROL | FILE_READ_ATTRIBUTES | FILE_READ_EA), the access will count as data access and the file access timestamp will be bumped. Sticking to `fsutil behavior set disablelastaccess 1' works better. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
missing config.rpath
Aloha, I am attempting to use cygport to compile LAME under cygwin-64. I have the files from here: https://sourceforge.net/p/cygwin-ports/lame/ But I keep getting this error: cp: cannot stat '/usr/share/gettext/config.rpath': No such file or directory In fact, I don't even have a /usr/share/gettext/ directory which is odd. gettext 0.19.8.1-2 has been installed. All other packages are up to date. This is a fresh install. Would be grateful for any pointers, thanks in advance! Michael -- 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: missing config.rpath
On 11/04/2017 12:29, Michael Hoenig wrote: Aloha, I am attempting to use cygport to compile LAME under cygwin-64. I have the files from here: https://sourceforge.net/p/cygwin-ports/lame/ But I keep getting this error: cp: cannot stat '/usr/share/gettext/config.rpath': No such file or directory In fact, I don't even have a /usr/share/gettext/ directory which is odd. gettext 0.19.8.1-2 has been installed. All other packages are up to date. This is a fresh install. Would be grateful for any pointers, thanks in advance! Michael Install gettext-devel-0.19.8.1-2 Regards Marco -- 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: Use a default path in exec*p*() if PATH is unset?
Thomas Wolff wrote: Am 10.04.2017 um 22:29 schrieb Christian Franke: A few years after https://cygwin.com/ml/cygwin/2014-09/msg00204.html I found another use case of an unset PATH variable: The configure script from mandoc (http://mdocml.bsd.lv/) uses this interesting approach to query default CC command from make: CC=`printf "all:\\n\\t@echo \\\$(CC)\\n" | env -i make -sf -` Why does it `env -i` at all? I guess because make result should not depend on environment. I agree that 'env -i' is probably to much, 'env -u CC' would be enough. (And why does it prepend a \ to the output?) It doesn't. The extra \\ is required because `...` is used instead of $(...): $ printf "all:\\n\\t@echo \\\$(CC)\\n" all: @echo \$(CC) $ CC=$(printf "all:\\n\\t@echo \\\$(CC)\\n" > /dev/tty) all: @echo \$(CC) $ CC=`printf "all:\\n\\t@echo \\\$(CC)\\n" > /dev/tty` all: @echo $(CC) It seems this scriptlet has an issue, rather than adapting core behaviour for it. Of course Cygwin shouldn't be adapted solely for this single case. But it possibly Cygwin should be adapted to the existing practice of various other open source *ix systems. Interestingly the approach in newlib/libc/posix/execvp.c differs from Cygwin and others: execvp() with PATH unset calls execv(). This has the same effect as execvp() with PATH set to current directory only. Christian -- 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: missing config.rpath
On 11/04/2017 00:44, Marco Atzeri wrote: On 11/04/2017 12:29, Michael Hoenig wrote: Aloha, I am attempting to use cygport to compile LAME under cygwin-64. I have the files from here: https://sourceforge.net/p/cygwin-ports/lame/ But I keep getting this error: cp: cannot stat '/usr/share/gettext/config.rpath': No such file or directory In fact, I don't even have a /usr/share/gettext/ directory which is odd. gettext 0.19.8.1-2 has been installed. All other packages are up to date. This is a fresh install. Would be grateful for any pointers, thanks in advance! Michael Install gettext-devel-0.19.8.1-2 Regards Marco That worked. Thanks for the quick help Marco! Aloha, Michael -- 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
warning message
2 [main] rsync 6252 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com sending incremental file list -- 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: warning message
On 11/04/2017 13:20, Randy Stokes wrote: 2 [main] rsync 6252 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com sending incremental file list Randy, it is an ancient problem. Solved age ago Ask whoever provided you with a very old copy of cygwin1.dll to update to latest version. Regards Marco -- 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: Use a default path in exec*p*() if PATH is unset?
On 4/11/2017 7:10 AM, Christian Franke wrote: > Thomas Wolff wrote: >> Am 10.04.2017 um 22:29 schrieb Christian Franke: >>> A few years after https://cygwin.com/ml/cygwin/2014-09/msg00204.html >>> I found another use case of an unset PATH variable: >>> >>> The configure script from mandoc (http://mdocml.bsd.lv/) uses this >>> interesting approach to query default CC command from make: >>> >>> CC=`printf "all:\\n\\t@echo \\\$(CC)\\n" | env -i make -sf -` >> Why does it `env -i` at all? > > I guess because make result should not depend on environment. I agree > that 'env -i' is probably to much, 'env -u CC' would be enough. > -i, --ignore-environment start with an empty environment A relative use of the executable will not be found if the environment is empty. > >> (And why does it prepend a \ to the output?) > > It doesn't. The extra \\ is required because `...` is used instead of > $(...): > > $ printf "all:\\n\\t@echo \\\$(CC)\\n" > all: > @echo \$(CC) > > $ CC=$(printf "all:\\n\\t@echo \\\$(CC)\\n" > /dev/tty) > all: > @echo \$(CC) > > $ CC=`printf "all:\\n\\t@echo \\\$(CC)\\n" > /dev/tty` > all: > @echo $(CC) > > >> It seems this scriptlet has an issue, rather than adapting core >> behaviour for it. > > Of course Cygwin shouldn't be adapted solely for this single case. > But it possibly Cygwin should be adapted to the existing practice of > various other open source *ix systems. > No, the other open source systems should adapt practices to defined POSIX representation and not impose such "defaults" to their methods. Using default behavior should never condoned as a default behavior, unless defined explicitly can always be different elsewhere or even change on the same system. > Interestingly the approach in newlib/libc/posix/execvp.c differs from > Cygwin and others: > execvp() with PATH unset calls execv(). This has the same effect as > execvp() with PATH set to current directory only. > Why do you assume that this is an issue with execvp? The user should not expect that an undefined behavior behaves the same way on other systems. You might be able to get away with "env -i `which make` -sf -" but this is broken based on POSIX. -- cyg 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: Cygwin - Install Liquidsoap for Shoutcast or Icecast
I get a warning, that I totally looked over yesterday. I went into the Repository, and installed all items with the name of OCAML However, that did not seem to do anything, as all these items are still missing and need to be installed. >>> Preparing working source directory *** Warning: Some build dependencies are not installed. *** Warning: This package may end up missing features, or not build at all. *** Warning: Consider installing these packages first before continuing: *** Warning: ocaml(ao) ocaml(camlimages) ocaml(camomile) ocaml(cry) ocaml(dtools) ocaml(duppy) ocaml(faad) ocaml(flac) ocaml(gavl) ocaml(gd) ocaml(gstreamer) ocaml(ladspa) ocaml(lame) ocaml(lastfm) ocaml(lo) ocaml(mad) ocaml(magic) ocaml(mm) ocaml(ogg) ocaml(opus) ocaml(pcre) ocaml(portaudio) ocaml(pulseaudio) ocaml(samplerate) ocaml(schroedinger) ocaml(sdl) ocaml(shine) ocaml(soundtouch) ocaml(speex) ocaml(taglib) ocaml(theora) ocaml(voaacenc) ocaml(vorbis) ocaml(xmlplaylist) ocaml(yojson) -- 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
GNU Tools Cauldron 2017, Prague, September 8-10
Hi, we are very pleased to invite you all the GNU Tools Cauldron on 8-10 September 2017. This year we will meet again in Prague, at Charles University. Details are here: https://gcc.gnu.org/wiki/cauldron2017 As usual, please register (capacity is limited), send abstracts and ask administrivia questions to tools-cauldron-ad...@googlegroups.com. I plan to contact GCC, GDB, binutils, CGEN, DejaGnu, newlib and glibc mailing lists. Please feel free to share with any other groups that are appropriate. Looking forward to see you in Prague, Honza Hubicka -- 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 not get XWindows to Work in Cygwin/X .... I LOVE CYGWIN, USE IT EVERY DAY
Dear Cygwin, I am trying to get the X Windows to work, I must be doing something wrong. I read the FAQ and manual but no go. I have Cygwin/X installed on a Windows 7 Desktop. I type Startxwin or xwin and just get a xterm to the server ? I got some directions I am gonna try tonight. I would like to take this chance to say thanks for the software I LOVE CYGWIN, USE IT EVERY DAY. I have shell scripting that runs my EDI programs ... it was on the korn shell on MKS toolkit the one person i worked with wanted to save money and (unknow to me) never paid the Software Maint. fees to mks and when I went to renew ... they wanted a huge sum of money and gave me a destuction date for the software i explained that I needed to run 2 environments and could not destroy the software. They would not deal with me, help me or for that matter, return my calls or email. It took a little work ... but I ported my scripting to bash under Cygwin. Next time the arrogant sales rep called me asking what I wanted to do ... I said I moved to the free, Open Source Cygwin and simply have no further need of your overpriced software. OPEN SOURCE RULES !!! -- 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 not get XWindows to Work in Cygwin/X .... I LOVE CYGWIN, USE IT EVERY DAY
Suggest reinstalling Cygwin with additional options as follows: - xwin-xdg-menu - xwinclip - xwininfo - cygrunsrv (if you're going to run an sshd server) - curl (if you test network connections of various protocols, useful when ping is blocked) - geany (lightweight IDE or programmer's editor) - mate-terminal ( or other Xwindow terminal programs (I like MATE terminal, but Xterm works also) - dia (Visio like vector based drawing program with some pretty good built in stencils) There, that should get you started. No need to remove anything you've already got installed, just run latest installer setup.exe or setup-x86.exe and pick the new programs. When it finishes, you should have a new application in your Cygwin/X menu item in Windows called "XWin Server", run that. You should then see two new icons pop up in the task bar, one is the X server and is only there to tell you that Xserver is active, the other looks like the bash launch icon, right click on that and voila, there is your new XDG desktop menu where all your graphical Cygwin programs will show up. Let me know if this was helpful. -Original Message- From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of mrushton Sent: Tuesday, April 11, 2017 1:55 PM To: cygwin Subject: Can not get XWindows to Work in Cygwin/X I LOVE CYGWIN, USE IT EVERY DAY Dear Cygwin, I am trying to get the X Windows to work, I must be doing something wrong. I read the FAQ and manual but no go. I have Cygwin/X installed on a Windows 7 Desktop. I type Startxwin or xwin and just get a xterm to the server ? I got some directions I am gonna try tonight. I would like to take this chance to say thanks for the software I LOVE CYGWIN, USE IT EVERY DAY. I have shell scripting that runs my EDI programs ... it was on the korn shell on MKS toolkit the one person i worked with wanted to save money and (unknow to me) never paid the Software Maint. fees to mks and when I went to renew ... they wanted a huge sum of money and gave me a destuction date for the software i explained that I needed to run 2 environments and could not destroy the software. They would not deal with me, help me or for that matter, return my calls or email. It took a little work ... but I ported my scripting to bash under Cygwin. Next time the arrogant sales rep called me asking what I wanted to do ... I said I moved to the free, Open Source Cygwin and simply have no further need of your overpriced software. OPEN SOURCE RULES !!! -- 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: Can not get XWindows to Work in Cygwin/X .... I LOVE CYGWIN, USE IT EVERY DAY
mrushton writes: > I type Startxwin or xwin and just get a xterm to the server? Well, then X works as it's supposed to be. The standard setup is to use a rootless server and have Windows manage the application windows (like that xterm you're seeing). There should be two new icons in the try in Windows' taskbar. Make them permanently visible, you can start some applications via the context menu from there. If you insist on using a root window and run a separate window manager on it (which I would only recommend if you dedicate a separate monitor to it), then WindowMaker is lightweight and doesn't pull in as many dependecies as some of the other choices. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- 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: Use a default path in exec*p*() if PATH is unset?
cyg Simple wrote: -i, --ignore-environment start with an empty environment A relative use of the executable will not be found if the environment is empty. Not necessarily (see Linux, *BSD, ...). POSIX says this is "implementation-defined" - under the assumption that 'env' uses execvp() which is the case for the GNU coreutils version. Interestingly the approach in newlib/libc/posix/execvp.c differs from Cygwin and others: execvp() with PATH unset calls execv(). This has the same effect as execvp() with PATH set to current directory only. Why do you assume that this is an issue with execvp? I never did (otherwise this would be a thread on cygwin-patches list). The above only means that it is IMO interesting that the Cygwin source package contains two implementations of execvp() which handle the unset PATH situation differently. The user should not expect that an undefined behavior behaves the same way on other systems. Of course. But even then it is a reasonable question which possible alternative should be implemented by Cygwin. Cygwin homepage says "Get that Linux feeling, ...". So "implementation-defined" behavior should possibly be close to Linux :-) Christian -- 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: gl2ps-1.4.0.-1
Version 1.4.0-1 of gl2ps (source only) libgl2ps1, libgl2ps-devel have been uploaded for cygwin. GL2PS is a C library providing high quality vector output for any OpenGL application. The main difference between GL2PS and other similar libraries is the use of sorting algorithms capable of handling intersecting and stretched polygons, as well as non manifold objects. GL2PS provides advanced smooth shading and text rendering, culling of invisible primitives, mixed vector/bitmap output, and much more... CHANGES This is a new mainstream release. http://www.geuz.org/pipermail/gl2ps-announce/2017/23.html WEBSITE http://www.geuz.org/gl2ps/ http://gitlab.onelab.info/gl2ps/gl2ps Regards Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) 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
Warning: Consider installing these packages ocaml(ao) ocaml(camlimages)
Hello All; So, I am getting really close to having LiquidSoap installed. I have run into an issue. >>> Preparing working source directory *** Warning: Some build dependencies are not installed. *** Warning: This package may end up missing features, or not build at all. *** Warning: Consider installing these packages first before continuing: *** Warning: ocaml(ao) ocaml(camlimages) ocaml(camomile) ocaml(cry) ocaml(dtools) ocaml(duppy) ocaml(faad) ocaml(flac) ocaml(gavl) ocaml(gd) ocaml(gstreamer) ocaml(ladspa) ocaml(lame) ocaml(lastfm) ocaml(lo) ocaml(mad) ocaml(magic) ocaml(mm) ocaml(ogg) ocaml(opus) ocaml(pcre) ocaml(portaudio) ocaml(pulseaudio) ocaml(samplerate) ocaml(schroedinger) ocaml(sdl) ocaml(shine) ocaml(soundtouch) ocaml(speex) ocaml(taglib) ocaml(theora) ocaml(voaacenc) ocaml(vorbis) ocaml(xmlplaylist) ocaml(yojson) I rent into the Repository and isntalled everything that was OCAML However, that did not resolve the above issue. Could someone please provide the code to get them items installed? And I am hoping, that having them installed, will resolve the issue below. >checking build system type... Invalid configuration `Users': machine `Users' >not recognized >configure: error: /bin/sh ./config.sub Users failed >make[1]: Entering directory >'/home/carrzstudio/liquidsoap/liquidsoap-1.2.1-1.x86_64/build/ocaml-cry-0.4.1' >make[1]: *** No targets specified and no makefile found. Stop. >make[1]: Leaving directory >'/home/carrzstudio/liquidsoap/liquidsoap-1.2.1-1.x86_64/build/ocaml-cry-0.4.1' >make: *** [Makefile:11: all] Error 1 >*** ERROR: make failed Thanks, All; Wayne -- 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: Warning: Consider installing these packages ocaml(ao) ocaml(camlimages)
On 2017-04-11 17:40, Wayne Barron wrote:
> ocaml(ao) ocaml(camlimages) ocaml(camomile) ocaml(cry) ocaml(dtools)
> ocaml(duppy) ocaml(faad) ocaml(flac) ocaml(gavl) ocaml(gd)
> ocaml(gstreamer) ocaml(ladspa) ocaml(lame) ocaml(lastfm) ocaml(lo)
> ocaml(mad) ocaml(magic) ocaml(mm) ocaml(ogg) ocaml(opus) ocaml(pcre)
> ocaml(portaudio) ocaml(pulseaudio) ocaml(samplerate)
> ocaml(schroedinger) ocaml(sdl) ocaml(shine) ocaml(soundtouch)
> ocaml(speex) ocaml(taglib) ocaml(theora) ocaml(voaacenc)
> ocaml(vorbis) ocaml(xmlplaylist) ocaml(yojson)
Ignore the ocaml, prefix the names with lib, and for Cygwin add
*-devel to get the names of the packages to install; if using cygport,
consider adding the following to DEPEND="...":
libao-devel libgd-devel libgstreamer1.0-devel libmad-devel libogg-devel
libopus-devel libpcre{,2}-devel libportaudio-devel libportaudiocpp-devel
libsamplerate-devel libschroedinger1.0-devel libtheora-devel
libvorbis-devel
install those Cygwin packages, possibly curl, pkg-config, and
gstreamer1.0-plugins-{base,doc}, and check the ocaml and gstreamer docs
for additional plugins you may need to install, and edit ocaml PACKAGES
to disable unavailable optional libraries.
You might want to work thru the install alternatives on:
http://liquidsoap.fm/download.html
to see which approach is easiest for you to get something installed and
running. You may want to start by copying PACKAGES.minimal to PACKAGES
as recommended and decide what you really need.
HTH and good luck.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
man page of CYGPORT(1) has an old content. should be updated.
Hello, I report one thing about manpage for cygport. Man page CYGPORT(1) seems to show old content about 'all' COMMAND. According to manpage CYGPORT(1), 'all' COMMMAND means 'run all of the above, excluding finish.' However 'download' COMMAND is excepted on actual performing. Thus, source patching with $(PATCH_URI} does not perform. Latest README of cygport describes correct information. https://github.com/cygwinports/cygport/blob/master/README According to it, fetch(download) COMMAND is not included in 'all'. I think manpage CYGPORT(1) should be updated. Currently I am using Cygwin as follows. $ uname -a CYGWIN_NT-6.1-WOW turtle0 2.8.0(0.309/5/3) 2017-04-01 20:42 i686 Cygwin $ cygport --version cygport 0.24.0 ... Regard. -- 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: Warning: Consider installing these packages ocaml(ao) ocaml(camlimages)
Hey, Brian. Are you referring too. >You might want to work through the install alternatives on: As in maybe using the recommended solution, of which is the top suggestion. http://opam.ocaml.org -- 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
