Re: postinstall: fontconfig abnormal exit
On Thu, 10 Sep 2020 08:40:24 -0600
Brian Inglis wrote:
> On 2020-09-10 04:57, Fergus Daly via Cygwin wrote:
> Sorry if this has been asked 4 million times already.
> >
> >>> $ head /etc/postinstall/{fontconfig_dtd,libxml2}.*
> >>==> /etc/postinstall/fontconfig_dtd.sh.done <==
hmmm. i don't understand exactly what this thread is about, but i do know that
on my latest fresh install of cygwin, the fontconfig_dtd install is claiming an
error at the end.
is this related to that ?
--
Brian
--
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: Error using cntlm
>Hi, >When I fire this command: >âcntlm -c cntlm.ini -M http://www.google.deâ >Iâm getting this error: >â0 [main] cntlm 22772 find_fast_cwd: WARNING: Couldn't compute FAST_CWD >pointer.â >Another problem is that I cannât generate encrypted password, but maybe it >is problem z my organization network settings. >âPassword: >Config profile 1/4... >Connection to proxy failed, bailing outâ >MF >This e-mail and the documents attached are covered business secret the Atos >group entities and contain confidential information intended solely for the >addressee. If you receive this e-mail in error, please notify the sender >immediately and destroy it. Atos Poland Global Services spóÅka z ograniczonÄ > odpowiedzialnoÅciÄ with its registered office in Bydgoszcz (previously Atos >Global Delivery Center Polska spóÅka z ograniczonÄ odpowiedzialnoÅciÄ >spóÅka komandytowa), address: 85-240 Bydgoszcz, Kraszewskiego 1 , entered in >the register of entrepreneurs of the National Judicial Register under the >number 811198 by the District Court in Bydgoszcz, XIII Commercial >Department of the National Judicial Register, NIP: 5213207288, share capital >PLN 3 805 500. As its integrity cannot be secured on the Internet, the Atos >group entities liability cannot be triggered for the message content. Although >the sender endeavors to maintain a computer virus-free network, the sender >does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings -- 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
Error using cntlm
Hi, When I fire this command: “cntlm -c cntlm.ini -M http://www.google.de” I’m getting this error: “0 [main] cntlm 22772 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.” Another problem is that I cann’t generate encrypted password, but maybe it is problem z my organization network settings. “Password: Config profile 1/4... Connection to proxy failed, bailing out” MF This e-mail and the documents attached are covered business secret the Atos group entities and contain confidential information intended solely for the addressee. If you receive this e-mail in error, please notify the sender immediately and destroy it. Atos Poland Global Services spółka z ograniczoną odpowiedzialnością with its registered office in Bydgoszcz (previously Atos Global Delivery Center Polska spółka z ograniczoną odpowiedzialnością spółka komandytowa), address: 85-240 Bydgoszcz, Kraszewskiego 1 , entered in the register of entrepreneurs of the National Judicial Register under the number 811198 by the District Court in Bydgoszcz, XIII Commercial Department of the National Judicial Register, NIP: 5213207288, share capital PLN 3 805 500. As its integrity cannot be secured on the Internet, the Atos group entities liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. -- 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
Setting up a proper modelling environment in Cygwin
Dear Cygwin users and developers, I am trying to run some models based on the ROMS ocean modeling system. And although I mainly run such models on Linux supercomputing systems, I sometimes use Cygwin to make test runs. However, whenever I install Cygwin on a new PC, I often find that my set up on an older PC I had been using doesn't work properly. After looking deeper into the issues, it seems that proper compilation requires that the same fortran compiler (gfortran in this case) be used to compile the necessary components. And as far as I understand, these components would mainly be: - zlib - hdf5 - netcdf - netcdf-fortran - openmpi As the gfortran compiler version number used for these different components is not indicated whenever I run cygwin setup-x86_64.exe, I am left to guess which version numbers for each to select. Of course, another option would be to accept the defaults for some components, and then compile my own version of say, netcdf, but this attempt almost always fails, and I'm not sure if this is due to conflicts with the already existing cygwin setup. Given the issues above, would anyone have any suggestions or recommendations on how to best achieve the setup I would like to have? I will greatly appreciate any help. Best regards, Lawrence -- 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: /dev/p* causes shell crash in i686
> > When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run > > any commands. They all give "The application was unable to start correctly > > (0xc022)". Anything different I should be doing? > > Check the permissions on cygwin1-20090909.dll. Is it executable? Doh. Thanks. Yeah, I made it executable and the problem with /dev/pt* now seems to be fixed. Thank you. And yes, I meant cygwin1-20200909.dll. Andrew -- 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
[ANNOUNCEMENT] ghostscript 9.53.0-1
The following packages have been uploaded to the Cygwin distribution: * ghostscript-9.53.0-1 * libgs9-9.53.0-1 * libgs-devel-9.53.0-1 GNU Ghostscript is a PostScript interpreter capable of converting PS files into a number of printer output formats. Ghostscript can also render PS files into a number of graphics file formats. This is an update to the latest upstream release. See http://www.ghostscript.com/doc/9.53.0/News.htm for a summary of the changes since the previous release. Ken Brown Cygwin's Ghostscript maintainer -- 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: /dev/p* causes shell crash in i686
On 2020-09-10 13:31, Thomas Wolff wrote: > Am 10.09.2020 um 21:19 schrieb Ken Brown via Cygwin: >> On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: On Sep 9 08:08, Andrew Schulman via Cygwin wrote: > Here's a strange one. In bash in i686, try to run: > > ls /dev/ptmx > > I only get about as far as: > > ls /dev/p > > and then my terminal window vanishes. This happens: > > * In fish or bash. > * On two different hosts that I've tried. > * In mintty or a system terminal. In the system terminal, sometimes the > command works normally the first time, but fails the 2nd time; or I have > to > press after `ls /dev/p`, then the terminal vanishes. > * With other commands that treat their arguments as files, not text. So > for > example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` > before the terminal window vanishes, but `echo /dev/ptmx` works normally. > > It doesn't happen: > > * In x86_64 - only i686. > * In scripts - only interactively. > > Is anyone else able to reproduce this? I've tried to capture an strace > log, > but I've failed so far. The strace seems to stop the crash. Still trying. > > I thought this could be a BLODA problem, but the two hosts I tried are > running different virus scanners (McAfee and Windows Defender). > > Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. > > Andrew I think I fixed it. I just uploaded new developer snapshots to https://cygwin.com/snapshots/ Please give them a try. >>> >>> When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run >>> any commands. They all give "The application was unable to start correctly >>> (0xc022)". Anything different I should be doing? >> >> Check the permissions on cygwin1-20090909.dll. Is it executable? > cygwin1-20090909.dll is 11 years old. Did you download the latest snapshot? The latest is 20200909, so I suspect his fingers got excited about 9s somewhere, plus the old one is no longer available: "The requested URL /snapshots/x86/cygwin1-20090909.dll.xz was not found on this server." -- 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: /dev/p* causes shell crash in i686
Am 10.09.2020 um 21:38 schrieb Ken Brown via Cygwin: On 9/10/2020 3:31 PM, Thomas Wolff wrote: Am 10.09.2020 um 21:19 schrieb Ken Brown via Cygwin: On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: On Sep 9 08:08, Andrew Schulman via Cygwin wrote: Here's a strange one. In bash in i686, try to run: ls /dev/ptmx I only get about as far as: ls /dev/p and then my terminal window vanishes. This happens: * In fish or bash. * On two different hosts that I've tried. * In mintty or a system terminal. In the system terminal, sometimes the command works normally the first time, but fails the 2nd time; or I have to press after `ls /dev/p`, then the terminal vanishes. * With other commands that treat their arguments as files, not text. So for example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` before the terminal window vanishes, but `echo /dev/ptmx` works normally. It doesn't happen: * In x86_64 - only i686. * In scripts - only interactively. Is anyone else able to reproduce this? I've tried to capture an strace log, but I've failed so far. The strace seems to stop the crash. Still trying. I thought this could be a BLODA problem, but the two hosts I tried are running different virus scanners (McAfee and Windows Defender). Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. Andrew I think I fixed it. I just uploaded new developer snapshots to https://cygwin.com/snapshots/ Please give them a try. When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run any commands. They all give "The application was unable to start correctly (0xc022)". Anything different I should be doing? Check the permissions on cygwin1-20090909.dll. Is it executable? cygwin1-20090909.dll is 11 years old. Did you download the latest snapshot? I'm sure that was just a typo. The 11-year-old one is not even available on the snapshot page. He could have a (very) old download sitting around somewhere and confused the download location. Just asked to make sure... In any case, I shouldn't have mentioned that in my reply. I should have told him to check the permissions on the (new) cygwin1.dll. 0xc022 is the NT status code STATUS_ACCESS_DENIED, so it's likely a permissions problem. 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 -- 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: /dev/p* causes shell crash in i686
On 9/10/2020 3:31 PM, Thomas Wolff wrote: Am 10.09.2020 um 21:19 schrieb Ken Brown via Cygwin: On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: On Sep 9 08:08, Andrew Schulman via Cygwin wrote: Here's a strange one. In bash in i686, try to run: ls /dev/ptmx I only get about as far as: ls /dev/p and then my terminal window vanishes. This happens: * In fish or bash. * On two different hosts that I've tried. * In mintty or a system terminal. In the system terminal, sometimes the command works normally the first time, but fails the 2nd time; or I have to press after `ls /dev/p`, then the terminal vanishes. * With other commands that treat their arguments as files, not text. So for example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` before the terminal window vanishes, but `echo /dev/ptmx` works normally. It doesn't happen: * In x86_64 - only i686. * In scripts - only interactively. Is anyone else able to reproduce this? I've tried to capture an strace log, but I've failed so far. The strace seems to stop the crash. Still trying. I thought this could be a BLODA problem, but the two hosts I tried are running different virus scanners (McAfee and Windows Defender). Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. Andrew I think I fixed it. I just uploaded new developer snapshots to https://cygwin.com/snapshots/ Please give them a try. When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run any commands. They all give "The application was unable to start correctly (0xc022)". Anything different I should be doing? Check the permissions on cygwin1-20090909.dll. Is it executable? cygwin1-20090909.dll is 11 years old. Did you download the latest snapshot? I'm sure that was just a typo. The 11-year-old one is not even available on the snapshot page. In any case, I shouldn't have mentioned that in my reply. I should have told him to check the permissions on the (new) cygwin1.dll. 0xc022 is the NT status code STATUS_ACCESS_DENIED, so it's likely a permissions problem. 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: /dev/p* causes shell crash in i686
On 2020-09-10 13:19, Ken Brown via Cygwin wrote: > On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: >>> On Sep 9 08:08, Andrew Schulman via Cygwin wrote: Here's a strange one. In bash in i686, try to run: ls /dev/ptmx I only get about as far as: ls /dev/p and then my terminal window vanishes. This happens: * In fish or bash. * On two different hosts that I've tried. * In mintty or a system terminal. In the system terminal, sometimes the command works normally the first time, but fails the 2nd time; or I have to press after `ls /dev/p`, then the terminal vanishes. * With other commands that treat their arguments as files, not text. So for example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` before the terminal window vanishes, but `echo /dev/ptmx` works normally. It doesn't happen: * In x86_64 - only i686. * In scripts - only interactively. Is anyone else able to reproduce this? I've tried to capture an strace log, but I've failed so far. The strace seems to stop the crash. Still trying. I thought this could be a BLODA problem, but the two hosts I tried are running different virus scanners (McAfee and Windows Defender). Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. Andrew >>> >>> I think I fixed it. I just uploaded new developer snapshots to >>> https://cygwin.com/snapshots/ Please give them a try. >> >> When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run >> any commands. They all give "The application was unable to start correctly >> (0xc022)". Anything different I should be doing? > > Check the permissions on cygwin1-20090909.dll. Is it executable? I recommend untar elsewhere and mv don't cp DLLs, especially cygwin1.dlls, as they seem to be able to get into a state showing such symptoms as above, even with local test builds, or after downloading and stripping Alternate Data Streams if present, tweaking perms and ACLs. -- 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: /dev/p* causes shell crash in i686
Am 10.09.2020 um 21:19 schrieb Ken Brown via Cygwin: On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: On Sep 9 08:08, Andrew Schulman via Cygwin wrote: Here's a strange one. In bash in i686, try to run: ls /dev/ptmx I only get about as far as: ls /dev/p and then my terminal window vanishes. This happens: * In fish or bash. * On two different hosts that I've tried. * In mintty or a system terminal. In the system terminal, sometimes the command works normally the first time, but fails the 2nd time; or I have to press after `ls /dev/p`, then the terminal vanishes. * With other commands that treat their arguments as files, not text. So for example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` before the terminal window vanishes, but `echo /dev/ptmx` works normally. It doesn't happen: * In x86_64 - only i686. * In scripts - only interactively. Is anyone else able to reproduce this? I've tried to capture an strace log, but I've failed so far. The strace seems to stop the crash. Still trying. I thought this could be a BLODA problem, but the two hosts I tried are running different virus scanners (McAfee and Windows Defender). Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. Andrew I think I fixed it. I just uploaded new developer snapshots to https://cygwin.com/snapshots/ Please give them a try. When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run any commands. They all give "The application was unable to start correctly (0xc022)". Anything different I should be doing? Check the permissions on cygwin1-20090909.dll. Is it executable? cygwin1-20090909.dll is 11 years old. Did you download the latest snapshot? -- 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: /dev/p* causes shell crash in i686
On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote: On Sep 9 08:08, Andrew Schulman via Cygwin wrote: Here's a strange one. In bash in i686, try to run: ls /dev/ptmx I only get about as far as: ls /dev/p and then my terminal window vanishes. This happens: * In fish or bash. * On two different hosts that I've tried. * In mintty or a system terminal. In the system terminal, sometimes the command works normally the first time, but fails the 2nd time; or I have to press after `ls /dev/p`, then the terminal vanishes. * With other commands that treat their arguments as files, not text. So for example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` before the terminal window vanishes, but `echo /dev/ptmx` works normally. It doesn't happen: * In x86_64 - only i686. * In scripts - only interactively. Is anyone else able to reproduce this? I've tried to capture an strace log, but I've failed so far. The strace seems to stop the crash. Still trying. I thought this could be a BLODA problem, but the two hosts I tried are running different virus scanners (McAfee and Windows Defender). Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. Andrew I think I fixed it. I just uploaded new developer snapshots to https://cygwin.com/snapshots/ Please give them a try. When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run any commands. They all give "The application was unable to start correctly (0xc022)". Anything different I should be doing? Check the permissions on cygwin1-20090909.dll. Is it executable? 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: /dev/p* causes shell crash in i686
> On Sep 9 08:08, Andrew Schulman via Cygwin wrote: > > Here's a strange one. In bash in i686, try to run: > > > > ls /dev/ptmx > > > > I only get about as far as: > > > > ls /dev/p > > > > and then my terminal window vanishes. This happens: > > > > * In fish or bash. > > * On two different hosts that I've tried. > > * In mintty or a system terminal. In the system terminal, sometimes the > > command works normally the first time, but fails the 2nd time; or I have to > > press after `ls /dev/p`, then the terminal vanishes. > > * With other commands that treat their arguments as files, not text. So for > > example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx` > > before the terminal window vanishes, but `echo /dev/ptmx` works normally. > > > > It doesn't happen: > > > > * In x86_64 - only i686. > > * In scripts - only interactively. > > > > Is anyone else able to reproduce this? I've tried to capture an strace log, > > but I've failed so far. The strace seems to stop the crash. Still trying. > > > > I thought this could be a BLODA problem, but the two hosts I tried are > > running different virus scanners (McAfee and Windows Defender). > > > > Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr attached. > > > > Andrew > > I think I fixed it. I just uploaded new developer snapshots to > https://cygwin.com/snapshots/ Please give them a try. When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I can't run any commands. They all give "The application was unable to start correctly (0xc022)". Anything different I should be doing? -- 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: postinstall: fontconfig abnormal exit
On 2020-09-10 04:57, Fergus Daly via Cygwin wrote:
Sorry if this has been asked 4 million times already.
>
>>> $ head /etc/postinstall/{fontconfig_dtd,libxml2}.*
>>==> /etc/postinstall/fontconfig_dtd.sh.done <==
>>> if [ -x /usr/bin/xmlcatalog ] ; then
>> /usr/bin/xmlcatalog --noout --add "system" "fonts.dtd"
>> /usr/share/xml/fontconfig/fonts.dtd /etc/xml/catalog
>> fi
> ==>> /etc/postinstall/libxml2.sh.done <==
>>> if test ! -f /etc/xml/catalog; then
>> /bin/mkdir -p /etc/xml
>> /usr/bin/xmlcatalog --noout --create /etc/xml/catalog
>> fi
>>> $ llgo /{etc/xml/,usr/bin/xml}catalog /usr/share/xml/fontconfig/fonts.dtd
>> /etc/postinstall/{fontconfig_dtd,libxml2}.*
>
>> Thank you!
>
> Out of interest:
> Is this something that would usually be achieved during setup, as in other
> instances of
> .sh -> .sh.done, but has just fallen off?
> Or (say) would it be achieved if I appended some specific package using setup
> -P?
> Or .. .. ?
Each of the postinstall scripts are installed as part of a package to perform
some aspect of installation that can not be done statically during the package
build as it may depend on dynamic aspects of each user's installation.
The Cygwin Setup program will normally rename the non-permanent (not starting
[0z][p-t]_...) postinstall scripts with suffix .done after successful execution,
so failure of the postinstall script is the usual reason they are not suffixed,
and that should be captured in /var/log/setup.log and /var/log/setup.log.full at
the end of each Setup run, and may be checked using:
$ fgrep -B1 'abnormal exit: exit code=' /var/log/setup.log*
showing e.g.
--
/var/log/setup.log-2015/10/18 07:27:14 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/
texlive-collection-basic.sh"
/var/log/setup.log:2015/10/18 07:27:26 abnormal exit: exit code=2
--
/var/log/setup.log-2016/03/10 17:33:13 running:
C:\usr\local\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.
dash"
/var/log/setup.log:2016/03/10 17:33:14 abnormal exit: exit code=127
--
/var/log/setup.log-2016/03/10 17:33:14 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/
zp_fontconfig_cache_1.sh"
/var/log/setup.log:2016/03/10 17:33:33 abnormal exit: exit code=3
--
/var/log/setup.log-2016/06/05 03:53:59 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/
zp_fontconfig_cache_1.sh"
/var/log/setup.log:2016/06/05 03:54:33 abnormal exit: exit code=1
--
/var/log/setup.log-2017/04/20 21:34:32 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile
"/etc/postinstall/postinstalltest.sh"
/var/log/setup.log:2017/04/20 21:34:32 abnormal exit: exit code=2
--
/var/log/setup.log-2017/09/07 18:49:13 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile
"/etc/postinstall/cygwin-doc.sh"
/var/log/setup.log:2017/09/07 18:49:13 abnormal exit: exit code=2
--
/var/log/setup.log-2017/09/08 23:16:33 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile
"/etc/preremove/cygwin-doc.sh"
/var/log/setup.log:2017/09/08 23:16:34 abnormal exit: exit code=1
--
/var/log/setup.log-2017/09/27 23:29:55 running:
C:\usr\local\cygwin64\bin\bash.exe --norc --noprofile
"/etc/preremove/rsnapshot.sh"
/var/log/setup.log:2017/09/27 23:29:55 abnormal exit: exit code=1
--
--
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: postinstall: fontconfig abnormal exit
>>> Sorry if this has been asked 4 million times already.
>> $ head /etc/postinstall/{fontconfig_dtd,libxml2}.*
>==> /etc/postinstall/fontconfig_dtd.sh.done <==
>> if [ -x /usr/bin/xmlcatalog ] ; then
> /usr/bin/xmlcatalog --noout --add "system" "fonts.dtd"
> /usr/share/xml/fontconfig/fonts.dtd /etc/xml/catalog
> fi
==>> /etc/postinstall/libxml2.sh.done <==
>> if test ! -f /etc/xml/catalog; then
> /bin/mkdir -p /etc/xml
> /usr/bin/xmlcatalog --noout --create /etc/xml/catalog
> fi
>> $ llgo /{etc/xml/,usr/bin/xml}catalog /usr/share/xml/fontconfig/fonts.dtd
> /etc/postinstall/{fontconfig_dtd,libxml2}.*
> Thank you!
Out of interest:
Is this something that would usually be achieved during setup, as in other
instances of
.sh -> .sh.done, but has just fallen off?
Or (say) would it be achieved if I appended some specific package using setup
-P?
Or .. .. ?
--
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
