texlive 20230313-2

[Ken Brown via Cygwin-announce]

This is a rebuild of the TeX Live binaries against the latest zlib.  It 
should fix the problem reported here:


  https://cygwin.com/pipermail/cygwin/2023-August/254245.html

For some unknown reason I was unable to build pmx, so it is omitted from 
this release.  If that's a big inconvenience for anyone, let me know and 
I'll try harder.


Ken

[ANNOUNCEMENT] texlive 20230313-2

[Ken Brown via Cygwin-announce via Cygwin]

This is a rebuild of the TeX Live binaries against the latest zlib.  It 
should fix the problem reported here:


  https://cygwin.com/pipermail/cygwin/2023-August/254245.html

For some unknown reason I was unable to build pmx, so it is omitted from 
this release.  If that's a big inconvenience for anyone, let me know and 
I'll try harder.


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: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

[Brian Inglis via Cygwin]

On 2023-08-21 06:03, Martin Wege via Cygwin wrote:

On Sat, Aug 19, 2023 at 7:50 PM Brian Inglis  wrote:


On 2023-08-18 07:09, Martin Wege via Cygwin wrote:

On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin
 wrote:


On Aug 17 20:49, Martin Wege via Cygwin wrote:

On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin
 wrote:

and the result is the same.  Note that Cygwin supports MSFT NFSv3 but
not CITI NFSv4.1 internally.  No gurantee that Cygwin always does what
is necessary for that other NFS.


1. How does Cygwin detect whether something is a MSFT NFSv3, or not?
Cygwin /bin/mount lists the CITI NFSv4.1 as 'nfs', so there *IS*
something which detects that?


The filesystem name returned by NtQueryVolumeInformationFile is "NFS".
If any other NFS returns the same filesystem name, it will be treated
just like MSFT NFSv3.


2. Are Cygwin soft link handing depend on MSFT NFSv3 or not, i.e. does
the Cygwin soft link code behave differently for MSFT NFSv3 file
systems?


Yes.  NFS doesn't support symlink creation and symlink reading via
the usual functions, because Windows symlinks are created as reparse
points.  NFS doesn't support reparse points.  So the developers of
the MSFT NFS client had to invent their own way to create and
read NFS symlinks:

https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l1719

https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l2750


3. Does Cygwin implement the pathconf() api?


Yes.  Surprisingly, you can check this yourself by just calling the
function and trying to compile your code.


Apologies, how do we say in German? "Ich sollte meine Frage konkretisieren:"

Does the Cygwin implementation of pathconf() support query data of the
underlying filesystem based on data from the kernel, as UNIX does? So
pathconf() returns different values for NTFS, ReFS, or Windows builtin
NFSv3?

I am asking, because as far as I know the Linux implementation is not
a syscall, and instead glibc guesses values based on builtin static
data, and whatever fstatfs() has to offer. Compared to that UNIX
(Solaris, AIX, HPUX, ...) have pathconf() as a syscall, and actually
ask the filesystem itself.


Many library functions are implemented as documented either in the Cygwin
packages cygwin-doc and man-pages-posix available for installation; and use as
e.g. `man 3p fpathconf`, also available online at:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/fpathconf.html or
https://man7.org/linux/man-pages/man3/fpathconf.3p.html
and for comparison and reference we make Cygwin package man-pages-linux
available for installation; and use as e.g. `man -m linux 3 fpathconf`, also
available online at:

 https://man7.org/linux/man-pages/man3/fpathconf.3.html

suggestions for setup are in the package announcements made every 9-12 weeks
when the latest Linux man-pages package is released and updated on Cygwin.

Please also note that the getconf(1) program is installed as part of Cygwin and
can access f/pathconf variables associated with a pathname argument, as shown in
getconf(1) `man 1 getconf` and getconf(1p) `man 1p getconf`.


Thanks, but my question was about the Cygwin *implementation*: Does it
distinguish between NTFS, REFS, FAT, NFS? Does it use data obtained
from the Windows kernel at runtime, or does it rely on static data
compiled into the cygwin.dll library?


My suggestion was to encourage you to try out the command on the relevant 
filesystems, or feel free to check out the repo and the implementation.


You can search the mailing lists on inbox.sourceware.org/cygwin or mail-archive.

Volunteers focus on fixes to reproducible problems, adding function, upgrading 
packages, and quick answers to questions: the rest is up to you!


If you need professional support, try job forums to hire someone with the 
knowledge or skills to answer your questions.


--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry

--
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: lulatex problems after update of zlib

[Ken Brown via Cygwin]

On 8/21/2023 11:02 AM, ASSI via Cygwin wrote:

(although in this case maybe i got spooked by the change
from 1.2.x to 1.3)


It looks like that's exactly what happened.  The version check compares 
the first 4 characters of the version string.


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: lulatex problems after update of zlib

[ASSI via Cygwin]

Ken Brown via Cygwin writes:
> Thanks for the report.  I think I can fix this by rebuilding the TeX
> Live binaries with the new zlib.  I'll do that ASAP.

The ABI hasn't changed, so it would be good if you relaxed or removed
this check.  I've done that in a few other packages over the years.  For
Cygwin it just doesn't make sense to insist on one particular version of
any library (although in this case maybe i got spooked by the change
from 1.2.x to 1.3).


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:  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: lulatex problems after update of zlib

[Ken Brown via Cygwin]

On 8/21/2023 3:31 AM, Per Larsson via Cygwin wrote:

After the latest update of zlib (1.2.13 -> 1.3),  I’ve got a problem using 
lualatex:

“lualatex failed: PANIC: unprotected error in call to Lua API (zlib library 
version does not match - header: 1.2.13, library: 1.3)”

It can be avoided by resetting zlib to the previous version, but reporting here 
to notice the problem.


Thanks for the report.  I think I can fix this by rebuilding the TeX 
Live binaries with the new zlib.  I'll do that ASAP.


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: Error

[cygwinautoreply--- via Cygwin]

>Not sure if you guys still exist or not? But having a problem porting over
>to Windows 10 and getting this error. Any suggestions?


>1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
>Please report this problem to the public mailing list cygwin@cygwin.com

>Thanks,
>Rich Kent

>/Rich Kent///

>RK Racing – Aurora IL

>www.RichKentRacing.com 

>rkraci...@aol.com 

>630-542-0604


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

[Rich Kent via Cygwin]

Not sure if you guys still exist or not? But having a problem porting over
to Windows 10 and getting this error. Any suggestions?


1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
Please report this problem to the public mailing list cygwin@cygwin.com

Thanks,
--
Rich Kent

/Rich Kent///

RK Racing – Aurora IL

www.RichKentRacing.com 

rkraci...@aol.com 

630-542-0604

--
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: mkfifo: cannot set permissions of 'x.fifo': Not a directory

[Martin Wege via Cygwin]

On Fri, Aug 18, 2023 at 10:34 AM Corinna Vinschen
 wrote:
>
> On Aug 18 06:02, Martin Wege via Cygwin wrote:
> > On Mon, Aug 7, 2023 at 4:42 PM Martin Wege  wrote:
> > >
> > > Hello,
> > >
> > > We get a weird mkfifo failure in Cygwin on NTFS:
> > >
> > > /usr/bin/mkfifo -m 600 x.fifo
> > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > Is there a known workaround? So far named fifos cannot be created somehow.
> >
> > This is fixed for NTFS, but still broken for Windows builtin NFS v3 client:
>
> It was actually never supposed to work on NFS.  Cygwin FIFOs are
> created as symlinks of the type Windows shortcut with the R/O attribute
> set.  Those are only generated on NTFS and FAT filesystems.  NFS symlinks
> are generated using special magic.  NFS doesn't support DOS attributes.

NFS supports symlinks!
Easy solution would be to say that symlinks on NFS pointing to
:\0:c4:$inodenum are pipes on the local Cygwin machine.
/usr/bin/mkfifo on Cygwin creates a symlink :\0:c4:$inodenum. Cygwin
stat() functions turn symlinks with a value of :\0:c4:... to pipes.
Everyone is happy!

It does not have to be portable across different platforms. Just
portable enough that mkfifo in with bash scripts works on NFS.

Thanks,
Martin
>
> Corinna

-- 
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 pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

[Martin Wege via Cygwin]

On Sat, Aug 19, 2023 at 7:50 PM Brian Inglis  wrote:
>
> On 2023-08-18 07:09, Martin Wege via Cygwin wrote:
> > On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin
> >  wrote:
> >>
> >> On Aug 17 20:49, Martin Wege via Cygwin wrote:
> >>> On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin
> >>>  wrote:
>  and the result is the same.  Note that Cygwin supports MSFT NFSv3 but
>  not CITI NFSv4.1 internally.  No gurantee that Cygwin always does what
>  is necessary for that other NFS.
> >>>
> >>> 1. How does Cygwin detect whether something is a MSFT NFSv3, or not?
> >>> Cygwin /bin/mount lists the CITI NFSv4.1 as 'nfs', so there *IS*
> >>> something which detects that?
> >>
> >> The filesystem name returned by NtQueryVolumeInformationFile is "NFS".
> >> If any other NFS returns the same filesystem name, it will be treated
> >> just like MSFT NFSv3.
> >>
> >>> 2. Are Cygwin soft link handing depend on MSFT NFSv3 or not, i.e. does
> >>> the Cygwin soft link code behave differently for MSFT NFSv3 file
> >>> systems?
> >>
> >> Yes.  NFS doesn't support symlink creation and symlink reading via
> >> the usual functions, because Windows symlinks are created as reparse
> >> points.  NFS doesn't support reparse points.  So the developers of
> >> the MSFT NFS client had to invent their own way to create and
> >> read NFS symlinks:
> >>
> >> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l1719
> >>
> >> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/path.cc;hb=HEAD#l2750
> >>
> >>> 3. Does Cygwin implement the pathconf() api?
> >>
> >> Yes.  Surprisingly, you can check this yourself by just calling the
> >> function and trying to compile your code.
> >
> > Apologies, how do we say in German? "Ich sollte meine Frage konkretisieren:"
> >
> > Does the Cygwin implementation of pathconf() support query data of the
> > underlying filesystem based on data from the kernel, as UNIX does? So
> > pathconf() returns different values for NTFS, ReFS, or Windows builtin
> > NFSv3?
> >
> > I am asking, because as far as I know the Linux implementation is not
> > a syscall, and instead glibc guesses values based on builtin static
> > data, and whatever fstatfs() has to offer. Compared to that UNIX
> > (Solaris, AIX, HPUX, ...) have pathconf() as a syscall, and actually
> > ask the filesystem itself.
>
> Many library functions are implemented as documented either in the Cygwin
> packages cygwin-doc and man-pages-posix available for installation; and use as
> e.g. `man 3p fpathconf`, also available online at:
> https://pubs.opengroup.org/onlinepubs/9699919799/functions/fpathconf.html or
> https://man7.org/linux/man-pages/man3/fpathconf.3p.html
> and for comparison and reference we make Cygwin package man-pages-linux
> available for installation; and use as e.g. `man -m linux 3 fpathconf`, also
> available online at:
>
> https://man7.org/linux/man-pages/man3/fpathconf.3.html
>
> suggestions for setup are in the package announcements made every 9-12 weeks
> when the latest Linux man-pages package is released and updated on Cygwin.
>
> Please also note that the getconf(1) program is installed as part of Cygwin 
> and
> can access f/pathconf variables associated with a pathname argument, as shown 
> in
> getconf(1) `man 1 getconf` and getconf(1p) `man 1p getconf`.

Thanks, but my question was about the Cygwin *implementation*: Does it
distinguish between NTFS, REFS, FAT, NFS? Does it use data obtained
from the Windows kernel at runtime, or does it rely on static data
compiled into the cygwin.dll library?

Thanks,
Martin

-- 
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: [PATCH] Cygwin: pty: Fix failure to clear switch_to_nat_pipe flag.

[Corinna Vinschen]

On Aug 21 17:53, Takashi Yano wrote:
> Hi Corinna,
> 
> On Mon, 21 Aug 2023 10:20:30 +0200
> Corinna Vinschen wrote:
> > Hi Takashi,
> > 
> > On Aug 19 15:07, Takashi Yano wrote:
> > > After the commit fbfea31dd9b9, switch_to_nat_pipe is not cleared
> > > properly when non-cygwin app is terminated in the case where the
> > > pseudo console is disabled. This is because get_winpid_to_hand_over()
> > > sometimes returns PID of cygwin process even though it should return
> > > only PID of non-cygwin process. This patch fixes the issue by adding
> > > a new argument which requests only PID of non-cygwin process to
> > > get_console_process_id().
> > 
> > How critical is that? Do we need a 3.4.9 asap, or can we wait and
> > collect a few more bugfixes first?
> 
> This problem is affected only when pseudo console is not
> activated. So, most of Win10 users do not have this issue.
> However, Win7/8 users may notice some small gritch after
> non-cygwin app is executed.
> 
> BTW, are you noticed that dumper.exe is missing in 3.4.8?

No, I didn't, thanks for notifying me.

> When you release new cygwin to fix that, I would be happy
> if above patch will applied as well.

Yeah, it will certainly be a 3.4.9 soon :}


Corinna

Re: [PATCH] Cygwin: pty: Fix failure to clear switch_to_nat_pipe flag.

[Takashi Yano]

Hi Corinna,

On Mon, 21 Aug 2023 10:20:30 +0200
Corinna Vinschen wrote:
> Hi Takashi,
> 
> On Aug 19 15:07, Takashi Yano wrote:
> > After the commit fbfea31dd9b9, switch_to_nat_pipe is not cleared
> > properly when non-cygwin app is terminated in the case where the
> > pseudo console is disabled. This is because get_winpid_to_hand_over()
> > sometimes returns PID of cygwin process even though it should return
> > only PID of non-cygwin process. This patch fixes the issue by adding
> > a new argument which requests only PID of non-cygwin process to
> > get_console_process_id().
> 
> How critical is that? Do we need a 3.4.9 asap, or can we wait and
> collect a few more bugfixes first?

This problem is affected only when pseudo console is not
activated. So, most of Win10 users do not have this issue.
However, Win7/8 users may notice some small gritch after
non-cygwin app is executed.

BTW, are you noticed that dumper.exe is missing in 3.4.8?
When you release new cygwin to fix that, I would be happy
if above patch will applied as well.

Thanks.

-- 
Takashi Yano 

Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

[Corinna Vinschen via Cygwin]

On Aug 21 06:49, Cedric Blancher via Cygwin wrote:
> On Fri, 18 Aug 2023 at 10:35, Corinna Vinschen via Cygwin
>  wrote:
> >
> > On Aug 18 06:02, Martin Wege via Cygwin wrote:
> > > On Mon, Aug 7, 2023 at 4:42 PM Martin Wege  
> > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > We get a weird mkfifo failure in Cygwin on NTFS:
> > > >
> > > > /usr/bin/mkfifo -m 600 x.fifo
> > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > > >
> > > > Is there a known workaround? So far named fifos cannot be created 
> > > > somehow.
> > >
> > > This is fixed for NTFS, but still broken for Windows builtin NFS v3 
> > > client:
> >
> > It was actually never supposed to work on NFS.
> 
> Are you sure? AT AST and ARB (rDNA data cruncher) certainly have
> worked with Cygwin on NFS shares (Windows builtin, I think you call it
> MSFT NFSv3) in the past in our institute.
> 
> Tested with Cygwin 3.4.8: AST is not even building without such
> support, and ARB throws nasty errors in the cluster run setup phase
> II, because it cannot create the command fifo used for each cluster
> node.
> 
> >
> > Cygwin FIFOs are
> > created as symlinks of the type Windows shortcut with the R/O attribute
> > set.  Those are only generated on NTFS and FAT filesystems.  NFS symlinks
> > are generated using special magic.  NFS doesn't support DOS attributes.
> 
> So no Linux mkfifo support on NFS with Cygwin?

You're talking about Linux FIFOs, which don't make *any* sense on
Cygwin, and I'm talking about Cygwin FIFOs which don't make *any* sense
on Linux or, FWIW, a remote NFS fileystem.

So if you want Cygwin to be able to create FIFOs on a remote NFS, which
Cygwin won't be able to use, great.  I don't see any sense in that, but,
as usual, https://cygwin.com/acronyms/#PTC


Corinna

-- 
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: [PATCH] Cygwin: pty: Fix failure to clear switch_to_nat_pipe flag.

[Corinna Vinschen]

Hi Takashi,

On Aug 19 15:07, Takashi Yano wrote:
> After the commit fbfea31dd9b9, switch_to_nat_pipe is not cleared
> properly when non-cygwin app is terminated in the case where the
> pseudo console is disabled. This is because get_winpid_to_hand_over()
> sometimes returns PID of cygwin process even though it should return
> only PID of non-cygwin process. This patch fixes the issue by adding
> a new argument which requests only PID of non-cygwin process to
> get_console_process_id().

How critical is that? Do we need a 3.4.9 asap, or can we wait and
collect a few more bugfixes first?


Thanks,
Corinna

lulatex problems after update of zlib

[Per Larsson via Cygwin]

After the latest update of zlib (1.2.13 -> 1.3),  I’ve got a problem using 
lualatex:

“lualatex failed: PANIC: unprotected error in call to Lua API (zlib library 
version does not match - header: 1.2.13, library: 1.3)”

It can be avoided by resetting zlib to the previous version, but reporting here 
to notice the problem.



Sent from Mail for Windows


-- 
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