Updated: bash-completion/-devel 2.14

2024-05-11 Thread Cygwin bash-completion Maintainer
Command options and arguments auto-completion under the Bash shell

The following packages have been upgraded in the Cygwin distribution:

* bash-completion   2.14
* bash-completion-devel 2.14

bash-completion provides auto-completion for options of and arguments to
hundreds of commands; and a collection of shell functions to develop
those using the bash programmable completion commands.

For more information see the project home page:

https://github.com/scop/bash-completion

See below for changes since the last Cygwin release: for full details
see /usr/share/doc/bash-completion/CHANGELOG.md after installation or:

https://github.com/scop/bash-completion/blob/master/CHANGELOG.md


2.14.0  2024-05-09

Features

- cryptsetup: complete --header with filenames
- env: complete commands and variable assignments
- env: treat `-*` as the command name after `-` and `--`
- env: treat `-*` as the command name after assignments
- ip: Complete 'route get' options
- ip: Complete addr add/change/replace options
- ip: Complete ip route list options
- ip: Complete link afstats command
- ip: Complete neigh add, del, change, replace
- ip: Complete route save/showdump
- iperf: --tos/-S argument completion
- ssh-copy-id: (non-)complete args to `-t` and `-F`
- ssh-keygen: complete -r/-Y specific -O args
- ssh-keyscan: complete -O argument

Bug Fixes

- _comp_{compgen,xfunc}: use `declare -F --` for arbitrary funcs
- _comp_{load,realcommand}: handle option-like command name
- available_interfaces: strip only trailing colon from entries
- bash_completion,conftest: use `complete -p --` for arbitrary cmds
- fio: engines completion
- ip: Complete link change as well as set
- ip: Don't stop at proxy and nomaster in neigh
- scp remote_files: do not filter generated paths with "$cur"
- scp remote_files: localize variable `cur`
- ssh-keygen: handling of bundled short options
- ssh-keygen: make work with custom IFS
- ssh-keygen: suggest -O arg completions depending on mode
- use -- to pass arbitrary cmdnames to `_comp_load`
- use `pathcmd=$(type -P -- "$1")` for arbitrary cmds

-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
, and click 'Unsubscribe'.

If you need more information on unsubscribing, start reading here: 
.



Updated: Perl distributions

2024-05-11 Thread ASSI


The following Perl distributions have been updated to their latest
release version available on CPAN:

noarch
--
 perl-Business-ISBN-Data-20240509.001-1
 perl-Path-Tiny-0.146-1
 perl-Test-Compile-3.3.3-1

-- 
-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
, and click 'Unsubscribe'.

If you need more information on unsubscribing, start reading here: 
.



Updated: upx-4.2.4-1

2024-05-11 Thread ASSI


UPX has been updated to version 4.2.4, see the release news for changes:

https://upx.github.io/upx-news.txt

UPX is a free, portable, extendable, high-performance executable packer
for several executable formats.

-- 
-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
, and click 'Unsubscribe'.

If you need more information on unsubscribing, start reading here: 
.



Re: Wrong value for |FileNormalizedNameInfo| (|24| vs. |48|) in Cygwin 3.6 /usr/include ...

2024-05-11 Thread Brian Inglis via Cygwin

On 2024-05-11 05:30, Roland Mainz via Cygwin wrote:

I'm writing a test program for |FileNormalizedNameInfo| right now (see
https://rovema.kpaste.net/07074abc).
Per 
https://learn.microsoft.com/en-us/windows/win32/api/minwinbase/ne-minwinbase-file_info_by_handle_class
|FileNormalizedNameInfo| should be |24|, but on Cygwin 3.6 I get the
value |48|.
Since |GetFileInformationByHandleEx()| gives me error 87 (="Invalid
Parameter") for |48|, but works as intended for |24| I assume that the
Cygwin header is wrong.

Could someone please check the Cygwin header files ?


Could someone please read the enum constant names and classes carefully?

Package w32api-headers:


Headers:
 snip 
$ grep -r FileNormalizedNameInfo /usr/include/
/usr/include/w32api/ddk/wdm.h:  FileNormalizedNameInformation,
/usr/include/w32api/minwinbase.h:*FileNormalizedNameInfo*,
/usr/include/w32api/winternl.h:FileNormalizedNameInformation = 48,
 snip 


*FileNormalizedNameInfo* 24/0x18 is defined in minwinbase.h 
FILE_INFO_BY_HANDLE_CLASS for GetFileInformationByHandleEx whereas 
*FileNormalizedNameInformation* 44/0x2e is defined in winternl.h 
FILE_INFORMATION_CLASS for NtQueryInformationFile:


https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-ntifs-ntqueryinformationfile

ditto in ddk/wdm.h!

--
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: Build machines

2024-05-11 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes:
>> I misremembered the code names.  The direct successor to the 7735HS
>> (Rembrandt Refresh) are the 7840HS / 7940HS (Phoenix-H at 8 cores and
>> upgraded to 4nm Zen4/RDNA3 and about 15% better performance per Watt);
>> the upcoming 16 core is the 7945HX (Dragon Range, 5nm Zen4/RDNA2).
>
> The Phoenix mini PC are starting to appear right now, about 15%…20% more
> performance for about 150€…200€ higher price (about 40…50%) right now.
> Still waiting for Dragon Range, first teasers have popped up, so I think
> it'll be available before the end of the year.

I've finally got my hands on that Dragon Range mITX motherboard, paired
it with 96 GiB memory, 2×4TB NVMe and built it into a nice small
form-factor case.  I've decided to run it under Linux for now and
virtualize Windows via KVM.  Running the gcc compilation test as before,
but with a different version of gcc to be built and the objdump
improvements, so not directly comparable.  I'll see if and when I can
re-do the older tests with the current versions later.

   | Processor  | HW | Core| TDP |  Base | Turbo | aTurbo | 
L1i/L1d+L2 |L3 | Mem |  comp |  inst |  pack |  test |   tot |
   ||| | [W] | [MHz] | [MHz] |  [MHz] | 
[kiB]  | [MiB] | [GiB/s] | [min] | [min] | [min] | [min] | [min] |
   
|++-+-+---+---+++---+-+---+---+---+---+---|
   | Xeon E3-1276v3 | 1S/4C/8T   | Haswell |  84 |  3600 |  4000 |   3800 | 
32/32+256  | 8 |25.6 |   101 |15 | 9 |   445 |   570 |
   | EPYC 7252  | 2S/16C/32T | Zen2| 120 |  3100 |  3200 |   3200 | 
32/32+512  |   128 |   170.6 |   123 | 9 |10 |   200 |   342 |
   | Ryzen 7735HS   | 1S/8C/16T  | Zen3+   |  54 |  3200 |  4750 |   3850 | 
32/32+512  |16 |75.0 |68 |32 | 7 |   200 |   307 |
   
|++-+-+---+---+++---+-+---+---+---+---+---|
   | Ryzen 7845HX   | 1S/16C/32T | Zen4|  75 |  3000 |  5200 |   4000 | 
32/32+1024 |64 |81.2 |43 | 2 | 4 |   122 |   171 |

Efficiency wise this (expectedly) doesn't quite reach the level of the
miniPC for low and medium load, hovering around 23W at idle under Linux
and 60W with the Windows VM started and idling, peaking at about 130W
under full load, which makes it slightly more efficient than two miniPC
for this scenario.  Virtualization seems to consume around two cores
with high filesystem activity, so maybe bare-metal via dual-boot would
help a bit.  I can't test direct hardware passthrough for disks at the
moment, which might also help.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada


Wrong value for |FileNormalizedNameInfo| (|24| vs. |48|) in Cygwin 3.6 /usr/include ...

2024-05-11 Thread Roland Mainz via Cygwin
Hi!



I'm writing a test program for |FileNormalizedNameInfo| right now (see
https://rovema.kpaste.net/07074abc).

Per 
https://learn.microsoft.com/en-us/windows/win32/api/minwinbase/ne-minwinbase-file_info_by_handle_class
|FileNormalizedNameInfo| should be |24|, but on Cygwin 3.6 I get the
value |48|.
Since |GetFileInformationByHandleEx()| gives me error 87 (="Invalid
Parameter") for |48|, but works as intended for |24| I assume that the
Cygwin header is wrong.

Could someone please check the Cygwin header files ?

Headers:
 snip 
$ grep -r FileNormalizedNameInfo /usr/include/
/usr/include/w32api/ddk/wdm.h:  FileNormalizedNameInformation,
/usr/include/w32api/minwinbase.h:FileNormalizedNameInfo,
/usr/include/w32api/winternl.h:FileNormalizedNameInformation = 48,
 snip 

Cygwin version:
 snip 
$ uname -a
CYGWIN_NT-10.0-19045 okkoto 3.6.0-0.115.g579064bf4d40.x86_64
2024-04-09 21:11 UTC x86_64 Cygwin
 snip 



Bye,
Roland
-- 
  __ .  . __
 (o.\ \/ /.o) roland.ma...@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&& programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)

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