On Fri, 25 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> On Fri, 25 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
>
> > Nah, not hard or complicated, I already went through the process locally.
> > I just need to memorialize it in the cyport (and look at my setup log to
>
On Fri, 25 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> Nah, not hard or complicated, I already went through the process locally.
> I just need to memorialize it in the cyport (and look at my setup log to
> see the handful of sphinx packages I installed, off the top of my head
>
Name: Jeremy Drake
BEGIN SSH2 PUBLIC KEY
Comment: "Jeremy Drake"
B3NzaC1yc2EDAQABAAABAQDSw43bWANkUZLgTU1e9yedgMWHUBncobL2kY3bVe
ftXZTsx0aDy+fxvuFg1CwAREiSi/MYqHe4wagQfXVMOV+yHtP8PaWteGVOQ5NaLq2XPbQl
qGJ5a4wagu9ORE8Kf4krcfDB97Q571UQ9KZGN2fHnPN8UoAZwXPi1JRJgCEAFnHYf/KMOD
WthbF5YTjq5
On Fri, 25 Apr 2025, Philippe Baril Lecavalier via Cygwin-apps wrote:
> On 2025-04-25 3:28 p.m., Jeremy Drake via Cygwin-apps wrote:
> >
> > Do you think I should follow Debian here and use that fork? Do I have to
> > source the package from git then? Gentoo still fo
On Fri, 25 Apr 2025, Brian Inglis via Cygwin-apps wrote:
> Later (2014-12-25!) developer sources:
>
> https://github.com/vmt/udis86
>
> updated fork sources additions and fixes from multiple acked upstreams:
>
> https://github.com/canihavesomecoffee/udis86
>
> used by Debian packager:
On Fri, 25 Apr 2025, Philippe Baril Lecavalier via Cygwin-apps wrote:
> On Thu, 24 Apr 2025 19:02:29 -0700 (PDT)
> Jeremy Drake via Cygwin-apps wrote:
>
> > This package uses python3 at build time. I inherit-ed python3, would
> > I be better off putting it in BUILD_REQUIR
On Thu, 24 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> I figured I'd try my hand at a dead-simple package. Let me know if I
> screwed anything up, or when I should send my SSH key (which I think is
> the next step). 3 of the patches (not the cygwin-msys one) are from
>
I figured I'd try my hand at a dead-simple package. Let me know if I
screwed anything up, or when I should send my SSH key (which I think is
the next step). 3 of the patches (not the cygwin-msys one) are from
Gentoo.
https://repology.org/project/udis86/versions
udis86.cygport
Description: Binar
On Thu, 24 Apr 2025, Mark Geisert via Cygwin-apps wrote:
> Hi Jeremy,
>
> On 4/24/2025 11:57 AM, Jeremy Drake via Cygwin-apps wrote:
> > On Wed, 23 Apr 2025, Mark Geisert via Cygwin wrote:
> >
> > > A new version 1.4.17-4 of the cygutils packages with a corrected
On Wed, 23 Apr 2025, Mark Geisert via Cygwin wrote:
> A new version 1.4.17-4 of the cygutils packages with a corrected
> 'cygstart' is now making its way to the mirrors.
Can I ask why patches are made in the packaging rather than applied to
the cygwin-apps/cygutils git repository, given that this
On Fri, 25 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> On Thu, 24 Apr 2025 10:06:05 -0700 (PDT)
> Jeremy Drake wrote:
> > On Thu, 24 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> >
> > > Hi Jeremy,
> > >
> > > On Tue, 22 Apr 2025 15:50:52 +0900
> > > To avoid this incompatibility, I tried to
On Thu, 24 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> Hi Jeremy,
>
> On Tue, 22 Apr 2025 15:50:52 +0900
> To avoid this incompatibility, I tried to build llvm/clang without
> both 0005-use_cxx11_abi.patch and 0110-use_cxx11_abi.patch, and add
> -DCMAKE_CXX_STANDARD=20
> instead. It makes llvm
On Wed, 23 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> On Tue, 22 Apr 2025 12:46:16 -0700 (PDT)
> Jeremy Drake wrote:
> > On Wed, 23 Apr 2025, Takashi Yano wrote:
> >
> > > cygwin packages lack lld, so clang uses ld (correct2?) to link,
> > > which does not support other targets than x86 (i686
On Wed, 23 Apr 2025, Takashi Yano wrote:
> cygwin packages lack lld, so clang uses ld (correct2?) to link,
> which does not support other targets than x86 (i686, x86_64).
> Therefore I disabled them.
Correct. At least for cygwin target, it actually calls gcc to do the
link, which in turns calls
On Wed, 23 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> > #include
> >
> > int main() {
> > std::cout << "Hello" << std::endl;
> > return 0;
> > }
>
> Thanks. But In my environment, it works as expected.
>
> $ clang++ hello.cc
> $ ./a.exe
> Hello
> $
Great! It also works for me in MS
On Tue, 22 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> +set(CYGWIN_LIBRARIES ${MINGW_RUNTIME} cygwin advapi32
> +shell32 user32 kernel32 ${CYGWIN_RUNTIME})
Is that MINGW_RUNTIME right, or should it have been CYGWIN_RUNTIME in a
copy-paste error? Because MINGW_RUNT
On Tue, 22 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> > I've also seen a crash with a simple "Hello world" C++ iostreams program,
> > only on Cygwin not MSYS2. I suspect it is related to the C++11 ABI thing,
> > but it is not worked around by defining the macro. There should also be a
>
> C
On Tue, 22 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> I did a quick look through the attachments to the [ITA] llvm email
Sorry for the flurry of replies... I noticed you had an old, *wrong*
patch for dli_fname compile error in Signals.inc... See the correct
version in https://github.
On Tue, 22 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> On Tue, 22 Apr 2025, Takashi Yano via Cygwin-apps wrote:
>
> > Previously, Xu Chiheng offered ITA for llvm, however, we haven't
> > heard from him in over a year.
> >
> > Recently, I could successfull
On Tue, 22 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> Previously, Xu Chiheng offered ITA for llvm, however, we haven't
> heard from him in over a year.
>
> Recently, I could successfully build llvm/clang related packages
> version 20.1.2 thanks to MSYS2 guys.
>
> Therefore, I would like to ad
Nice! Please note that there are updated patches in MSYS2-packages/llvm
which replace some of the 'hack' patches with more proper methods (which I
opened PRs upstream for, but I've not gotten any replies to them yet).
Also, there is an issue currently outstanding, for which I opened an
upstream PR
On Sat, 19 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> On Sat, 19 Apr 2025, Brian Inglis via Cygwin-apps wrote:
>
> > That kind of thing would have to happen in the local Cygport or Scallywag CI
> > Windows environment, as the calm infrastructure is Fedora.
> >
> &
On Sat, 19 Apr 2025, Brian Inglis via Cygwin-apps wrote:
> That kind of thing would have to happen in the local Cygport or Scallywag CI
> Windows environment, as the calm infrastructure is Fedora.
>
> Could we use gendef and nm/objdump to compare Cygwin definitions and uses, or
> is there some loa
On Sat, 12 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> Maybe setting -DCMAKE_CXX_STANDARD=20 would work around this? It would at
> least take a different path in that if/elif block in basic_string.
It does indeed work around this, and builds a functional dylib llvm/clang
on Cygwin.
&
On Sat, 12 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> On Sat, 12 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
>
> > On Sun, 13 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> >
> > > > Yes. However, see my previous mail for the strange issue I ran into
>
On Sat, 12 Apr 2025, Jeremy Drake via Cygwin-apps wrote:
> On Sun, 13 Apr 2025, Takashi Yano via Cygwin-apps wrote:
>
> > > Yes. However, see my previous mail for the strange issue I ran into
> > > trying to do this (strange because it works fine on MSYS2 but fails on
&
On Sun, 13 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> > Yes. However, see my previous mail for the strange issue I ran into
> > trying to do this (strange because it works fine on MSYS2 but fails on
> > Cygwin)
>
> The same happens for me as well...
Maybe you'll have some luck debugging it.
On Sat, 12 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> Thanks for the advice. I was trying to build DLL with gcc.
> Now I can successfully build llvm without DLL using gcc.
>
> Next step I am trying is building clang using gcc. It seems
> that clang is the same, I mean, DLL should be disabled
On Thu, 10 Apr 2025, Jeremy Drake wrote:
> We (@mati865 and I) just managed to get llvm/clang 20.1.2 building and
> targeting Cygwin over at MSYS2, and I was wondering if you had anyone
> interested in these patches to update the package(s) in Cygwin? I'm not
> particularly interested in taking o
On Fri, 11 Apr 2025, Takashi Yano via Cygwin-apps wrote:
> On Thu, 10 Apr 2025 12:45:06 -0700 (PDT)
> Jeremy Drake wrote:
> > We (@mati865 and I) just managed to get llvm/clang 20.1.2 building and
> > targeting Cygwin over at MSYS2, and I was wondering if you had anyone
> > interested in these pat
On Fri, 11 Apr 2025, Jon Turney via Cygwin-apps wrote:
> Many thanks.
>
> I posted the patches to incorporate this in our CI here:
> https://cygwin.com/pipermail/cygwin-patches/2025q2/013646.html
>
> I'm not crazy about using pskill, not least because because it's a bit awkward
> to get into place
We (@mati865 and I) just managed to get llvm/clang 20.1.2 building and
targeting Cygwin over at MSYS2, and I was wondering if you had anyone
interested in these patches to update the package(s) in Cygwin? I'm not
particularly interested in taking on more responsibilities, but I guess I
could take
Fixes a warning "no return statement in function returning non-void",
and solves a crash running --help.
Hopefully this is the right place for this now, since I am not interesting
in becoming a package maintainer as the list description says ;)From f4821db24d4e4feca16e4aea58843128e233ef4e Mon Sep
33 matches
Mail list logo
