Re: [PATCH cygport] Increase _FORTIFY_SOURCE level from 2 to 3 in CFLAGS

2024-04-28 Thread ASSI via Cygwin-apps
Christian Franke via Cygwin-apps writes: > _FORTIFY_SOURCE=3 is supported by Cygwin 3.5.0 headers and Cygwin gcc > 13.2.1 test release. > > Silently falls back to level 2 if level 3 is unsupported (older > headers or gcc) or to level 0 if unsupported at all (C++, clang). Well, if only that was

Re: [cygport] enabling a replacement for "objdump -d -l"

2024-03-12 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > But I'm not being oblique here. I really do want comments. Well, adding comments or proper POD is about the same effort, so I'd tend towards the latter. > I'm not sure what's so astounding about the suggestion that a fifty > line script should have some

Re: [cygport] enabling a replacement for "objdump -d -l"

2024-03-11 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > Thanks, this is great! You're welcome. > Please, please make a patch with git format-patch, which I can then > just apply. You can always just pull it in from my repo… when it's ready. > Fifty lines of perl with no comments! This is just line noise to me >

[ATTN. MAINTAINER] units

2024-03-04 Thread ASSI via Cygwin-apps
The postinstall script for units downloads currency exchange rates and hangs up for a long time if it can't access the server (if it ever finishes, I've killed the process on all machines where I've seen this). Can this part please either be removed entirely or moved into a sub-package that

Re: [cygport] enabling a replacement for "objdump -d -l"

2024-02-20 Thread ASSI via Cygwin-apps
Marco Atzeri via Cygwin-apps writes: > if works should not be the default ? Let's start with interested parties giving it a spin, shall we? ONce configured into your .cygportrc it essentially is the default for all your builds. > Reducing that time is very interesting for the big stuff That's

[cygport] enabling a replacement for "objdump -d -l"

2024-02-18 Thread ASSI via Cygwin-apps
Cygport uses "objdump -d -l" to extract the list of source files that need to be copied into the debuginfo package. This operation triggers some O(N²) or even higher complexity and in addition has been getting slower in recent binutils releases due to more and more information being put into

Re: Tmux crashes on copy

2024-02-17 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > I don't use tmux, so if I were to just bump the version, I'd just be > deploying the updated package without any testing, which is something > I try to avoid doing. I do, I just built it locally (with the dud patch that doesn't actually fix control mode backed

Re: [ITP] pigz 2.8

2024-01-25 Thread ASSI via Cygwin-apps
Marco Atzeri via Cygwin-apps writes: > BUILD_REQUIRES="zlib-devel ncompress gzip" Why is ncompress a build dependency? Please remove if possible. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2:

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2024-01-21 Thread ASSI via Cygwin-apps
小さい猫 via Cygwin-apps writes: > now updated to 15.0.7 I've built it and activated the tests, which seem to have roughly the same results as 9.0.1, so that looks good. For 9.0.1 I think I've finally got it to build almost cleanly. I still need to ignore some fallout from documentation bitrot, but

Re: [ITA] llvm

2024-01-15 Thread ASSI via Cygwin-apps
徐持恒 Xu Chiheng via Cygwin-apps writes: > Without process_install_dir_bin_symlinks, you can't get an installable > package *.xz. You have not explained what exactly the issue is you're trying to solve. If you get links to outside DESTDIR then the install targets are broken and you need to fix the

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2024-01-15 Thread ASSI via Cygwin-apps
小さい猫 via Cygwin-apps writes: > On Thursday, 14 December 2023 at 2:42 PM, 小さい猫 via Cygwin-apps > wrote: > >> By the way, just now I have updated these cygports to 13.0.1 LLVM release in >> my GitHub repo. > > now updated to 14.0.5 THanks for letting us know. I can't promise, but I'll try to

Re: [ITA] llvm

2024-01-14 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes: > That's mildly confusing to me… anyway, I'll try to build LLVM from this > (maybe this weekend). I expect there will need to be further changes to > the packaging, given how far out of date the cygport you based it on is. LLVM 16 does indeed build (di

Re: [ITA] llvm

2024-01-10 Thread ASSI via Cygwin-apps
徐持恒 Xu Chiheng via Cygwin-apps writes: > I'd like to adopt the llvm package. > I have build scripts and patches, and .cygport files at > https://github.com/xu-chiheng/Note. That's mildly confusing to me… anyway, I'll try to build LLVM from this (maybe this weekend). I expect there will need to

Re: Unmaintained packages in base package set

2024-01-07 Thread ASSI via Cygwin-apps
Takashi Yano via Cygwin-apps writes: > I found the cause. DISTCLEANFILES in original cygport file removes them. > Now I can successfully build libatk1.0-doc. Thanks! No, that means the tarball includes files that should get re-built, but apparently you somehow failed to do that. Regards, Achim.

[Attn. MAINTAINER] gpg2

2023-12-19 Thread ASSI via Cygwin-apps
Hi Marco, Since the last update gpg2 segfaults, rolling back step by step points at libgpg-error as the culprit. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld:

Re: [NMU] inkscape 0.92.3-2 (Test)

2023-12-11 Thread ASSI via Cygwin-apps
Mark Geisert via Cygwin-apps writes: > I've uploaded a non-maintainer re-build of the existing inkscape > 0.92.3. This attempts to work around a problem with the current > inkscape reported to exit with 127 error code (missing DLL). This > build was produced with gcc-g++ 7.4 while the current

Re: cygport upgrade to use gnupg2/gpg2 if available

2023-11-20 Thread ASSI via Cygwin-apps
Brian Inglis via Cygwin-apps writes: > After applying the attached patches, which add support for the newer > gpg2 from gnupg2 if installed, the attached log second chunk shows the > new keys verified by gpg2 added to lib/src_prep.cygpart > ___gpg_verify(). > > Similar code has been added to

Re: [PATCH cygport] git.cygclass: Suppress the depth option

2023-11-20 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > This could just be named something a little shorter, like > "GIT_URI_NO_SMART_TRANSPORT", since it's really a property of the > URI's host? > > But I wonder if wouldn't just be better to try with --depth and then > fallback to without it, if that fails

Re: [cygport RFC PATCH 1/1] Run install functions separately

2023-11-06 Thread ASSI via Cygwin-apps
Adam Dinwoodie via Cygwin-apps writes: > I think you've misunderstood how `set -e` works. Likely, for some definition of "works". I'm the last person to understand bash, really. […] > The issue is that the && chain disables `set -e` for anything other than > the final command in the chain,

Re: [cygport RFC PATCH 1/1] Run install functions separately

2023-11-03 Thread ASSI via Cygwin-apps
Adam Dinwoodie via Cygwin-apps writes: > When running as part of a `&&` chain, Bash's `set -e` behaviour is > suppressed entirely, which means calls that produce non-zero error codes > will be ignored if they're called inside functions that are part of such > a chain. > > To avoid silent failures

[Pending NMU] mysql, mariadb-connector-c

2023-10-22 Thread ASSI via Cygwin-apps
Due to a problem with a new major version of perl-DBD-mysql (trhat hasn't been resolved and will have to wait for an upstream fix) I've been looking at re-building those two packages. The updated packaging is available in the playground branches:

Re: Updated: mingw64-x86_64-/nghttp2 libnghttp2_14/-devel 1.57

2023-10-14 Thread ASSI via Cygwin-apps
Cygwin nghttp2 Maintainer via Cygwin-announce writes: > * libnghttp2_14 1.57 This library pulls in a lot of build dependencies, but then does not have any actual dependencies on anything. You seem to be building a static library? If so, please stop doing that. Regards,

Re: [Attn. Maintainers] OpenSSL v3

2023-10-11 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes: > Support for OpenSSL LTS v1.1.1 is ending on September 11. > > With the next release from upstream I will make OpenSSL LTS v3.0 current > on Cygwin. I've just rebuilt OpenSSH locally using the 3.0.10 test > package without any problems and unless y

Re: [PATCH setup] Enable large files (>2 GiB)

2023-10-10 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > This seems right, and works for installing qt5-webkit-debuginfo when I > gave it a quick try (seems to work on i686 as well). Oh good to know, so I don't need to boot up the machine that still has the 32bit installation for testing. > (Note that if you have

[PATCH setup] Enable large files (>2 GiB)

2023-10-08 Thread ASSI via Cygwin-apps
This fixes the issue reported here: https://cygwin.com/pipermail/cygwin/2023-October/254562.html Not tested on 32bit. --8<---cut here---start->8--- diff --git a/Makefile.am b/Makefile.am index 3bd83dc4..70bfd032 100644 --- a/Makefile.am +++ b/Makefile.am @@

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-09-05 Thread ASSI via Cygwin-apps
William Hu via Cygwin-apps writes: > Hi All, > > Re OCaml compilers: I should be able to package OCaml 4.14.1 (and hopefully > an > alpha version of 5.1.0 as well) for Cygwin in the coming weeks. OCaml 5.0.0 > temporarily dropped Cygwin support so the Cygwin versions will of course skip > that

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-09-05 Thread ASSI via Cygwin-apps
William Hu via Cygwin-apps writes: > On Wednesday, August 30th, 2023, ASSI wrote: >> NOt immediately, but it makes me wonder if there's other such leakage. >> I have not found a (text) file that stores this information in the >> installed package, so it seems that the information is compiled in >>

Re: The correct manner to obsolete subpackage.

2023-08-30 Thread ASSI via Cygwin-apps
Takashi Yano via Cygwin-apps writes: > But, my case is > >> If the package is really being removed without any replacement, there >> are mechanisms to deal with that case, but that case should be really rare. > > this. pulseaudio package no longer provides esound and gconf, > however, these

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-30 Thread ASSI via Cygwin-apps
William Hu via Cygwin-apps writes: > Just checked the file and I agree that CFLAGS looks a little funny - are > there any > other stupid flags/variables that you had in mind? NOt immediately, but it makes me wonder if there's other such leakage. I have not found a (text) file that stores this

Re: what license is this?

2023-08-28 Thread ASSI via Cygwin-apps
Andrew Schulman via Cygwin-apps writes: > https://github.com/jqlang/jq/blob/master/COPYING OpenSUSE License:CC-BY-3.0 AND MIT Fedora License:MIT and ASL 2.0 and CC-BY and GPLv3 Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-28 Thread ASSI via Cygwin-apps
小さい猫 via Cygwin-apps writes: >> - [ ] dtc (?) > > Ah sorry... that device tree compiler cygport repo in the github org > is not related to LLVM stuffs. just i happened to need it for building > something else and it's adapted from the old cygwinports-extras[1]. OK, I thought so already, but I

Re: [PATCH cygport] Add initial support for SOURCE_DATE_EPOCH

2023-08-28 Thread ASSI via Cygwin-apps
Christian Franke via Cygwin-apps writes: > If the build-path changes, more files differ (cygcheck.exe, ldd.exe, > cygserver.exe) because __FILE__ is used and expands to an absolute > path name. This could be fixed by adding -fmacro-prefix and/or -ffile-prefix arguments. Regards, Achim. --

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-27 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes: > I've started a local llvm-revival branch… Progress, OCaml bindings are back again (I've not run the tests yet): --8<---cut here---start->8--- * OCaml Updates - [X] flexdll 0.39 ==> 0.43 + does not recogn

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-26 Thread ASSI via Cygwin-apps
小さい猫 via Cygwin-apps writes: > i am not familiar with the ocaml stuffs, and i dont quite understand > what is the problem ur currently getting. Dune cannot be fully built because lwt.unix or one of it's dependencies is missing. I could built a bootstrapped package, but that later runs into

Re: [PATCH cygport] Add initial support for SOURCE_DATE_EPOCH

2023-08-24 Thread ASSI via Cygwin-apps
Christian Franke via Cygwin-apps writes: > If binutils, gzip and tar also would support this, the patch would be > empty :-) GZip has -n though and GNU tar --mtime and --clamp-mtime, so why not use that? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-17 Thread ASSI via Cygwin-apps
小さい猫 via Cygwin-apps writes: > On Monday, August 14th, 2023 at 12:50 AM, ASSI via Cygwin-apps > wrote: > >> I've started a local llvm-revival branch… I got sidetracked with OCaml, >> but that will need some more time and currently I have just disabled the >> OCa

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-14 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes: > I've started a local llvm-revival branch… I got sidetracked with OCaml, > but that will need some more time and currently I have just disabled the > OCaml bindings in LLVM instead (not removed: this is controlled by a > variable in the script and anot

Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust

2023-08-13 Thread ASSI via Cygwin-apps
I've started a local llvm-revival branch… I got sidetracked with OCaml, but that will need some more time and currently I have just disabled the OCaml bindings in LLVM instead (not removed: this is controlled by a variable in the script and another variable to control the LLVM target list).

[Attn. Maintainers] OpenSSL v3

2023-08-11 Thread ASSI via Cygwin-apps
Support for OpenSSL LTS v1.1.1 is ending on September 11. With the next release from upstream I will make OpenSSL LTS v3.0 current on Cygwin. I've just rebuilt OpenSSH locally using the 3.0.10 test package without any problems and unless your package has no current upstream I expect no

Re: [PATCH cygport] lib/src_prep.cygpart: Fix incorrect options passed to unzstd in unpack()

2023-08-07 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > Yes, I had managed to deduce that much. :) > > Providing a specific instance would save me having to find or invent > one, though. Sorry, I did not have one at hand, all such instances in my stack of packages are either uncompressed files or compressed

Re: [PATCH cygport] lib/src_prep.cygpart: Fix incorrect options passed to unzstd in unpack()

2023-08-04 Thread ASSI via Cygwin-apps
Yasutaka ATARASHI via Cygwin-apps writes: > Yeah, I also wonder why the --keep option is not used for .gz and .bz2. > Now, I recognized the reason. Thanks. > `unpack()` is expected to extract the files to the current working > directory regardless of the specified path of the input. Please see >

Re: [PATCH cygport] lib/src_prep.cygpart: Fix incorrect options passed to unzstd in unpack()

2023-08-04 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > Do you have an example of a cygport which fails without this fix, so I > can add a test for this? Anything with a SRC_URI or PATCH_URI that has .zst suffix but not .tar.zst should suffice. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb

Re: [PATCH cygport] lib/src_prep.cygpart: Fix incorrect options passed to unzstd in unpack()

2023-07-30 Thread ASSI via Cygwin-apps
yak_ex via Cygwin-apps writes: > `unpack()` invokes `unzstd` for a *.zst file as > `unzstd -qo file.zst` > Then, an error occurs as 'stdin is a console, aborting', > because the `-o` option is to specify an output file name. Indeed, sorry for that. > There are some choices to fix it. This patch

Re: [RFC] parallelizing cygport test

2023-07-24 Thread ASSI via Cygwin-apps
ASSI via Cygwin-apps writes: > I've recently updated a few packages that do a serious amount of > compilation during test and it became painfully obvious that cygtest > does not run make with the "-j" option nor does it currently offer an > option to change that. > > G

Re: chattr makes cygport slow

2023-07-23 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > Ok. I made a cygport 0.36.6 release with this change. Thanks. You haven't tagged that release on GitHub yet it seems. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional

[RFC] parallelizing cygport test

2023-07-23 Thread ASSI via Cygwin-apps
I've recently updated a few packages that do a serious amount of compilation during test and it became painfully obvious that cygtest does not run make with the "-j" option nor does it currently offer an option to change that. Given the brittleness of some test suites it might be prudent to

Re: chattr makes cygport slow

2023-07-16 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > The warning (error if RESTRICT=case_insensitive) should occur for all > commands, not just prep. OK. > How about the attached. Looks promising. > Even then, it should only be modifying every directory, not every file. Run strace on "chattr -r +C ." and see

[ITA] uchardet

2023-07-16 Thread ASSI via Cygwin-apps
For the record: I have adopted the uchardet package, previously orphaned by Yaakov. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: chattr makes cygport slow

2023-07-08 Thread ASSI via Cygwin-apps
Jon Turney via Cygwin-apps writes: > So, the idea here is that we try to ensure it's on, at least for the > working directory. That IMHO should only be done when the working directory is created, but not retroactively applied to an existing workdir. > Skipping it when 'finish' is used isn't

Re: [ITP] italic-man

2023-06-25 Thread ASSI via Cygwin-apps
[I've had no time to look at this in detail and that will have to wait a bit more.] Thomas Wolff via Cygwin-apps writes: >>> would it actually make a difference whether the zp_ is a script of >>> italic-man or of man-db? I've also added a cygport file to the >>> repository so you can try the

Re: Build machines

2023-06-24 Thread ASSI via Cygwin-apps
Achim Gratz 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

Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent

2023-05-02 Thread ASSI via Cygwin-apps
Marco Atzeri via Cygwin-apps writes: > are you planning to upload 5.36.1 as test ? No. > I will be on the road for 2 weeks in May and I will not be able to > update any package starting from 8th May I need to check another few hundred build logs this evening, then the release should be good to

Re: [ITP] openh264 (2.3.1)

2023-02-14 Thread ASSI via Cygwin-apps
Takashi Yano via Cygwin-apps writes: > Thanks for the advice. I have revised the cygport file. You are getting the file and the hash from the same unprotected source. I was thinking you should put the hash into the cygport file and hence the postinstall script. Also note that the system doing

Re: [ITP] openh264 (2.3.1)

2023-02-14 Thread ASSI via Cygwin-apps
Takashi Yano via Cygwin-apps writes: > - The libopenh264 package includes only /etc/postinstall > and /etc/preremove, which downloads/removes Cisco's dll > (binary) as well as license file. This is a Windows / MingW64 DLL, not a Cygwin one? Also, since Cisco seems to be unable to correctly