Re: Where to post instructions on building something under cygwin ...
On 2020-06-22 18:10, Eliot Moss wrote: > Dear fellow cygwin-ers ... > > A recent poster has prompted me to ask this question: > > Assuming someone wrote up the instructions for building / installing some > python > package under cygwin, where could those instructions go? Is there a place in > the cygwin web pages for such a thing? Or would this better go back with the > package in question (scipy), saying "Here's a recipe that some users have used > with success to install this package under cygwin." I would get someone to prepare a scipy.cygport file that documents the package info, home page, upstream source archive, build and runtime dependencies, and build process according to Cygwin packaging standards, and can be run by the cygport utility to reproducibly build the package. Someone could start with a copy of numpy.cygport, make the appropriate changes, and post here for review and help. If you can then get a python package maintainer to adopt the package, the package will be available thru the usual Cygwin distribution channels. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.] -- 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
ImageMagick maybe broken by libgs9 upgrade
I use ImageMagick to convert and crop shipping labels from PDFs generated by Ebay. On 6/8, this command worked: $ convert -density 300 -crop 1500x1200 label.pdf label.png Aborted (core dumped) The command still runs on PDFs that were not generated by Ebay, but I get the same error on old Ebay PDF files (from 6/8 and earlier) that previously converted and cropped without problems. This is in my /var/log/setup.log: 2020/06/09 19:52:15 29 install libgs9 9.52-2 2020/06/09 19:52:15 30 erase libgs9 9.27-2 Cropping in a separate step after converting to PNG still works: $ convert -density 300 label.pdf temp.png $ convert -crop 1500x1200 temp.png label.png But in case other ImageMagick functionality is also broken, this isn't a permanent solution. I tried to downgrade libgs9, but 9.27 is no longer an option in setup, even after I added another mirror. Thanks for your help! Emily -- 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
Where to post instructions on building something under cygwin ...
Dear fellow cygwin-ers ... A recent poster has prompted me to ask this question: Assuming someone wrote up the instructions for building / installing some python package under cygwin, where could those instructions go? Is there a place in the cygwin web pages for such a thing? Or would this better go back with the package in question (scipy), saying "Here's a recipe that some users have used with success to install this package under cygwin." Regards - Eliot -- 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: Files and folders created with invalid ACL
On 6/22/2020 3:59 PM, Eliot Moss wrote: On 6/22/2020 2:08 PM, Thorsten Kampe wrote: Maybe you took Andre slightly literally; rephrasing, what are your current Should have read "Andrey"! Eliot -- 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: Files and folders created with invalid ACL
On 2020-06-22 13:59, Eliot Moss wrote:
> On 6/22/2020 2:08 PM, Thorsten Kampe wrote:
>> * Andrey Repin (Mon, 22 Jun 2020 20:20:35 +0300)
>>>
icacls test.txt /verify
test.txt: Ace entries not in canonical order.
>>>
>>> This is normal. All conformant drivers MUST be able to correctly process
>>> such
>>> ACL's. "Non-canonical" does not mean "invalid".
>>
>> `lsd` reports an error ("os error 1336"). But that might simply
>> be a result of the "non canonical order".
>
> I agree; lsd seems to be being overly picky, not that you personally
> can do much about that.
>
Interestingly the issue does not occur with files created in
the user's Cygwin home directory but - for instance - in the
Documents folder of the user's Windows profile.
>>>
This is a fresh Cygwin installation on a test system. Has
anyone found a solution?
>>>
[1]
> http://cygwin.1069669.n5.nabble.com/Issues-with-ACL-settings-after-updating-to-the-latest-cygwin-dll-td124123.html
>
>>>
>
>>> Needs more specifics.
>>> How did you set your fstab, particularly cygdrive prefix? Any extra mounts?
>>> How did you modify nsswitch?
>>
>> As I wrote, it's a "fresh Cygwin installation on a test
>> system" that means the phenomennon is observable directly after
>> the installation.
>>
>> I did some testing: files created in the user's home directory
>> (/home/Administrator), the home directory (/home) and other sub
>> directories don't show the issue.
>>
>> If I create a file or directory directly under / or anywhere
>> else on the drive, the issue occurs.
>>
>> If that would be the case on my main workstation, I would be
>> fine with that. Unfortunately on my main workstation the issue
>> occurs everywhere.
>
> Maybe you took Andre slightly literally; rephrasing, what are your current
> fstab and nsswitch contents? I would also ask, what do icacls and getfacl
> show on your / directory (the some that is the root of the hierarchy where
> things aren't working for you)? It could be that fixing some entry there,
> and recursively, will get you to a good state.
Often setfacl -b on files may reduce the ACLs to simple canonical entries
u::rw[-x],g::r-[-x],o::r-[-x]
.\$USER:(F)
BUILTIN\$GROUP:(RX)
Everyone:(RX)
but you have to be careful that the same operation on directories keeps the
DACLs d:u::rwx,d:g::r-x,d:o::r-x
.\$USER:(F)
BUILTIN\$GROUP:(RX)
Everyone:(RX)
CREATOR OWNER:(OI)(CI)(IO)(F)
CREATOR GROUP:(OI)(CI)(IO)(RX)
Everyone:(OI)(CI)(IO)(RX)
as if the DACLs get stripped, files created under those directories often have
*NO* permissions: making them create only directories.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
--
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: change in handling quotes in cygwin package from 3.1.4-1 to 3.1.5-1
On 6/15/2020 12:21 PM, Josh Thompson wrote:
We recently noticed a change in double quote (") handling that is causing a
command we issue to fail. The command is:
[...]
3.1.4:
$ cmd.exe /c "echo \""
"
3.1.5:
$ cmd.exe /c "echo \""
\"
I can confirm this change in behavior, and I thought it would be completely
trivial to do a bisection to find the commit that caused it. Unfortunately, it
seems that the issue is somehow tied up with the fact that the toolchain used
for building the cygwin package was upgraded shortly after the release of 3.1.4.
An attempt to rebuild 3.1.4 with the current toolchain fails because of some
gcc/binutils changes. So I applied the attached patches, which were applied to
the Cygwin git master shortly after the release of 3.1.4, in order to make the
build succeed.
After installing the rebuilt 3.1.4, however, the cmd.exe call above exhibits the
"3.1.5" behavior rather than the "3.1.4" behavior. I can't see anything in the
patches that would explain this. I thought maybe it was a compiler optimization
problem, but rebuilding without optimization doesn't change anything.
I'm stumped.
Ken
>From 5f66c2c756c2b3b43e565e471c82ee4ed05a4adb Mon Sep 17 00:00:00 2001
From: Corinna Vinschen
Date: Wed, 26 Feb 2020 17:02:01 +0100
Subject: [PATCH] Cygwin: Makefile.in: add -fno-builtin-execve CFLAG when
building exec.o
gcc-9.2.0 has an execve builtin which uses the nothrow attribute.
This results in an error when aliasing execve to _execve for newlib:
exec.cc:88:23: error: 'int _execve(const char*, char* const*, char*
const*)' specifies less restrictive attribute than its target
'int execve(const char*, char* const*, char* const*)': 'nothrow'
[-Werror=missing-attributes]
88 | EXPORT_ALIAS (execve, _execve) /* For newlib */
Add the -fno-builtin-execve CFLAGS when building exec.o to override
the gcc builtin.
Signed-off-by: Corinna Vinschen
---
winsup/cygwin/Makefile.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/winsup/cygwin/Makefile.in b/winsup/cygwin/Makefile.in
index ca0633eb8..f273ba793 100644
--- a/winsup/cygwin/Makefile.in
+++ b/winsup/cygwin/Makefile.in
@@ -567,6 +567,8 @@ ifeq ($(target_cpu),i686)
exceptions_CFLAGS:=-fno-omit-frame-pointer
endif
endif
+# required since gcc 9.x
+exec_CFLAGS:=-fno-builtin-execve
fhandler_proc_CFLAGS+=-DUSERNAME="\"$(USER)\"" -DHOSTNAME="\"$(HOSTNAME)\""
fhandler_proc_CFLAGS+=-DGCC_VERSION="\"`$(CC) -v 2>&1 | tail -n 1`\""
--
2.27.0
>From 28382c97a5d5fd7366adbf7ce9445b1b4beb02a9 Mon Sep 17 00:00:00 2001
From: Corinna Vinschen
Date: Wed, 26 Feb 2020 16:50:34 +0100
Subject: [PATCH] Cygwin: posix timers: fix uninitialized variable
The variable returning the overrun count from the tracker object after
disarming the overrun counter was not correctly initialized. For some
reason this has only been noticed by gcc-9.2.0, not by the formerly used
gcc-7.4.0.
This problem should not have had any runtime impact. The method
timer_tracker::disarm_overrun_event is supposed to be called in
lock-step with timer_tracker::arm_overrun_event, which in turn
results in the variable getting a valid value.
Signed-off-by: Corinna Vinschen
---
winsup/cygwin/posix_timer.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/winsup/cygwin/posix_timer.cc b/winsup/cygwin/posix_timer.cc
index c0d548fe9..75cd4fa60 100644
--- a/winsup/cygwin/posix_timer.cc
+++ b/winsup/cygwin/posix_timer.cc
@@ -81,7 +81,7 @@ timer_tracker::arm_overrun_event (LONG64 exp_cnt)
LONG
timer_tracker::disarm_overrun_event ()
{
- LONG ret;
+ LONG ret = 0;
AcquireSRWLockExclusive ();
if (overrun_count != OVR_DISARMED)
--
2.27.0
>From ba2f251d439294c7087f3a38a8d407c95cdc5c1e Mon Sep 17 00:00:00 2001
From: Jon Turney
Date: Wed, 26 Feb 2020 18:48:51 +
Subject: [PATCH] Cygwin: Update dumper for bfd API changes
Update dumper for bfd API changes in binutils 2.34
libbfd doesn't guarantee API stability, so we've just been lucky this
hasn't broken more often.
See binutils commit fd361982.
---
winsup/utils/dumper.cc | 30 ++
winsup/utils/parse_pe.cc | 4
2 files changed, 26 insertions(+), 8 deletions(-)
diff --git a/winsup/utils/dumper.cc b/winsup/utils/dumper.cc
index f71bdda8b..226c2283d 100644
--- a/winsup/utils/dumper.cc
+++ b/winsup/utils/dumper.cc
@@ -39,6 +39,20 @@
#define NOTE_NAME_SIZE 16
+#ifdef bfd_get_section_size
+/* for bfd < 2.34 */
+#define get_section_name(abfd, sect) bfd_get_section_name (abfd, sect)
+#define get_section_size(sect) bfd_get_section_size(sect)
+#define set_section_size(abfd, sect, size) bfd_set_section_size(abfd, sect,
size)
+#define set_section_flags(abfd, sect, flags) bfd_set_section_flags(abfd, sect,
flags)
+#else
+/* otherwise bfd >= 2.34 */
+#define get_section_name(afbd, sect) bfd_section_name (sect)
+#define get_section_size(sect) bfd_section_size(sect)
+#define set_section_size(abfd, sect, size) bfd_set_section_size(sect, size)
+#define
Re: Files and folders created with invalid ACL
On 6/22/2020 2:08 PM, Thorsten Kampe wrote:
> * Andrey Repin (Mon, 22 Jun 2020 20:20:35 +0300)
>>
>>> icacls test.txt /verify
>>> test.txt: Ace entries not in canonical order.
>>
>> This is normal. All conformant drivers MUST be able to correctly process such
>> ACL's. "Non-canonical" does not mean "invalid".
>
> `lsd` reports an error ("os error 1336"). But that might simply
> be a result of the "non canonical order".
I agree; lsd seems to be being overly picky, not that you personally
can do much about that.
>>> Interestingly the issue does not occur with files created in
>>> the user's Cygwin home directory but - for instance - in the
>>> Documents folder of the user's Windows profile.
>>
>>> This is a fresh Cygwin installation on a test system. Has
>>> anyone found a solution?
>>
>>> [1]
http://cygwin.1069669.n5.nabble.com/Issues-with-ACL-settings-after-updating-to-the-latest-cygwin-dll-td124123.html
>>
>> Needs more specifics.
>> How did you set your fstab, particularly cygdrive prefix? Any extra mounts?
>> How did you modify nsswitch?
>
> As I wrote, it's a "fresh Cygwin installation on a test
> system" that means the phenomennon is observable directly after
> the installation.
>
> I did some testing: files created in the user's home directory
> (/home/Administrator), the home directory (/home) and other sub
> directories don't show the issue.
>
> If I create a file or directory directly under / or anywhere
> else on the drive, the issue occurs.
>
> If that would be the case on my main workstation, I would be
> fine with that. Unfortunately on my main workstation the issue
> occurs everywhere.
Maybe you took Andre slightly literally; rephrasing, what are your current
fstab and nsswitch contents? I would also ask, what do icacls and getfacl
show on your / directory (the some that is the root of the hierarchy where
things aren't working for you)? It could be that fixing some entry there,
and recursively, will get you to a good state.
Regards - Eliot Moss
--
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: Files and folders created with invalid ACL
* Andrey Repin (Mon, 22 Jun 2020 20:20:35 +0300)
>
> Greetings, Thorsten Kampe!
>
> > I'm experiencing the issue described here[1]: files and folders
> > created with Cygwin utilities like touch and mkdir have an
> > incorrect ACL ("The access control list (ACL) structure is
> > invalid (os error 1336)").
>
> > icacls test.txt /verify
> > test.txt: Ace entries not in canonical order.
>
> This is normal. All conformant drivers MUST be able to correctly process such
> ACL's. "Non-canonical" does not mean "invalid".
`lsd` reports an error ("os error 1336"). But that might simply
be a result of the "non canonical order".
> > Interestingly the issue does not occur with files created in
> > the user's Cygwin home directory but - for instance - in the
> > Documents folder of the user's Windows profile.
>
> > This is a fresh Cygwin installation on a test system. Has
> > anyone found a solution?
>
> > [1]
> > http://cygwin.1069669.n5.nabble.com/Issues-with-ACL-settings-after-updating-to-the-latest-cygwin-dll-td124123.html
>
> Needs more specifics.
> How did you set your fstab, particularly cygdrive prefix? Any extra mounts?
> How did you modify nsswitch?
As I wrote, it's a "fresh Cygwin installation on a test
system" that means the phenomennon is observable directly after
the installation.
I did some testing: files created in the user's home directory
(/home/Administrator), the home directory (/home) and other sub
directories don't show the issue.
If I create a file or directory directly under / or anywhere
else on the drive, the issue occurs.
If that would be the case on my main workstation, I would be
fine with that. Unfortunately on my main workstation the issue
occurs everywhere.
Thorsten
--
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: Files and folders created with invalid ACL
Greetings, Thorsten Kampe!
> I'm experiencing the issue described here[1]: files and folders
> created with Cygwin utilities like touch and mkdir have an
> incorrect ACL ("The access control list (ACL) structure is
> invalid (os error 1336)").
> icacls test.txt /verify
> test.txt: Ace entries not in canonical order.
This is normal. All conformant drivers MUST be able to correctly process such
ACL's. "Non-canonical" does not mean "invalid".
> Interestingly the issue does not occur with files created in
> the user's Cygwin home directory but - for instance - in the
> Documents folder of the user's Windows profile.
> This is a fresh Cygwin installation on a test system. Has
> anyone found a solution?
> [1]
> http://cygwin.1069669.n5.nabble.com/Issues-with-ACL-settings-after-updating-to-the-latest-cygwin-dll-td124123.html
Needs more specifics.
How did you set your fstab, particularly cygdrive prefix? Any extra mounts?
How did you modify nsswitch?
--
With best regards,
Andrey Repin
Monday, June 22, 2020 20:10:13
Sorry for my terrible english...
--
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: Cygwin Setup says, "could not open /etc/xml/catalog for saving // add command failed". Am I safe to ignore it?
My Name via Cygwin writes: > Thank you, but I find catalog already present, as a file rather than a > directory; so I'll hold off unless you say mkdir is really what I should do: No, the file is correct. The following worked for me: > chmod a+x /etc/xml/catalog > /etc/postinstall/fontconfig_dtd.sh.done ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- 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: Cygwin Setup says, "could not open /etc/xml/catalog for saving // add command failed". Am I safe to ignore it?
BTW, Cygwin Setup 64 showed me that error message at the end of installing this set of Cygwin packages: python27, bzr, emacs-w32, aspell, aspell-en, octave. On Sun, Jun 21, 2020 at 11:13 PM My Name wrote: > Thank you, but I find catalog already present, as a file rather than a > directory; so I'll hold off unless you say mkdir is really what I should do: > > = > $ cat /etc/xml/catalog > > V1.0//EN" " > http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd;> > > > > > $ > = > > On Sun, Jun 21, 2020 at 10:07 PM Marco Atzeri via Cygwin < > cygwin@cygwin.com> wrote: > >> On 22.06.2020 04:48, My Name via Cygwin wrote: >> > [image: CygwinSetup64ErrorMessage-000.png] >> > >> > /var/log/setup: >> > >> > === >> > ... >> > 2020/06/21 17:21:30 running: C:\cygwin64\bin\bash.exe --norc --noprofile >> > "/etc/postinstall/fontconfig_dtd.sh" >> > could not open /etc/xml/catalog for saving >> > add command failed >> > 2020/06/21 17:21:30 abnormal exit: exit code=2 >> > ... >> > === >> > >> >> try >> >>mkdir /etc/xml/catalog >>/etc/postinstall/fontconfig_dtd.sh >> >> -- >> 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 >> > -- 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: Apparent bug in either (1) Cygwin default Package-list or (2) Package "bzr" dependency-list
> -Original Message- > From: My Name > Sent: Monday, June 22, 2020 2:34 AM > To: Allen Hewes > Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2) > Package "bzr" dependency-list > > > WSL2 > > At your convenience, can you please link to instructions on how to install and > start WSL2? I spent some hours searching and trying, but all I found was > people asking Microsoft for instructions, Microsoft giving answers, people > saying the Microsoft's answers didn't work, and the Microsoft agents > disappearing; and a variety of conflicting instructions on Microsoft's site, > as if > they had changed the installation / startup procedure repeatedly, without > leaving a trail to whichever method is current. I forgot to add that you can't run WSL2 and VirtualBox at the same time. WSL2 uses Hyper-V under the covers and that's incompatible with VirtualBox atm. You can make VirtualBox run with Hyper-V but the scuttlebutt is you'd have much more fun watching paint dry than running VirtualBox guests on Hyper-V... If you use VirtualBox don't use WSL2. /allen Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Apparent bug in either (1) Cygwin default Package-list or (2) Package "bzr" dependency-list
> -Original Message- > From: My Name > Sent: Monday, June 22, 2020 2:34 AM > To: Allen Hewes > Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2) > Package "bzr" dependency-list > > > WSL2 > > At your convenience, can you please link to instructions on how to install and > start WSL2? I spent some hours searching and trying, but all I found was > people asking Microsoft for instructions, Microsoft giving answers, people > saying the Microsoft's answers didn't work, and the Microsoft agents > disappearing; and a variety of conflicting instructions on Microsoft's site, > as if > they had changed the installation / startup procedure repeatedly, without > leaving a trail to whichever method is current. > This is it: https://docs.microsoft.com/en-us/windows/wsl/install-win10. So as with lots of Microsoft docs, you'll need to read the fine print, because it matters with WSL2. Install WSL first, then upgrade to WSL2. You need the just released Windows 10 2004 version. WSL2 just landed "regular folks" in Windows 10 2004 (20H1). ...and we are moving the thread from it's original intent... Now, keep in mind that even with WSL, you will run into Python 2 deprecation issues. For instance, I prefer to use Fedora when I use Linux. The next version of Fedora won't have Python 2 as an installable option. So you'll be in the same Python 2 boat. Now, if you choose to run (and pay for) an "Enterprise OS" (cough, cough), you'll be OK, but in 2020 who does that? :trollface: I guess you could run one of the LTS Ubuntu's... I don't have any direct experience with Ubuntu myself. /allen Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. -- 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: Cygwin Setup says, "could not open /etc/xml/catalog for saving // add command failed". Am I safe to ignore it?
Thank you, but I find catalog already present, as a file rather than a directory; so I'll hold off unless you say mkdir is really what I should do: = $ cat /etc/xml/catalog http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd;> $ = On Sun, Jun 21, 2020 at 10:07 PM Marco Atzeri via Cygwin wrote: > On 22.06.2020 04:48, My Name via Cygwin wrote: > > [image: CygwinSetup64ErrorMessage-000.png] > > > > /var/log/setup: > > > > === > > ... > > 2020/06/21 17:21:30 running: C:\cygwin64\bin\bash.exe --norc --noprofile > > "/etc/postinstall/fontconfig_dtd.sh" > > could not open /etc/xml/catalog for saving > > add command failed > > 2020/06/21 17:21:30 abnormal exit: exit code=2 > > ... > > === > > > > try > >mkdir /etc/xml/catalog >/etc/postinstall/fontconfig_dtd.sh > > -- > 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 > -- 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
