On Dec 8 16:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> Sorry for pressing this, I must be slow today.
>
> > just won't run correctly anymore on W7/8
>
> Won't or may not?
Won't
Corinna
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://
Sorry for pressing this, I must be slow today.
> just won't run correctly anymore on W7/8
Won't or may not?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com
On Dec 8 14:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
> > since the first 3.3.0 release in October 2021.
>
> I saw that. It did not look alarming. It basically was like "you'll be on
> your own".
>
> > Su
> for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
> since the first 3.3.0 release in October 2021.
I saw that. It did not look alarming. It basically was like "you'll be on
your own".
> Supporting older OSes requires to keep workarounds in the code and
Understood. But you
On Dec 7 17:59, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > contains patches dropping W7 and W8 support:
>
> Hmm... I understood that "dropping support" was not something that
> would _require_ newer OS, but that it may not work (or not guaranteed
> to work, patches not checked for
> contains patches dropping W7 and W8 support:
Hmm... I understood that "dropping support" was not something that would
_require_ newer OS,
but that it may not work (or not guaranteed to work, patches not checked for
compatibility, etc)
on the older OSes... Are you saying that W7 and W8 would b
On Dec 7 15:05, Daniel Abrahamsson via Cygwin wrote:
> > On Dec 7 12:50, Corinna Vinschen via Cygwin wrote:
> > > On Dec 7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > > > Hi,
> > > >
> > > > This morning I updated cygwin, and after that gcc started producing
> > > > errors like this:
> > >
On Dec 7 14:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > provided you run at least Windows 8.1
>
> Why would that be a requirement?
Test releases are created from the master branch which already
bumped version to 3.5.0 and contains patches dropping W7 and W8
support:
https://c
> On Dec 7 12:50, Corinna Vinschen via Cygwin wrote:
> > On Dec 7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > > Hi,
> > >
> > > This morning I updated cygwin, and after that gcc started producing
> > > errors like this:
> > >
> > > > gcc -Wall -Wextra -Werror -pedantic -Wno-unused-paramet
> provided you run at least Windows 8.1
Why would that be a requirement?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: htt
On Dec 7 12:50, Corinna Vinschen via Cygwin wrote:
> On Dec 7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > Hi,
> >
> > This morning I updated cygwin, and after that gcc started producing errors
> > like this:
> >
> > > gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg
> > >
On Dec 7 08:58, Daniel Abrahamsson via Cygwin wrote:
> Hi,
>
> This morning I updated cygwin, and after that gcc started producing errors
> like this:
>
> > gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE
> > -c -o ../obj/.o .c
> > gcc -o ../bin/ ../obj/.o -pg
> > /
Hi,
This morning I updated cygwin, and after that gcc started producing errors like
this:
> gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE
> -c -o ../obj/.o .c
> gcc -o ../bin/ ../obj/.o -pg
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
>
13 matches
Mail list logo