GCC doesn't find relative includes when passed paths using backward-slashes

2023-01-15 Thread Alexander Grund via Cygwin

Hi,

consider the following MWE:

|$ touch bar/foo.h $ cat bar/main.cpp #include "foo.h" int main(){} With this most simple setup 
calling GCC with `g++ "bar\main.cpp"` results in GCC failing to find the include file. However 
using `g++ "bar/main.cpp"` works as expected. |
|So the compiler does find the CPP file and also is able to resolve others paths passed 
with backslashes (e.g. -I arguments) but basically disables resolving includes relative 
to the file including it. For context: This turned up on CI for Boost where 
"|C:\cygwin64\bin" is added to the PATH env variable to be able to use the 
Cygwin GCC with B2. The build system, finding it is running on Windows, will pass paths 
with backward slashes to the compiler. This happens on both CMD with the added PATH and 
using the bash. For reference I tried the same with MinGW and there either path separator 
worked. So it seems to be an issue in the Cygwin builds of GCC. I tried both 11.2 and 
11.3, the latest currently available. Best Regards, Alexander Grund ||

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


Re: GCC doesn't find relative includes when passed paths using backward-slashes

2023-01-15 Thread Hans-Bernhard Bröker via Cygwin

Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin:

The build system, finding it is running on Windows, will pass paths with 
backward slashes to the compiler. 


And that's wrong.  Cygwin is not, for practical intents and purposes, 
Windows.  It just runs on top of it.


Yes, backslashed path names do work in some cases on Cygwin (note that 
in the case at hand, you did have to "" around the name for that to 
work).  But at some point that idea has to be given up to achieve the 
primary goal of emulating a Unix-like environment.


The correct solution thus becomes "Don't do that, then."  Fix the build 
system detection to recognize Cygwin as a type of Unix, and things will 
almost certainly just work.



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


Re: GCC doesn't find relative includes when passed paths using backward-slashes

2023-01-15 Thread Thomas Wolff via Cygwin



Am 15.01.2023 um 14:51 schrieb Hans-Bernhard Bröker via Cygwin:

Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin:

The build system, finding it is running on Windows, will pass paths 
with backward slashes to the compiler. 


And that's wrong.  Cygwin is not, for practical intents and purposes, 
Windows.  It just runs on top of it.


Yes, backslashed path names do work in some cases on Cygwin (note that 
in the case at hand, you did have to "" around the name for that to 
work).  But at some point that idea has to be given up to achieve the 
primary goal of emulating a Unix-like environment.


The correct solution thus becomes "Don't do that, then."  Fix the 
build system detection to recognize Cygwin as a type of Unix, and 
things will almost certainly just work.



It also depends on how your application, in this case gcc or rather cpp, 
handles path names.
If it uses library functions dirname and basename, it should work as you 
expect, but maybe it looks for '/' itself, so you cannot expect all 
applications to be patched for cygwin/Windows pathname support.


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


Re: [ANNOUNCEMENT] Updated: man-db-2.11.2-1

2023-01-15 Thread Henry S. Thompson via Cygwin
Achim Gratz via Cygwin writes:

> The man-db package is updated to the latest upstream version 2.11.2.

Thanks for this.  

> ...

> The diagnostic output from the update is stored at
> /var/log/mandb-index.log, so you can check if there were problems on
> the last update.

A quick scan of this reveals 86 warnings:

  54 whatis parse for ... failed
  29 bad symlink or ROFF `.so' request
   3 is a dangling symlink

Are any of these of any interest to ordinary users, as opposed to
package maintainers?

ht
-- 
   Henry S. Thompson, School of Informatics, University of Edinburgh
  10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk
   URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


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


[ANNOUNCEMENT] attr 2.5.1-1.20.g0981a7bfe487

2023-01-15 Thread Corinna Vinschen via Cygwin
The following packages have been uploaded to the Cygwin distribution:

* attr-2.5.1-1.20.g0981a7bfe487
* libattr-devel-2.5.1-1.20.g0981a7bfe487
* libattr1-2.5.1-1.20.g0981a7bfe487



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


[ANNOUNCEMENT] ghostscript 9.56.1-1

2023-01-15 Thread Ken Brown via Cygwin-announce via Cygwin
The following packages have been uploaded to the Cygwin distribution as test 
releases:


* ghostscript-9.56.1-1
* libgs9-9.56.1-1
* libgs-devel-9.56.1-1

GNU Ghostscript is a PostScript interpreter capable of converting PS files into 
a number of printer output formats.  Ghostscript can also render PS files into a 
number of graphics file formats.


This is an update to the latest upstream release in the 9.x series [*], with 
some patches from Fedora.  See


  http://www.ghostscript.com/doc/9.56.1/News.htm

for a summary of the changes since the previous release.  The most interesting 
change is that the PDF Interpreter has a new implementation written in C (rather 
than PostScript).


Ken

[*] The latest upstream release is 10.0.0, but I am not uploading it yet because 
of reported problems with TeX Live.


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


Re: [ANNOUNCEMENT] Updated: man-db-2.11.2-1

2023-01-15 Thread Achim Gratz via Cygwin
Henry S. Thompson via Cygwin writes:
> A quick scan of this reveals 86 warnings:
>
>   54 whatis parse for ... failed
>   29 bad symlink or ROFF `.so' request
>3 is a dangling symlink
>
> Are any of these of any interest to ordinary users, as opposed to
> package maintainers?

THese are warning, not errors.  There are tons of errors and
questionable ROFF constructs in the sources of various man pages, for
better or worse.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

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


Re: GCC doesn't find relative includes when passed paths using backward-slashes

2023-01-15 Thread Achim Gratz via Cygwin
Alexander Grund via Cygwin writes:
> consider the following MWE:
>
> |$ touch bar/foo.h $ cat bar/main.cpp #include "foo.h" int main(){}
> |With this most simple setup calling GCC with `g++ "bar\main.cpp"`
> |results in GCC failing to find the include file. However using `g++
> |"bar/main.cpp"` works as expected. |

Giving any Cygwin tools non-POSIX path constructs is asking for trouble,
notwithstanding the fact that sometimes it works (or seems to work).

> |So the compiler does find the CPP file and also is able to resolve
> | others paths passed with backslashes (e.g. -I arguments) but
> | basically disables resolving includes relative to the file including
> | it. For context: This turned up on CI for Boost where
> | "|C:\cygwin64\bin" is added to the PATH env variable to be able to
> | use the Cygwin GCC with B2. The build system, finding it is running
> | on Windows, will pass paths with backward slashes to the
> | compiler.

Then use a build system that doesn't do this.

> | This happens on both CMD with the added PATH and using the
> | bash. For reference I tried the same with MinGW and there either
> | path separator worked. So it seems to be an issue in the Cygwin
> | builds of GCC.

No it isn't, just like you couldn't expect this to work on Linux.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

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


[no subject]

2023-01-15 Thread Nouman Shahid via Cygwin
Bash 1876 error occured

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


vmstat yields error 'Unable to create system stat structure' on W11x64

2023-01-15 Thread System Administrator via Cygwin
Hello,

I am trying to migrate my framework to Windows 11 running Cygwin.
When executing vmstat it returns the following error:

"Unable to create system stat structure”

Using the very same packages (install files) on Windows 10, produces the proper 
vmstat results (i.e. no error).
I’ve tried W11 pro and Enterprise - same difference (none.) Windows 11 is 
running in a VMware VM. W11 is the December version wit the latest updates (as 
of today).
The working W10 is running on the same physical hardware, using the same 
version of VMware, also in a VM.
Cygwin is the latest version 3.4.3, with the latest props-ng package (4.0.2-1)

Any help (or at least hint) is greatly appreciated.

Bets wishes,

Immanuel.

PRS System Administrationmailto:sys...@prs.de
Patzschke + Rasp Software GmbH  http://www.prs.de
Bierstadter Straße 7   Fax: +49-(0)611-1731-0
D-65189 WiesbadenPhone: +49-(0)611-1731-0

Patzschke + Rasp Software GmbH, Bierstadter Str. 7, D-65189 Wiesbaden
Eintragung im Handelsregister: Amtsgericht Wiesbaden, HRB Nr. 22673
Geschäftsführer: Wolfgang Kechel, Till Immanuel Patzschke


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


Re: vmstat yields error 'Unable to create system stat structure' on W11x64

2023-01-15 Thread Adam Dinwoodie via Cygwin
On Sun, 15 Jan 2023 at 22:05, System Administrator via Cygwin wrote:
>
> Hello,
>
> I am trying to migrate my framework to Windows 11 running Cygwin.
> When executing vmstat it returns the following error:
>
> "Unable to create system stat structure”
>
> Using the very same packages (install files) on Windows 10, produces the 
> proper vmstat results (i.e. no error).
> I’ve tried W11 pro and Enterprise - same difference (none.) Windows 11 is 
> running in a VMware VM. W11 is the December version wit the latest updates 
> (as of today).
> The working W10 is running on the same physical hardware, using the same 
> version of VMware, also in a VM.
> Cygwin is the latest version 3.4.3, with the latest props-ng package (4.0.2-1)
>
> Any help (or at least hint) is greatly appreciated.

Can you provide the cygcheck output, per
https://cygwin.com/problems.html? It might be useful to have the
cygcheck output from both the Win10 and Win11 VMs to compare, but the
Win11 VM where things aren't working is going to be the most useful
one there.

It might also be useful to know how you're calling vmstat: are you
doing it from a Cygwin Bash shell within MinTTY, or from a PowerShell
prompt using Windows' console, or something else? And are you running
with Administrator privileges?

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


Re: vmstat yields error 'Unable to create system stat structure' on W11x64

2023-01-15 Thread System Administrator via Cygwin
Hello,

please find attached the cygcheck output - apologies for the oversight.

It does NOT make a difference whether the bash, run from MinTTY (desktop 
shortcut), is run “As Administrator” or as regular user, the error occurs in 
both scenarios.
Running it from PowerShell (both Admin and reg. user) yields the same error.

Thank you for your help - best wishes,

Immanuel.

P.S. W10 is an older version of Cygwin, but using that one on W11 produces the 
same erroneous results…



On 15. Jan 2023, at 23:19, Adam Dinwoodie  wrote:

On Sun, 15 Jan 2023 at 22:05, System Administrator via Cygwin wrote:

Hello,

I am trying to migrate my framework to Windows 11 running Cygwin.
When executing vmstat it returns the following error:

"Unable to create system stat structure”

Using the very same packages (install files) on Windows 10, produces the proper 
vmstat results (i.e. no error).
I’ve tried W11 pro and Enterprise - same difference (none.) Windows 11 is 
running in a VMware VM. W11 is the December version wit the latest updates (as 
of today).
The working W10 is running on the same physical hardware, using the same 
version of VMware, also in a VM.
Cygwin is the latest version 3.4.3, with the latest props-ng package (4.0.2-1)

Any help (or at least hint) is greatly appreciated.

Can you provide the cygcheck output, per
https://cygwin.com/problems.html? It might be useful to have the
cygcheck output from both the Win10 and Win11 VMs to compare, but the
Win11 VM where things aren't working is going to be the most useful
one there.

It might also be useful to know how you're calling vmstat: are you
doing it from a Cygwin Bash shell within MinTTY, or from a PowerShell
prompt using Windows' console, or something else? And are you running
with Administrator privileges?

PRS System Administrationmailto:sys...@prs.de
Patzschke + Rasp Software GmbH  http://www.prs.de
Bierstadter Straße 7   Fax: +49-(0)611-1731-0
D-65189 WiesbadenPhone: +49-(0)611-1731-0

Patzschke + Rasp Software GmbH, Bierstadter Str. 7, D-65189 Wiesbaden
Eintragung im Handelsregister: Amtsgericht Wiesbaden, HRB Nr. 22673
Geschäftsführer: Wolfgang Kechel, Till Immanuel Patzschke



cygcheck.out
Description: cygcheck.out

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