Takashi Yano via Cygwin wrote:
On Mon, 24 Feb 2025 11:29:59 +0100
Christian Franke wrote:
Found with 'stress-ng --cpu-sched 1':
Testcase (attached):
$ uname -r
3.6.0-0.387.g8cebbb2b42bf.x86_64
$ gcc -o timersig timersig.c
$ ./timersig
638: fork()=639
!...!SIGSTOP: Per
Hi,
I have installed the following Python packages:
* python39
* python39-devel
* python39-pip
Then I've run `python3.9 -m venv venv`, which results in:
> Error: Command
'['/home/daab/build-essentials/venv/bin/python3.9.exe', '-Im',
'ensurepip', '--upgrade', '--default-pip']' returned non-ze
On Mar 5 17:16, Christian Franke via Cygwin wrote:
> Roland Mainz via Cygwin wrote:
> > Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
> > /usr/include/unistd.h and clang:
> > snip
> > $ clang --version
> > clang version 8.0.1 (tags/RELEASE_801/final)
> > Target: x
> The error is valid because the addition of this very old C++ feature
> took a very long time :-)
Well, it may be so, but adding the parameter names in those prototype on Cygwin
end of things would be a better and less disruptive approach, IMO.
$.02,
Anton Lavrentiev
Contractor NIH/NLM/NCBI
-
Roland Mainz via Cygwin wrote:
Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
/usr/include/unistd.h and clang:
snip
$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
$ cl
Maybe it's because -Wsystem-headers is not enabled? I'm unsure what gcc's
default behavior is with -Wall, but if you add an explicit -Wsystem-headers you
might still get that warning.
-Dimitry
> On 5 Mar 2025, at 19:58, Corinna Vinschen via Cygwin
> wrote:
>
> On Mar 5 17:16, Christian Fran
Hi!
Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
/usr/include/unistd.h and clang:
snip
$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
$ clang -std=gnu17 -Wall -
On Mar 5 20:10, Dimitry Andric via Cygwin wrote:
> Maybe it's because -Wsystem-headers is not enabled? I'm unsure what
> gcc's default behavior is with -Wall, but if you add an explicit
> -Wsystem-headers you might still get that warning.
Thanks, that was the reason. With -Wsystem-headers I can r
Dimitry-
Thanks for your response.
You have been very helpful.
I agree with your statement relating to the version determination.
I will await if the maintainer has any response before formulating my next
action.
If necessary, I can take this information you provided back to Tenable team and
try
On Wed, Mar 05, 2025 at 08:27:53PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin wrote:
> > We could change this to a macro instead:
> >
> > -static inline void setproctitle_init (int, char *[], char *[]) {}
> > +#define setproctitle_init(c, a, e)
>
> Changing to the empty marco removes
Dear list member(s),
I've reviewed the list archives for the last two months since subcomponent
release, and googled, but didn't find an answer for my question.
I'm encountering an issue with Tenable detecting a difference in version in our
security scans indicating that OpenSSH is still at a v
In my opinion, it is wrong that scanners rely on this information. :-) But
putting that discussion aside, the openssh-portable distribution does not
announce its "patch level" in its version banner by default.
See e.g. https://github.com/openssh/openssh-portable/blob/master/version.h,
where SSH
> We could change this to a macro instead:
>
> -static inline void setproctitle_init (int, char *[], char *[]) {}
> +#define setproctitle_init(c, a, e)
Changing to the empty marco removes the side effects in the arguments (such as
len++, for example),
which may silently break existing code -- so
13 matches
Mail list logo
