[ANNOUNCEMENT] Updated: libspectre-0.2.10-2
The following packages have been uploaded to the Cygwin distribution: * libspectre-devel-0.2.10-2 * libspectre1-0.2.10-2 * libspectre-0.2.10-2-src * libspectre-debuginfo-0.2.10-2 This is an update to the latest upstream (version 0.2.10 with an upstream patch [1]). [1]: https://gitlab.freedesktop.org/libspectre/libspectre/-/commit/66dc111212930fa7f936ea3ed69a566febef5f4c -- libspectre is a small library for rendering Postscript documents. It provides a convenient easy to use API for handling and rendering Postscript documents. HomePage: https://www.freedesktop.org/wiki/Software/libspectre/ News: https://gitlab.freedesktop.org/libspectre/libspectre/-/blob/0.2.10/NEWS Source: https://gitlab.freedesktop.org/libspectre/libspectre/-/tree/0.2.10 License: GNU General Public License v2.0 https://gitlab.freedesktop.org/libspectre/libspectre/-/blob/0.2.10/COPYING Cygwin Package Summary: https://www.cygwin.com/packages/summary/libspectre-src.html Cygport Source: https://www.cygwin.com/git/?p=git/cygwin-packages/libspectre.git -- Lemures Lemniscati -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: libspectre-0.2.10-2
The following packages have been uploaded to the Cygwin distribution: * libspectre-devel-0.2.10-2 * libspectre1-0.2.10-2 * libspectre-0.2.10-2-src * libspectre-debuginfo-0.2.10-2 This is an update to the latest upstream (version 0.2.10 with an upstream patch [1]). [1]: https://gitlab.freedesktop.org/libspectre/libspectre/-/commit/66dc111212930fa7f936ea3ed69a566febef5f4c -- libspectre is a small library for rendering Postscript documents. It provides a convenient easy to use API for handling and rendering Postscript documents. HomePage: https://www.freedesktop.org/wiki/Software/libspectre/ News: https://gitlab.freedesktop.org/libspectre/libspectre/-/blob/0.2.10/NEWS Source: https://gitlab.freedesktop.org/libspectre/libspectre/-/tree/0.2.10 License: GNU General Public License v2.0 https://gitlab.freedesktop.org/libspectre/libspectre/-/blob/0.2.10/COPYING Cygwin Package Summary: https://www.cygwin.com/packages/summary/libspectre-src.html Cygport Source: https://www.cygwin.com/git/?p=git/cygwin-packages/libspectre.git -- Lemures Lemniscati
Re: Permissions issues after installing Windows 10
On Thu, Jun 2, 2022 at 6:44 AM Brent Epp wrote: In the [Security] tab for these files or directories, under "Group or > user names", it lists the owner as "Account Unknown(S-...)". In some > cases, these files are completely inaccessible and I can't even take > ownership or change the permissions. I have to either restore them from > a backup or boot to a Linux environment to access them. > Windows displays "Account Unknown" (with a SID) in the ACL when it can't resolve the SID reference. There can be a number of reasons for this. One common reason is that the SID belongs to a domain account and the domain is not accessible. Another is that the SID belongs to a local account on a different computer (e.g., a removable disk is moved between computers and local accounts are in the ACL). Well-known SIDs (e.g., S-1-5-32-544 for the local Administrators group, etc.) should resolve from any computer. Bill -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: shebang env sh stopped working with coreutils-8.32-1
On 6/2/2022 8:49 AM, Daniel Jeliński wrote: Thank you for posting your steps, they helped me solve this issue. Everything on my end was similar, except that instead of bash configure I used a custom script that was supposed to prepare the environment. On closer inspection, it turned out that the script was downloading make 4.0 and running bash configure with parameter MAKE=/path/to/make-4.0. After removing that, the build finished without any issues. It was also much faster than with cygwin-3.2/make-4.0. I've added Magnus to the CC since he's the one who originally reported the jobserver issue. Magnus, does Daniel's solution also work for you? Can we consider this issue solved? Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: shebang env sh stopped working with coreutils-8.32-1
Hi Takashi, Thank you for posting your steps, they helped me solve this issue. Everything on my end was similar, except that instead of bash configure I used a custom script that was supposed to prepare the environment. On closer inspection, it turned out that the script was downloading make 4.0 and running bash configure with parameter MAKE=/path/to/make-4.0. After removing that, the build finished without any issues. It was also much faster than with cygwin-3.2/make-4.0. Thanks again, Daniel -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Permissions issues after installing Windows 10
On 2022-05-08 10:35, Andrey Repin wrote: Greetings, Brent Epp! I recently (finally) installed Windows 10 on my system (clean install). All of my files are stored in on a secondary drive/partition, on which cygwin is also installed. I expected to be able to just pick up where I left off, but I'm getting all sorts of permissions issues with cygwin. I did run the cygwin setup again to reinstall/upgrade. First, I had restore my cygwin home directory from a backup, since it was giving me permissions errors on .bash_history, .ssh, etc, but the biggest headache is with git repos. First, it gives a "fatal: unsafe repository" error. If I add it to the safe directories list, it git still has to reindex the repo every time I run `git status`, and it still fails when I try to enter a commit. It seems most or everything is owned by "Administrators". The only way I've been able to fix this is to go through the Windows advanced permissions dialog, change the owner to my user, and set all sub-objects to inheritable permissions, but I'm very leery about mass changes like this. Why did this happen? And is there a better/safer/correct way to fix this? The only way is to install a clean copy of Cygwin and carefully copy your changes over. This will ensure that all permissions are set correctly, and all programs are rebased correctly as well. This is because Windows uses a very different file access control that that of simple POSIX permissions, on top of which Cygwin emulates them. If you want your pain to be somewhat less in the future, move your home away from Cygwin directory and use noacl flag on it, which will defer permissions control to the underlying OS layer. I'm using my Windows profile as Cygwin home, but your mileage may vary. Thanks, I did try a clean install of cygwin. This has not resolved the issue. I think what's happened is that some of all files modified by by various command line programs (git, rsync, etc.) in cygwin have ended up with permissions that didn't carry across with the new Windows installation. In the [Security] tab for these files or directories, under "Group or user names", it lists the owner as "Account Unknown(S-...)". In some cases, these files are completely inaccessible and I can't even take ownership or change the permissions. I have to either restore them from a backup or boot to a Linux environment to access them. - Brent -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: shebang env sh stopped working with coreutils-8.32-1
On Wed, 1 Jun 2022 21:38:53 +0200 Daniel Jeliński wrote: > śr., 1 cze 2022 o 18:21 Ken Brown napisał(a): > > The original report on that issue > > (https://cygwin.com/pipermail/cygwin/2022-March/251095.html) described it as > > long-standing. Are you saying that it got worse with cygwin-3.3.x? That > > would > > be disappointing, because we overhauled the internal implementation of > > pipes in > > cygwin-3.3.0. > > Yessir. I'm also using Cygwin to build OpenJDK. With Cygwin 3.2.0, the > build starts with 8 threads and usually loses no more than 1-2 tokens; > with 3.3.5 the build either finishes with a single token, or segfaults > after a few seconds. > FWIW, I haven't seen any problems with single-threaded builds. How can we reproduce the losing jobserver token issue? I tried the following steps, however, no such messages appeared. 1) git clone https://git.openjdk.java.net/jdk/ 2) cd jdk 3) export TEMP=/tmp 4) bash configure 5) make images The summary of the configuration is as follows: Configuration summary: * Name: windows-x86_64-server-release * Debug level:release * HS debug level: product * JVM variants: server * JVM features: server: 'cds compiler1 compiler2 epsilongc g1gc jfr jni-check jvmci jvmti management parallelgc serialgc services shenandoahgc vm-structs zgc' * OpenJDK target: OS: windows, CPU architecture: x86, address length: 64 * Version string: 19-internal-adhoc.yano.jdk (19-internal) * Source date:Determined at build time Tools summary: * Environment:cygwin version 3.3.5-341.x86_64, 2022-05-13 12:27 UTC; windows version 10.0.19044.1706; prefix "/cygdrive"; root "C:\cygwin64" * Boot JDK: java version "18" 2022-03-22 Java(TM) SE Runtime Environment (build 18+36-2087) Java HotSpot(TM) 64-Bit Server VM (build 18+36-2087, mixed mode, sharing) (at /cygdrive/c/progra~1/java/jdk-18) * Toolchain: microsoft (Microsoft Visual Studio 2022) * C Compiler: Version 19.32.31329 (at /cygdrive/c/progra~1/micros~1/2022/commun~1/vc/tools/msvc/1432~1.313/bin/hostx86/x64/cl.exe) * C++ Compiler: Version 19.32.31329 (at /cygdrive/c/progra~1/micros~1/2022/commun~1/vc/tools/msvc/1432~1.313/bin/hostx86/x64/cl.exe) Build performance summary: * Build jobs: 8 * Memory limit: 16136 MB $ cygcheck -c autoconf make zip unzip Cygwin Package Information Package VersionStatus autoconf 15-1 OK make 4.3-1 OK unzip6.0-17 OK zip 3.0-12 OK -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
