On Saturday, October 19, 2024 03:27 AM, Sam Edge expressed:
> Cc: Sam Edge <sam.edge.cyg...@gmx.com>
>
> On 18/10/2024 20:54, José Isaías Cabrera wrote:
> > On Friday, October 18, 2024 03:32 PM, Sam Edge expressed:
> >  > you
> >  > should be using a Microsoft or MSYS2/MinGW native (or Cygwin MinGW
> >  > cross) toolchain and pointing it to Windows native Tcl libraries.
> >
> > I am. These are my commands in cygwin to create the tools:
> >
> > To install the new version in cygwin:
> > ./configure --enable-all --prefix=/usr --disable-tcl && make install
> > [snip]
>
> I'm afraid my expertise (such as it is!) doesn't extend to MinGW, sorry,
> but you'll need to install or build MinGW compatible Tcl libraries and
> point your build tools to them. I see there are some available via
> Cygwin setup (packages mingw64-i686-tcl, mingw64-x86_64-tcl) but whether
> they are sufficient I don't know.

This is a great idea. I have not tried this. I will give it a try. Thanks.

> Since you're building non-Cygwin Windows binaries you may get more
> knowledgable support from the MinGW forums/mailing lists rather than
> here. Best of luck.

Thanks. I also installed sys2 and the same thing is happening. Thanks.

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

Reply via email to