Re: Error

[cygwinautoreply--- via Cygwin]

>Not sure if you guys still exist or not? But having a problem porting over
>to Windows 10 and getting this error. Any suggestions?


>1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
>Please report this problem to the public mailing list cygwin@cygwin.com

>Thanks,
>Rich Kent

>/Rich Kent///

>RK Racing – Aurora IL

>www.RichKentRacing.com 

>rkraci...@aol.com 

>630-542-0604


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

-- 
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: error report

[cygwinautoreply--- via Cygwin]

>bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10      0 [main] 
>iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  
>Please report this problem tothe public mailing list cygwin@cygwin.com


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

-- 
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: Error running setup-x86_64.exe: syntax error in setup.zst

[Keith Thompson via Cygwin]

On Fri, Apr 7, 2023 at 2:40 AM Jon Turney  wrote:
>
> On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:
> > Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
> >
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 30182: syntax error, unexpected $undefined, expecting COMMA or NL
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 30182: unrecognized line 30183 (do you have the latest setup?)
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 30203: syntax error, unexpected $undefined, expecting COMMA or NL
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 30203: unrecognized line 30204 (do you have the latest setup?)
> >
> > (I can't copy the text from the message box so I retyped it.)
>
> Protip: Ctrl-C should work on a message box.

Yes, it does! You can't select part of the text and there's no visual
feedback, but if you select the message box and type Ctrl-C, it works.
That's going to be useful.

> > I re-downloaded setup-x86_64.exec, and it's identical to the one on my 
> > laptop.
> >
> > I'm using the mirrors.kernel.org mirror.
> > The setup.zst from mirrors.dotsrc.org is identical.
> > I decompressed setup.zst and I do see something suspicious on the
> > indicated lines.
> >
> > Here's line 30182:
> >
> > build-depends: \, bison, cygport, dblatex, docbook2X, flex,
> > gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel,
> > libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel,
> > libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel,
> > libpng-devel, libreadline-devel, libsqlite3-devel, libxslt,
> > python3-devel, texinfo
> >
> > Line 30203 is similar. I don't see a lone backslash anywhere else in the 
> > file.
>
> Yeah, this is wrong.
>
> I need to investigate further why the mechanisms which should have
> caught this didn't.
>
> > The setup.zst from mirrors.sonic.net does *not* have problematic
> > build-depends lines.
> > (Switching to a different mirror might be a workaround, but I haven't
> > tried it yet.)
> >
> > The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06
> > 20:42:10 UTC).
> > The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06
> > 15:36:11 UTC).
> > The bad one is about 5 hours newer than the good one.
> > I'm concerned that the bad setup.zst might propagate to other mirrors.
> This is fixed as of setup-timestamp: 1680860048
>
> Thanks very much for reporting this.
>
> Apologies for the inconvenience.

The mirror I use (mirrors.kernel.org) now has a setup.zst with a
newer timestamp (1680869581) and without the stray backslashes.

-- 
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: Error running setup-x86_64.exe: syntax error in setup.zst

[Jon Turney via Cygwin]

On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:

Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:

https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: unrecognized line 30183 (do you have the latest setup?)
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30203: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30203: unrecognized line 30204 (do you have the latest setup?)

(I can't copy the text from the message box so I retyped it.)


Protip: Ctrl-C should work on a message box.


I re-downloaded setup-x86_64.exec, and it's identical to the one on my laptop.

I'm using the mirrors.kernel.org mirror.
The setup.zst from mirrors.dotsrc.org is identical.
I decompressed setup.zst and I do see something suspicious on the
indicated lines.

Here's line 30182:

build-depends: \, bison, cygport, dblatex, docbook2X, flex,
gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel,
libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel,
libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel,
libpng-devel, libreadline-devel, libsqlite3-devel, libxslt,
python3-devel, texinfo

Line 30203 is similar. I don't see a lone backslash anywhere else in the file.


Yeah, this is wrong.

I need to investigate further why the mechanisms which should have 
caught this didn't.



The setup.zst from mirrors.sonic.net does *not* have problematic
build-depends lines.
(Switching to a different mirror might be a workaround, but I haven't
tried it yet.)

The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06
20:42:10 UTC).
The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06
15:36:11 UTC).
The bad one is about 5 hours newer than the good one.
I'm concerned that the bad setup.zst might propagate to other mirrors.

This is fixed as of setup-timestamp: 1680860048

Thanks very much for reporting this.

Apologies for the inconvenience.


--
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: Error running setup-x86_64.exe: syntax error in setup.zst

[Fergus Daly via Cygwin]

>> I'm concerned that the bad setup.zst might propagate to other mirrors.
Yes, identical error arising at
https://cygwin.mirror.uk.sargasso.net/x86_64/setup.zst
and elsewhere.



-- 
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: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Corinna Vinschen via Cygwin]

On Mar 14 09:30, Yeo Kai Wei via Cygwin wrote:
> Hi Corinna,
> 
> I can't update to 3.5+, I tried reinstalling using the Cygwin setup
> 
> Using "uname -a", my current version is 3.4.6-1.x86_64.
> 
> I assume 3.5 hasn't been released officially.
> 
> May I know where to get the test release?

In setup.  Use the version pulldown menu on the right side of the
"New" column, or the "Test" check mark at the top right.


Corinna

-- 
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: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Brian Inglis via Cygwin]

On 2023-03-13 21:44, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:

Please pay close attention to how the command was shown to you, including the 
use of the whitespace:


$ LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY



In the terminal, when I use $LC_MONETARY = "en_ZM.utf-8" locale -ck
LC_MONETARY
Cygwin replies "-bash: LC_MONETARY: command not found"


The dollar sign in there was the shell prompt; not something you have to type.

So, this is basically what and how you should enter it:

LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY


Try it using a known good locale first, then that locale.
Shut down all Cygwin processes.
Run setup-x86_64:
Select Packages/View Full/Search cygwin/column New dropdown/bottom 
entry/3.5.0-0.231.g93f70d7849b8, same for -devel and -doc if desired, then 
Search Clear, reset View Pending, then Next, ...

Run your terminal, redo the commands above, and you should see correct data.

--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry


--
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: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin]

Please pay close attention to how the command was shown to you, including the 
use of the whitespace:

> >$ LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY

> In the terminal, when I use $LC_MONETARY = "en_ZM.utf-8" locale -ck
> LC_MONETARY
> Cygwin replies "-bash: LC_MONETARY: command not found"

The dollar sign in there was the shell prompt; not something you have to type.

So, this is basically what and how you should enter it:

LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY

HTH,

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: https://cygwin.com/ml/#unsubscribe-simple

Re: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Yeo Kai Wei via Cygwin]

Hi Corinna,

I can't update to 3.5+, I tried reinstalling using the Cygwin setup

Using "uname -a", my current version is 3.4.6-1.x86_64.

I assume 3.5 hasn't been released officially.

May I know where to get the test release?


In the terminal, when I use $LC_MONETARY = "en_ZM.utf-8" locale -ck 
LC_MONETARY


Cygwin replies "-bash: LC_MONETARY: command not found"


Thank you very much.


Kind Regards,

YEO Kai Wei

On 13/3/2023 6:49 pm, Corinna Vinschen wrote:

On Mar 13 08:40, Yeo Kai Wei via Cygwin wrote:

Hi All,

May I ask if there's a bug with Cygwin and Windows currency?

The en_ZM locale isn't yet supported by Cygwin.  This will change with
Cygwin 3.5.0.  You can install the latest Cygwin test release
3.5.0-0.231.g93f70d7849b8 and retry.  You'll get the correct output:

Region: en_AU.utf-8 Currency symbol: $ International currency symbol: AUD
Region: en_CA.utf-8 Currency symbol: $ International currency symbol: CAD
Region: en_GB.utf-8 Currency symbol: £ International currency symbol: GBP
Region: en_US.utf-8 Currency symbol: $ International currency symbol: USD
Region: en_NZ.utf-8 Currency symbol: $ International currency symbol: NZD
Region: en_ZM.utf-8 Currency symbol: K International currency symbol: ZMW

Btw., you don't even need a test application, just call

   $ LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY


The correct answer should be "Region: en_ZM.utf-8 Currency symbol: K
International currency symbol: ZMK"

Supposedly, the code works on Linux.

Is this an issue with Windows?

We're fetching most locale information from Windows, this includes the
LC_MONETARY information.  However, the locale support up to Cygwin 3.4.x
is restricted by an issue in Windows:

Originally, locales were handled in Windows by using so called locale
identifiers, LCID, 2 byte numbers.  These LCIDs are used by Cygwin
internally.

In the meantime, Windows switched from LCIDs to locale string
identifiers following RFC 4646 resp. RFC 5646. Now, the problem is this:

Cygwin didn't yet follow suite, still using LCIDs internally, but
Windows introduced locales for which no LCID has ever been assigned.
Asking for the LCID for "en-ZW" returns 0.

For Cygwin 3.5.0, I converted Cygwin to use RFC 5646 locale strings
internally, too, so the next major version of Cygwin will be able to
support all locales Windows supports.


     while (regions[i])
     {
     setlocale(LC_MONETARY, regions[i]);

You're not checking for errors here.  If the locale isn't supported,
setlocale should return NULL...


     const struct lconv* loc = localeconv();

...and the locale information stays unchanged.  As such, if en_ZM isn't
supported, this call will still fetch the information of the en_NZ.utf-8
locale.


HTH,
Corinna


--
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: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Corinna Vinschen via Cygwin]

On Mar 13 08:40, Yeo Kai Wei via Cygwin wrote:
> Hi All,
> 
> May I ask if there's a bug with Cygwin and Windows currency?

The en_ZM locale isn't yet supported by Cygwin.  This will change with
Cygwin 3.5.0.  You can install the latest Cygwin test release
3.5.0-0.231.g93f70d7849b8 and retry.  You'll get the correct output:

Region: en_AU.utf-8 Currency symbol: $ International currency symbol: AUD
Region: en_CA.utf-8 Currency symbol: $ International currency symbol: CAD
Region: en_GB.utf-8 Currency symbol: £ International currency symbol: GBP
Region: en_US.utf-8 Currency symbol: $ International currency symbol: USD
Region: en_NZ.utf-8 Currency symbol: $ International currency symbol: NZD
Region: en_ZM.utf-8 Currency symbol: K International currency symbol: ZMW

Btw., you don't even need a test application, just call

  $ LC_MONETARY="en_ZM.utf-8" locale -ck LC_MONETARY

> The correct answer should be "Region: en_ZM.utf-8 Currency symbol: K
> International currency symbol: ZMK"
> 
> Supposedly, the code works on Linux.
> 
> Is this an issue with Windows?

We're fetching most locale information from Windows, this includes the
LC_MONETARY information.  However, the locale support up to Cygwin 3.4.x
is restricted by an issue in Windows:

Originally, locales were handled in Windows by using so called locale
identifiers, LCID, 2 byte numbers.  These LCIDs are used by Cygwin
internally.

In the meantime, Windows switched from LCIDs to locale string
identifiers following RFC 4646 resp. RFC 5646. Now, the problem is this:

Cygwin didn't yet follow suite, still using LCIDs internally, but
Windows introduced locales for which no LCID has ever been assigned.
Asking for the LCID for "en-ZW" returns 0.

For Cygwin 3.5.0, I converted Cygwin to use RFC 5646 locale strings
internally, too, so the next major version of Cygwin will be able to
support all locales Windows supports.

>     while (regions[i])
>     {
>     setlocale(LC_MONETARY, regions[i]);

You're not checking for errors here.  If the locale isn't supported,
setlocale should return NULL...

>     const struct lconv* loc = localeconv();

...and the locale information stays unchanged.  As such, if en_ZM isn't
supported, this call will still fetch the information of the en_NZ.utf-8
locale.


HTH,
Corinna

-- 
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: [ERROR] Locale Monetary Symbol Prints Wrongly on Windows : Cygwin

[Brian Inglis via Cygwin]

On 2023-03-12 18:40, Yeo Kai Wei via Cygwin wrote:

May I ask if there's a bug with Cygwin and Windows currency?


Windows Language Locale culture codes and currencies


This is the output from the code below.
Region: en_AU.utf-8 Currency symbol: $ International currency symbol: AUD
Region: en_CA.utf-8 Currency symbol: $ International currency symbol: CAD
Region: en_GB.utf-8 Currency symbol: £ International currency symbol: GBP
Region: en_US.utf-8 Currency symbol: $ International currency symbol: USD
Region: en_NZ.utf-8 Currency symbol: $ International currency symbol: NZD
Region: en_ZM.utf-8 Currency symbol: $ International currency symbol: NZD < 
ERROR
The correct answer should be "Region: en_ZM.utf-8 Currency symbol: K 
International currency symbol: ZMK"

 ZMW Zambia kwacha

Install Cygwin package units and see /usr/share/units/currencies.units:

$ units_cur
$ grep zambia /usr/share/units/currency.units
ZMWzambiakwacha
zambiakwacha  0.049970632087833 USD


Supposedly, the code works on Linux.
Is this an issue with Windows?
How can one solve this issue?

If you look at the Windows Locale culture id ref:

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f?source=recommendations

https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-LCID/%5bMS-LCID%5d.pdf

only two official languages are supported for Zambia and only since Windows 10:

"...
LanguageLocationLanguageLanguageSupported
(or type)   ID  tag version
...
Bemba   Zambia  0x1000  bem-ZM  Release 10
...
English Zambia  0x1000  en-ZM   Release 10
...
LanguageLanguage
ID  tag
0x1000  Locale without assigned LCID if the current user default locale.
See section 2.2.1.
...
2.2.1 Locale Names without LCIDs
Every locale name without an assigned LCID MAY be temporarily given one of the 
LCIDs in the following table, if the application requests an LCID.<14> These 
locale names include any valid [RFC5646] language tag.
Note: LCID assignments for Locale Names without LCIDs are temporary and are not 
suitable for use across a protocol, or for interchange between processes or 
machines.
These temporary LCID assignments are also unsuitable for tagging persisted data 
as the meaning of the LCID assignment will change over time.

...
NameValue   Conditions
LOCALE_CUSTOM_UNSPECIFIED<17>	0x1000	When an LCID is requested for a locale 
without a permanent LCID assignment, nor a temporary assignment as above, the 
protocol will respond with LOCALE_CUSTOM_UNSPECIFIED for all such locales. 
Because this single value is used for numerous possible locale names, it is 
impossible to round trip this locale, even temporarily.
Applications should discard this value as soon as possible and never persist it. 
If the system is forced to respond to a request for LCID_CUSTOM_UNSPECIFIED, it 
will fall back to the current user locale. This is often incorrect but may 
prevent an application or component from failing.
As the meaning of this temporary LCID is unstable, it should never be used for 
interchange or persisted data.

This is a 1-to-many relationship that is very unstable.
..."

So it looks like you can only use this if you set this to the current user 
default locale, or set that up under your own custom locale using one of the 
other termporary assignment ids available, and set the current user default 
locale to that.


Instructions for doing so are available out there on the web if you search hard!

--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry

--
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: [ERROR] msgget() "Function not implemented" Error : Cygwin

[Yeo Kai Wei via Cygwin]

How To Deal With the msgget() Issue and "Function not implemented" and 
Cygwin Server


1. Download the "*cygrunsrv*" binaries using "setup-x86_64.exe". Search 
for it at the DLL page. Download 1.64-1. Now you have Cygwin Server. 
This is usually not mentioned.


2. Run Cygwin as administrator. This is usually not mentioned.

3. Start the Cygwin server with "*net start cygserver*". It should say 
"The CYGWIN cygserver service is starting.
The CYGWIN cygserver service was started successfully.". You have to 
google this. It is not on the instruction page for some reason.


4. Run the program. It should work now.


On 28/2/2023 6:29 pm, Corinna Vinschen wrote:

On Feb 28 18:13, Yeo Kai Wei via Cygwin wrote:

Hi Cygwin,

May I ask if there will be an implementation of msgget() on Cygwin for
Windows?

There is, for ages.  However, you have to run cygserver for that
to work:

   https://cygwin.com/cygwin-ug-net/using-cygserver.html

If cygserver isn't running, the XSI IPC functions return ENOSYS.

Alternatively, convert your tool to using POSIX message queues, those
are using a file backed solution and don't require cygserver.


Corinna


--
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: [ERROR] msgget() "Function not implmented" Error : Cygwin

[Ken Brown via Cygwin]

[Please don't top-post.]

On 3/1/2023 6:56 AM, Yeo Kai Wei via Cygwin wrote:

Do you want to install cygserver as service?
(Say "no" if it's already installed as service) (yes/no) yes
/usr/bin/cygserver-config: line 181: cygrunsrv: command not found

Installation of cygserver as service failed.  Please check the
error messages you got.  They might give a clue why it failed.

A good start is either you don't have administrator privileges
or a missing cygrunsrv binary.  Please check for both."


May I ask what I should do next?


Did you check for the cygrunsrv binary?  If you don't have it, then 
install the cygrunsrv package.


Ken

--
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: [ERROR] msgget() "Function not implmented" Error : Cygwin

[Yeo Kai Wei via Cygwin]

Hi Corinna,

Thank you for the help.

I tried following the instructions on 
https://cygwin.com/cygwin-ug-net/using-cygserver.html#start-cygserver


There was a line, "Before you run Cygserver for the first time, you 
should run the /usr/bin/cygserver-config script once."


I googled for some instructions and it said to use "cygserver-config" in 
the Cygwin terminal.


I did it and the following is the reply from the terminal.

*Without admin privileges*

"$ cygserver-config
Generating /etc/cygserver.conf file
chown: changing ownership of '/etc/cygserver.conf': Permission denied


Warning: The following function requires administrator privileges!

Do you want to install cygserver as service?
(Say "no" if it's already installed as service) (yes/no) yes
/usr/bin/cygserver-config: line 181: cygrunsrv: command not found

Installation of cygserver as service failed.  Please check the
error messages you got.  They might give a clue why it failed.

A good start is either you don't have administrator privileges
or a missing cygrunsrv binary.  Please check for both."


*With admin privileges*
"$ cygserver-config
Overwrite existing /etc/cygserver.conf file? (yes/no) yes
Generating /etc/cygserver.conf file


Warning: The following function requires administrator privileges!

Do you want to install cygserver as service?
(Say "no" if it's already installed as service) (yes/no) yes
/usr/bin/cygserver-config: line 181: cygrunsrv: command not found

Installation of cygserver as service failed.  Please check the
error messages you got.  They might give a clue why it failed.

A good start is either you don't have administrator privileges
or a missing cygrunsrv binary.  Please check for both."


May I ask what I should do next?


Thank you very much.


Kind Regards,

YEO Kai Wei

P.S. How do you convert to using POSIX message queues in Cygwin?


On 28/2/2023 6:29 pm, Corinna Vinschen wrote:

On Feb 28 18:13, Yeo Kai Wei via Cygwin wrote:

Hi Cygwin,

May I ask if there will be an implementation of msgget() on Cygwin for
Windows?

There is, for ages.  However, you have to run cygserver for that
to work:

   https://cygwin.com/cygwin-ug-net/using-cygserver.html

If cygserver isn't running, the XSI IPC functions return ENOSYS.

Alternatively, convert your tool to using POSIX message queues, those
are using a file backed solution and don't require cygserver.


Corinna


--
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: [ERROR] msgget() "Function not implmented" Error : Cygwin

[Corinna Vinschen via Cygwin]

On Feb 28 18:13, Yeo Kai Wei via Cygwin wrote:
> Hi Cygwin,
> 
> May I ask if there will be an implementation of msgget() on Cygwin for
> Windows?

There is, for ages.  However, you have to run cygserver for that
to work:

  https://cygwin.com/cygwin-ug-net/using-cygserver.html

If cygserver isn't running, the XSI IPC functions return ENOSYS.

Alternatively, convert your tool to using POSIX message queues, those
are using a file backed solution and don't require cygserver.


Corinna

-- 
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: Error: child_copy: cygheap read copy failed.

[Corinna Vinschen via Cygwin]

On Jan 20 22:30, Takashi Yano via Cygwin wrote:
> On Fri, 20 Jan 2023 13:26:20 +0100
> Corinna Vinschen wrote:
> > On Jan 20 21:18, Takashi Yano via Cygwin wrote:
> > > On Fri, 20 Jan 2023 12:30:29 +0100
> > > Corinna Vinschen wrote:
> > > > Also, your ffplay executable isn't high-entropy-VA enabled, by any
> > > > chance?
> > > 
> > > I'm sorry, but the high-entropy-va is ebabled.
> > > 
> > > $ peflags -v /usr/bin/ff{mpeg,probe,play}
> > > /usr/bin/ffmpeg: 
> > > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> > >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> > > /usr/bin/ffprobe: 
> > > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> > >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> > > /usr/bin/ffplay: 
> > > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> > >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> > 
> > Btw., how did this happen?  The native Cygwin compiler/linker combo
> > usually doesn't set the dynamicbase and high-entropy-VA flags by
> > default...
> 
> Perhaps this is because configure of ffmpeg explicitly
> has the following lines:
> 
> check_ldflags -Wl,--nxcompat,--dynamicbase
> check_ldflags -Wl,--high-entropy-va # binutils 2.25

Oh, ok. The configurey should only do that on native Windows builds.

> Removing these lines makes ff{mpeg,probe,play} disable
> both high-entropy-va and dynamicbase flags.

Great!


Thanks,
Corinna

-- 
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: Error: child_copy: cygheap read copy failed.

[Takashi Yano via Cygwin]

On Fri, 20 Jan 2023 13:26:20 +0100
Corinna Vinschen wrote:
> On Jan 20 21:18, Takashi Yano via Cygwin wrote:
> > On Fri, 20 Jan 2023 12:30:29 +0100
> > Corinna Vinschen wrote:
> > > Also, your ffplay executable isn't high-entropy-VA enabled, by any
> > > chance?
> > 
> > I'm sorry, but the high-entropy-va is ebabled.
> > 
> > $ peflags -v /usr/bin/ff{mpeg,probe,play}
> > /usr/bin/ffmpeg: 
> > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> > /usr/bin/ffprobe: 
> > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> > /usr/bin/ffplay: 
> > coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
> >  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> 
> Btw., how did this happen?  The native Cygwin compiler/linker combo
> usually doesn't set the dynamicbase and high-entropy-VA flags by
> default...

Perhaps this is because configure of ffmpeg explicitly
has the following lines:

check_ldflags -Wl,--nxcompat,--dynamicbase
check_ldflags -Wl,--high-entropy-va # binutils 2.25

Removing these lines makes ff{mpeg,probe,play} disable
both high-entropy-va and dynamicbase flags.

-- 
Takashi Yano 

-- 
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: Error: child_copy: cygheap read copy failed.

[Corinna Vinschen via Cygwin]

On Jan 20 21:18, Takashi Yano via Cygwin wrote:
> On Fri, 20 Jan 2023 12:30:29 +0100
> Corinna Vinschen wrote:
> > Also, your ffplay executable isn't high-entropy-VA enabled, by any
> > chance?
> 
> I'm sorry, but the high-entropy-va is ebabled.
> 
> $ peflags -v /usr/bin/ff{mpeg,probe,play}
> /usr/bin/ffmpeg: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffprobe: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffplay: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])

Btw., how did this happen?  The native Cygwin compiler/linker combo
usually doesn't set the dynamicbase and high-entropy-VA flags by
default...


Corinna

-- 
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: Error: child_copy: cygheap read copy failed.

[Corinna Vinschen via Cygwin]

On Jan 20 21:18, Takashi Yano via Cygwin wrote:
> On Fri, 20 Jan 2023 12:30:29 +0100
> Corinna Vinschen wrote:
> > Also, your ffplay executable isn't high-entropy-VA enabled, by any
> > chance?
> 
> I'm sorry, but the high-entropy-va is ebabled.
> 
> $ peflags -v /usr/bin/ff{mpeg,probe,play}
> /usr/bin/ffmpeg: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffprobe: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffplay: 
> coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
>  pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> 
> peflags -e0 /usr/bin/ff{mpeg,probe,play} solves the issue.
> Thansk!

I'm glad to read that, actually!

> Shoud I remove dynamicbase flag as well?

I did a lot of local testing with ASLR locally, and it's fine for DLLs,
but not so much for the application executable itself.

You can keep dynamicbase for testing, but currently it's not advised
to do so, and you should definitely remove it for distro executables.


Thanks,
Corinna

-- 
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: Error: child_copy: cygheap read copy failed.

[Takashi Yano via Cygwin]

On Fri, 20 Jan 2023 12:30:29 +0100
Corinna Vinschen wrote:
> Also, your ffplay executable isn't high-entropy-VA enabled, by any
> chance?

I'm sorry, but the high-entropy-va is ebabled.

$ peflags -v /usr/bin/ff{mpeg,probe,play}
/usr/bin/ffmpeg: 
coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
 pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
/usr/bin/ffprobe: 
coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
 pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
/usr/bin/ffplay: 
coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg])
 pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])

peflags -e0 /usr/bin/ff{mpeg,probe,play} solves the issue.
Thansk!

Shoud I remove dynamicbase flag as well?

-- 
Takashi Yano 

-- 
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: Error: child_copy: cygheap read copy failed.

[Corinna Vinschen via Cygwin]

On Jan 20 12:56, Takashi Yano via Cygwin wrote:
> Hi Corinna,
> 
> I am now working on porting ffmpeg for cygwin, and noticed that
> the following error sometimes happens.
> 
> $ while true; do ffplay 2>&1 |grep cygheap; done
>   0 [main] ffplay (10172) child_copy: cygheap read copy failed, 
> 0x0..0x800028FB8, done 0, windows pid 10172, Win32 error 299
> 
> This seems to happen after the commit:
> 
> commit 2f9b8ff00cce0d0ceeb1091b6b9aecae914ddb89
> Author: Corinna Vinschen 
> Date:   Wed Oct 26 21:16:35 2022 +0200
> 
> Cygwin: decouple cygheap from Cygwin DLL
> [...]
> I looked into this problem a bit and found that VirtualAlloc()
> for MEM_RESERVE of cygheap area in cygheap_fixup_in_child()
> failed with ERROR_INVALID_ADDRESS. It seems that the address
> range is already occupied for some reason.

You should try to find out what that is.
> 
> I also noticed that the following patch seems to resolve the issue.
> 
> diff --git a/winsup/cygwin/local_includes/memory_layout.h 
> b/winsup/cygwin/local_includes/memory_layout.h
> index a3a0cae70..67164cfaf 100644
> --- a/winsup/cygwin/local_includes/memory_layout.h
> +++ b/winsup/cygwin/local_includes/memory_layout.h
> @@ -44,15 +44,15 @@ details. */
>  
>  /* That's where the cygheap is located. CYGHEAP_STORAGE_INITIAL defines the
> end of the initially committed heap area. */
> -#define CYGHEAP_STORAGE_LOW  0x8UL
> -#define CYGHEAP_STORAGE_INITIAL  0x80030UL
> -#define CYGHEAP_STORAGE_HIGH 0xaUL
> +#define CYGHEAP_STORAGE_LOW  0x700UL
> +#define CYGHEAP_STORAGE_INITIAL  0x730UL
> +#define CYGHEAP_STORAGE_HIGH 0x702UL
>  
>  /* This is where the user heap starts.  There's no defined end address.
> The user heap pontentially grows into the mmap arena.  However,
> the user heap grows upwards and the mmap arena grows downwards,
> so there's not much chance to meet unluckily. */
> -#define USERHEAP_START   0xaUL
> +#define USERHEAP_START   0x8UL

That doesn't make sense.  So we now have the user heap in place of the
cygheap, and that works?  So why should anything occuping the 0x8
- 0xa area if the cygheap needs it, suddenly not occupy it when
the user heap needs it?

Of course, this could be a result of the user heap not being reserved in
full size like the cygheap is.  The fact that it works with your patch
above points to an incidental success, with the user heap keeping most
of the area from 0x8 - 0xa free.  It would then fail
only later, if the application tries to raise the user heap beyond a
certain size.

Right now this looks like a very special case.  I don't know what I
should do from my side.  Please add debug output and/or use vmmap
from sysinternals to find out what's actually occupying the area
from 0x8 - 0xa and where exactly.

Also, your ffplay executable isn't high-entropy-VA enabled, by any
chance?


Corinna

-- 
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: Error when building autoconf2.1, broken package?

[Jon Turney]

On 10/08/2022 11:35, Carlo B. wrote:

Il giorno mer 3 ago 2022 alle ore 21:52 Jon Turney
 ha scritto:


On 22/07/2022 15:44, Carlo B. wrote:

it works, thank you very much.
I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
before calling cygconf and it also worked fine without manually
setting that environment variable.
I think that it would be worth to update the cygport script into
autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
other people.


Is there something wrong with our supplied autconf2.1 package?


Nowadays, it is not possible to make the autconf2.1 package from "src"
because the errors written in previous emails.
I don't know if the fault is caused by a regression into cygport or it
is needed to fix the "src" package of autconf2.1 for supporting a new
syntax or something like that. Unfortunately, the main problem is that
running the cygport script for autoconf 2.1 still hangs, so perhaps it
would be useful to fix it, in one way or another one.
Thank you very much for your time and your reply.


This isn't really responsive to my question: Are you building an 
autoconf2.1 package because the one we provide is deficient in some way, 
or because you want to?



This is a regression in cygport, which I'll see about fixing.


This should be fixed as of cygport 0.35.3


(Briefly: cygport tries to detect the version of autoconf which was used
to generate the ./configure script, so it knows what option arguments to
supply to it.  Recently this was extended to detect autoconf 2.7x, but
that seems to have broken detecting autoconf 2.1x)



--
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: Error line 30, E 117...

[Václav Haisman]

On 07. 09. 22 0:31, Kevin M. Wilson via Cygwin wrote:
> Question if Cygwin isn't 'installed' by Windows 10, then how is it installed, 
> and how can it be uninstalled??
> 
> 
> Good sense makes one slow to anger, and it is his glory tooverlook an offense.
> 
> Proverbs 19:11
> 
> 
See the FAQ link: https://cygwin.com/faq/faq.html#faq.setup.setup

-- 
VH

-- 
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: Error when building autoconf2.1, broken package?

[Carlo B.]

Hello,

Il giorno mer 3 ago 2022 alle ore 21:52 Jon Turney
 ha scritto:
>
> On 22/07/2022 15:44, Carlo B. wrote:
> > Hello,
> > it works, thank you very much.
> > I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
> > before calling cygconf and it also worked fine without manually
> > setting that environment variable.
> > I think that it would be worth to update the cygport script into
> > autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
> > other people.
>
> Is there something wrong with our supplied autconf2.1 package?
>
Nowadays, it is not possible to make the autconf2.1 package from "src"
because the errors written in previous emails.
I don't know if the fault is caused by a regression into cygport or it
is needed to fix the "src" package of autconf2.1 for supporting a new
syntax or something like that. Unfortunately, the main problem is that
running the cygport script for autoconf 2.1 still hangs, so perhaps it
would be useful to fix it, in one way or another one.
Thank you very much for your time and your reply.

Sincerely,

Carlo Bramini.


> >
> > Sincerely,
> >
> > Carlo Bramini.
> >
> > Il giorno gio 21 lug 2022 alle ore 15:07 Takashi Yano
> >  ha scritto:
> >>
> >> On Tue, 19 Jul 2022 12:42:47 +0200
> >> "Carlo B." wrote:
> >>> Hello,
> >>> I did these actions:
> >>> 1) Downloaded autoconf2.1-2.13-12-src.tar.bz2
> >>> 2) Unpack that file.
> >>> 3) I run this command:
> >>>
> >>> cygport autoconf2.1.cygport all
> >>>
> >>> and this is the output on screen:
> >>>
> >> Preparing autoconf2.1-2.13-12.x86_64
> >> Unpacking source autoconf-2.13.tar.gz
> >>> *** Info: applying patch autoconf2.1-texinfo.patch (-p2):
> >>> patching file autoconf.texi
> >> Preparing working source directory
> >>> *** Info: applying patch autoconf2.1-2.13-12.cygwin.patch (-p2):
> >>> patching file CYGWIN-PATCHES/autoconf2.1.README
> >> Compiling autoconf2.1-2.13-12.x86_64
> >>> *** ERROR: could not detect autoconf version; perhaps set 
> >>> AUTOCONF_VERSION?
>
> This is a regression in cygport, which I'll see about fixing.
>
> (Briefly: cygport tries to detect the version of autoconf which was used
> to generate the ./configure script, so it knows what option arguments to
> supply to it.  Recently this was extended to detect autoconf 2.7x, but
> that seems to have broken detecting autoconf 2.1x)
>
> >>>
> >>> Have you an idea of the cause of the problem?
> >>> I tried to download and rebuild also autoconf2.5 and autoconf2.7 and
> >>> they worked fine, only 2.1 fails.
> >>> Thank you very much for your time.
> >>
> >> I could build autoconf2.1 successfully by the following steps.
> >>
> >>
> >> 1) Modify autoconf2.1.cygport as follows.
> >>
> >> diff --git a/autoconf2.1.cygport.orig b/autoconf2.1.cygport
> >> index c8b075f..6876c3c 100755
> >> --- a/autoconf2.1.cygport.orig
> >> +++ b/autoconf2.1.cygport
> >> @@ -28,7 +28,7 @@ src_compile() {
> >>  cd ${B}
> >>  cygconf --program-suffix=-2.13
> >>  cygmake -j1
> >> -   (makeinfo --no-split -I ${S} -o autoconf2.13.info autoconf.texi)
> >> +   (makeinfo --no-split -o autoconf2.13.info ${S}/autoconf.texi)
>
> I'm not sure why this change is needed.
>
> >>   }
> >>
> >>   DIFF_EXCLUDES="autoconf.info standards.info stamp-vti version.texi"
> >>
> >> 2) Run 'export AUTOCONF_VERSION=2.13'
> >> 3) Run 'cygport autoconf2.1.cygport all'

-- 
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: Error when building autoconf2.1, broken package?

[Jon Turney]

On 22/07/2022 15:44, Carlo B. wrote:

Hello,
it works, thank you very much.
I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
before calling cygconf and it also worked fine without manually
setting that environment variable.
I think that it would be worth to update the cygport script into
autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
other people.


Is there something wrong with our supplied autconf2.1 package?



Sincerely,

Carlo Bramini.

Il giorno gio 21 lug 2022 alle ore 15:07 Takashi Yano
 ha scritto:


On Tue, 19 Jul 2022 12:42:47 +0200
"Carlo B." wrote:

Hello,
I did these actions:
1) Downloaded autoconf2.1-2.13-12-src.tar.bz2
2) Unpack that file.
3) I run this command:

cygport autoconf2.1.cygport all

and this is the output on screen:


Preparing autoconf2.1-2.13-12.x86_64
Unpacking source autoconf-2.13.tar.gz

*** Info: applying patch autoconf2.1-texinfo.patch (-p2):
patching file autoconf.texi

Preparing working source directory

*** Info: applying patch autoconf2.1-2.13-12.cygwin.patch (-p2):
patching file CYGWIN-PATCHES/autoconf2.1.README

Compiling autoconf2.1-2.13-12.x86_64

*** ERROR: could not detect autoconf version; perhaps set AUTOCONF_VERSION?


This is a regression in cygport, which I'll see about fixing.

(Briefly: cygport tries to detect the version of autoconf which was used 
to generate the ./configure script, so it knows what option arguments to 
supply to it.  Recently this was extended to detect autoconf 2.7x, but 
that seems to have broken detecting autoconf 2.1x)




Have you an idea of the cause of the problem?
I tried to download and rebuild also autoconf2.5 and autoconf2.7 and
they worked fine, only 2.1 fails.
Thank you very much for your time.


I could build autoconf2.1 successfully by the following steps.


1) Modify autoconf2.1.cygport as follows.

diff --git a/autoconf2.1.cygport.orig b/autoconf2.1.cygport
index c8b075f..6876c3c 100755
--- a/autoconf2.1.cygport.orig
+++ b/autoconf2.1.cygport
@@ -28,7 +28,7 @@ src_compile() {
 cd ${B}
 cygconf --program-suffix=-2.13
 cygmake -j1
-   (makeinfo --no-split -I ${S} -o autoconf2.13.info autoconf.texi)
+   (makeinfo --no-split -o autoconf2.13.info ${S}/autoconf.texi)


I'm not sure why this change is needed.


  }

  DIFF_EXCLUDES="autoconf.info standards.info stamp-vti version.texi"

2) Run 'export AUTOCONF_VERSION=2.13'
3) Run 'cygport autoconf2.1.cygport all'


--
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: Error when building autoconf2.1, broken package?

[Carlo B.]

Hello,
it works, thank you very much.
I also added AUTOCONF_VERSION=2.13 directly into the cygport script,
before calling cygconf and it also worked fine without manually
setting that environment variable.
I think that it would be worth to update the cygport script into
autoconf2.1-2.13-12-src.tar.bz2 to make it working again also for
other people.

Sincerely,

Carlo Bramini.

Il giorno gio 21 lug 2022 alle ore 15:07 Takashi Yano
 ha scritto:
>
> On Tue, 19 Jul 2022 12:42:47 +0200
> "Carlo B." wrote:
> > Hello,
> > I did these actions:
> > 1) Downloaded autoconf2.1-2.13-12-src.tar.bz2
> > 2) Unpack that file.
> > 3) I run this command:
> >
> > cygport autoconf2.1.cygport all
> >
> > and this is the output on screen:
> >
> > >>> Preparing autoconf2.1-2.13-12.x86_64
> > >>> Unpacking source autoconf-2.13.tar.gz
> > *** Info: applying patch autoconf2.1-texinfo.patch (-p2):
> > patching file autoconf.texi
> > >>> Preparing working source directory
> > *** Info: applying patch autoconf2.1-2.13-12.cygwin.patch (-p2):
> > patching file CYGWIN-PATCHES/autoconf2.1.README
> > >>> Compiling autoconf2.1-2.13-12.x86_64
> > *** ERROR: could not detect autoconf version; perhaps set AUTOCONF_VERSION?
> >
> > Have you an idea of the cause of the problem?
> > I tried to download and rebuild also autoconf2.5 and autoconf2.7 and
> > they worked fine, only 2.1 fails.
> > Thank you very much for your time.
>
> I could build autoconf2.1 successfully by the following steps.
>
>
> 1) Modify autoconf2.1.cygport as follows.
>
> diff --git a/autoconf2.1.cygport.orig b/autoconf2.1.cygport
> index c8b075f..6876c3c 100755
> --- a/autoconf2.1.cygport.orig
> +++ b/autoconf2.1.cygport
> @@ -28,7 +28,7 @@ src_compile() {
> cd ${B}
> cygconf --program-suffix=-2.13
> cygmake -j1
> -   (makeinfo --no-split -I ${S} -o autoconf2.13.info autoconf.texi)
> +   (makeinfo --no-split -o autoconf2.13.info ${S}/autoconf.texi)
>  }
>
>  DIFF_EXCLUDES="autoconf.info standards.info stamp-vti version.texi"
>
> 2) Run 'export AUTOCONF_VERSION=2.13'
> 3) Run 'cygport autoconf2.1.cygport all'
>
> --
> Takashi Yano 

-- 
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: Error when building autoconf2.1, broken package?

[Takashi Yano]

On Tue, 19 Jul 2022 12:42:47 +0200
"Carlo B." wrote:
> Hello,
> I did these actions:
> 1) Downloaded autoconf2.1-2.13-12-src.tar.bz2
> 2) Unpack that file.
> 3) I run this command:
> 
> cygport autoconf2.1.cygport all
> 
> and this is the output on screen:
> 
> >>> Preparing autoconf2.1-2.13-12.x86_64
> >>> Unpacking source autoconf-2.13.tar.gz
> *** Info: applying patch autoconf2.1-texinfo.patch (-p2):
> patching file autoconf.texi
> >>> Preparing working source directory
> *** Info: applying patch autoconf2.1-2.13-12.cygwin.patch (-p2):
> patching file CYGWIN-PATCHES/autoconf2.1.README
> >>> Compiling autoconf2.1-2.13-12.x86_64
> *** ERROR: could not detect autoconf version; perhaps set AUTOCONF_VERSION?
> 
> Have you an idea of the cause of the problem?
> I tried to download and rebuild also autoconf2.5 and autoconf2.7 and
> they worked fine, only 2.1 fails.
> Thank you very much for your time.

I could build autoconf2.1 successfully by the following steps.


1) Modify autoconf2.1.cygport as follows.

diff --git a/autoconf2.1.cygport.orig b/autoconf2.1.cygport
index c8b075f..6876c3c 100755
--- a/autoconf2.1.cygport.orig
+++ b/autoconf2.1.cygport
@@ -28,7 +28,7 @@ src_compile() {
cd ${B}
cygconf --program-suffix=-2.13
cygmake -j1
-   (makeinfo --no-split -I ${S} -o autoconf2.13.info autoconf.texi)
+   (makeinfo --no-split -o autoconf2.13.info ${S}/autoconf.texi)
 }
 
 DIFF_EXCLUDES="autoconf.info standards.info stamp-vti version.texi"

2) Run 'export AUTOCONF_VERSION=2.13'
3) Run 'cygport autoconf2.1.cygport all'

-- 
Takashi Yano 

-- 
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: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10

[John Balkunas]

Thank you!  This looks like it may help.

 8< 

From: Cygwin  on behalf of 
Brian Inglis 
Sent: Sunday, April 24, 2022 1:08 PM
To: cygwin@cygwin.com 
Subject: Re: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10 
 
On 2022-04-24 08:02, John Balkunas wrote:
> Hello,
> 
> I installed Cywin64 Terminal so that I can compile chrony-4.2 for use with 
> Windows 10 Pro 64-bit. I used the Cygwin Setup program/installer named 
> setup-x86_64.exe for 64 bit Windows.  The install appeared to go well.  After 
> the install, from within the Cywin64 Terminal, I see the following 3 results:
> 
> Command: "cygcheck -V"
> Result:
> cygcheck (cygwin) 3.3.4
> System Checker for Cygwin
> Copyright (C) 1998 - 2022 Cygwin Authors
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Command: "gcc --version"
> Result:
> gcc (GCC) 11.2.0
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Command: "g++ --version"
> Result:
> g++ (GCC) 11.2.0
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Thus, this leads me to think everything is ready to go on my Win10 machine 
> for compiling.  However, when I switch to the directory I unpacked the 
> chrony-4.2 to and run the "./configure" command (I used no switches) from 
> within the Cygwin64 Terminal I see the following:
> 
> Command: "./configure"
> Result:
> error: CYGWIN_NT-10.0-x86_64 is not supported (yet?)
> 
> I have tried searching for this error (was really hard trying to go through 
> the Cygwin web archives) and haven't seen it discussed.  I am pretty computer 
> literate, but at this juncture I'm not sure how to proceed.  I've compiled a 
> few programs before (from within Linux), have done some programming in the 
> past, but am in no way "comfortable" or that knowledgeable about it and am 
> officially stuck.
> 
> ANY responses would likely be appreciated.  Thank you in advance for any 
> help/suggestions/clues!

BTDT, IIRC too many Linux dependencies.
Still running NTP from Meinberg:

https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable
https://www.meinbergglobal.com/download/ntp/windows/ntp-4.2.8p15-v2-win32-setup.exe
https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm
https://www.meinbergglobal.com/download/ntp/windows/time-server-monitor/ntp-time-server-monitor-104.exe

You can download the sources and build the daemon and utilities with 
older VS releases, but Meinberg provides a service installer and monitor 
utility.

With serial driver and PPS DLL, service and other setup tweaking, you 
can run a serial GPS with PPS at Realtime priority and get microsecond 
stability.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

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

-- 
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: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10

[Brian Inglis]

On 2022-04-24 08:02, John Balkunas wrote:

Hello,

I installed Cywin64 Terminal so that I can compile chrony-4.2 for use with 
Windows 10 Pro 64-bit. I used the Cygwin Setup program/installer named 
setup-x86_64.exe for 64 bit Windows.  The install appeared to go well.  After 
the install, from within the Cywin64 Terminal, I see the following 3 results:

Command: "cygcheck -V"
Result:
cygcheck (cygwin) 3.3.4
System Checker for Cygwin
Copyright (C) 1998 - 2022 Cygwin Authors
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Command: "gcc --version"
Result:
gcc (GCC) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Command: "g++ --version"
Result:
g++ (GCC) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thus, this leads me to think everything is ready to go on my Win10 machine for compiling. 
 However, when I switch to the directory I unpacked the chrony-4.2 to and run the 
"./configure" command (I used no switches) from within the Cygwin64 Terminal I 
see the following:

Command: "./configure"
Result:
error: CYGWIN_NT-10.0-x86_64 is not supported (yet?)

I have tried searching for this error (was really hard trying to go through the Cygwin 
web archives) and haven't seen it discussed.  I am pretty computer literate, but at this 
juncture I'm not sure how to proceed.  I've compiled a few programs before (from within 
Linux), have done some programming in the past, but am in no way "comfortable" 
or that knowledgeable about it and am officially stuck.

ANY responses would likely be appreciated.  Thank you in advance for any 
help/suggestions/clues!


BTDT, IIRC too many Linux dependencies.
Still running NTP from Meinberg:

https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable
https://www.meinbergglobal.com/download/ntp/windows/ntp-4.2.8p15-v2-win32-setup.exe
https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm
https://www.meinbergglobal.com/download/ntp/windows/time-server-monitor/ntp-time-server-monitor-104.exe

You can download the sources and build the daemon and utilities with 
older VS releases, but Meinberg provides a service installer and monitor 
utility.


With serial driver and PPS DLL, service and other setup tweaking, you 
can run a serial GPS with PPS at Realtime priority and get microsecond 
stability.


--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
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: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10

[René Berber]

On 4/24/2022 10:37 AM, René Berber wrote:


On 4/24/2022 10:3 AM, John Balkunas wrote:




Thank you!  It makes sense.  Upon further reading it looks like
chrony's docs say it does not run on/support Windows.


That is not the same as not supporting Cygwin.

[snip]
Taken from chrony's FAQ:

"7.1. Does chrony support Windows?

No. The chronyc program (the command-line client used for configuring 
chronyd while it is running) has been successfully built and run under 
Cygwin in the past. chronyd is not portable, because part of it is very 
system-dependent. It needs adapting to work with Windows' equivalent of 
the adjtimex() call, and it needs to be made to work as a service."


Running as a service is not a problem in Cygwin, there's a helper 
program for that.


I'm not sure about the support for adjtimex()... Its not in any header 
so I guess its not supported.  There is an adjtime() in sys/time.h, but 
that is not the same.


--
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: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10

[René Berber]

On 4/24/2022 10:3 AM, John Balkunas wrote:




Thank you!  It makes sense.  Upon further reading it looks like
chrony's docs say it does not run on/support Windows.


That is not the same as not supporting Cygwin.


Looks like I should be trying to get NTP running instead of Chrony
for time clock syncing/updating on this Win10 machine.  Bet that will
be fun.


I wouldn't give up, chrony probably works out of the box, it just needs 
to accept that the environment is Linux-like.



Thanks again.


You are welcome.
--
René Berber

--
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: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10

[René Berber]

On 4/24/2022 9:02 AM, John Balkunas wrote:


I installed Cywin64 Terminal so that I can compile chrony-4.2 for use with 
Windows 10 Pro 64-bit. I used the Cygwin Setup program/installer named 
setup-x86_64.exe for 64 bit Windows.  The install appeared to go well.  After 
the install, from within the Cywin64 Terminal, I see the following 3 results:

[snip]

Command: "./configure"
Result:
error: CYGWIN_NT-10.0-x86_64 is not supported (yet?)


That message is from chrony, there's no apparent problem with Cygwin. 
The message is just telling you that the OS CYGWIN* is not one known to 
work, or the project being already ported if that is needed.


Perhaps its time to look into configure's options, there may be one to 
(force) build for Linux and, depending on how portable that project is, 
it usually works.


Another detail which is often overlooked, you need to install the 
pre-requisites (listed by the specific project) and its development 
libraries (as in -devel in setup).


Hope this helps.
--
R.Berber

--
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: Error encountered in Octave software - Please help!!

[Takashi Yano via Cygwin]

On Thu, 16 Sep 2021 15:44:06 -0400
Bryan VanSchouwen wrote:
> I just tried performing an analysis in the Octave software (GNU Octave,
> version 5.2.0), using the attached "dm" input file, and the following
> commands:
> load dm
> cdmt = cor(dm.')
> 
> However, I encountered the following error message:
> error: 'cor' undefined near line 1 column 8
> 
> What is going on here??

cor() requires package nan. So please install octave-nan
package and run 'pkg load nan' from octave command line.

'pkg load nan' shows many warning messages. However, it
seems to work.

-- 
Takashi Yano 

-- 
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: Error during transfer

[Andrey Repin]

Greetings, bsampl--- via Cygwin!

> Hello, during a transfer today I got this error message, The last part is
> always there when starting rsync, should be a problem related to windows,
> but the 5 lines before are new. I would like to ask you to explain the
> possible reason for this error. I just copied files from one external disk
> to another on localhost. Many thanks.

> 

> rsync: writefd_unbuffered failed to write 4092 bytes to socket [sender]:
> Broken pipe (32)

> rsync: read error: Software caused connection abort (113)

> rsync error: error in rsync protocol data stream (code 12) at
> /home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/io.c(764) [sender=3.0.9]

> Error in rsync protocol data stream

> Rsync.exe returned an error. Will try again. This is retry number 1 of 5


I get similar errors regularly

>> sending incremental file list
>> attempt to hack rsync failed.
>> rsync error: protocol incompatibility (code 2) at receiver.c(582) 
>> [receiver=3.1.0]

Even if nothing is needed to be sent, like in this example.

>> $ rsync --version
>> rsync  version 3.2.4dev  protocol version 31
>> Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
>> Web site: https://rsync.samba.org/
>> Capabilities:
>> 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
>> socketpairs, hardlinks, no hardlink-specials, symlinks, IPv6, atimes,
>> batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv,
>> symtimes, prealloc, stop-at, no crtimes
>> Optimizations:
>> no SIMD, asm, openssl-crypto
>> Checksum list:
>> xxh128 xxh3 xxh64 (xxhash) md5 md4 none
>> Compress list:
>> zstd lz4 zlibx zlib none
>>
>> rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
>> are welcome to redistribute it under certain conditions.  See the GNU
>> General Public Licence for details.


-- 
With best regards,
Andrey Repin
Tuesday, September 7, 2021 9:37:18

Sorry for my terrible english...


-- 
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: Error during transfer

[cygwinautoreply--- via Cygwin]

>Hello, during a transfer today I got this error message, The last part is
>always there when starting rsync, should be a problem related to windows,
>but the 5 lines before are new. I would like to ask you to explain the
>possible reason for this error. I just copied files from one external disk
>to another on localhost. Many thanks.

>
>--



>rsync: writefd_unbuffered failed to write 4092 bytes to socket [sender]:
>Broken pipe (32)

>rsync: read error: Software caused connection abort (113)

>rsync error: error in rsync protocol data stream (code 12) at
>/home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/io.c(764) [sender=3.0.9]

>Error in rsync protocol data stream

>Rsync.exe returned an error. Will try again. This is retry number 1 of 5



>Executing: rsync.exe  -v -rlt -z --chmod=a=rw,Da+x --delete
>--exclude='*.lrc' "/cygdrive/D/Daten/Multimedia/Musikbibliothek/Bibliothek/"
>"localhost::newMusic/Bibliothek/"

>  1 [main] rsync 10360 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem to

>the public mailing list   cygwin@cygwin.com

>
>--





>Regards

>Bernhard Sampl





https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

-- 
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: Error Report

[Marco Atzeri via Cygwin]

On 27.05.2021 01:50, Jaime Arseneault via Cygwin wrote:

Hi,

I got an error and it says in the error to report it to this email address.
This happened while I was using WiiBaFu to patch Rhythm Heaven Fever with
custom textures.

Thanks



Hi Jaime,

the warning is explained at
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
Regards
Marco

--
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: Error Report

[cygwinautoreply--- via Cygwin]

>1 [main] rsync 3280 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. 
>Please report this problem to
>the public mailing list cygwin@cygwin.com
>sending incremental file list
>M. Wortmann Elektrotechnik GmbH & Co. KG
>Horst 13
>48301 Nottuln
>02502/2243821
>i...@wortmann-elektro.de
>www.wortmann-elektro.de

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
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: Error running gitg

[Keith Thompson via Cygwin]

I've seen some inconsistent behavior while trying to install older
versions of gitg.

On one of my two Windows 10 laptops, I tried installing version 3.22.0
(which worked) and then 3.24.0 (which also worked) before updating
back to the current 3.26.0 (which also worked).  I had seen gitg 3.26.0 fail
to work when I first installed it.

On my other laptop, I haven't been able to get any version to work
after trying to reproduce what I did on the first laptop.

I don't have any more information, other than that the problem seems to be
more complicated than I thought it was.
--
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: Error with wxWidgets 3.0.5 for CYGWIN.

[Hamish McIntyre-Bhatty via Cygwin]

On 26/02/2021 12:05, Hamish McIntyre-Bhatty via Cygwin wrote:

On 26/02/2021 11:54, Carlo B. via Cygwin wrote:

Hello,
after updating some packages, I tried to rebuild my Kicad sources and
I discovered that I could not do it anymore. During the process, it
hangs with this error:

error: 'wxRE_ADVANCED' was not declared in this scope.

It seems that the new package of wxWidgets 3.0.5 had not been compiled
with built-in regex support, including wxRE_ADVANCED option. I
downgraded to wxWidgets 3.0.4 and I was able to build everything
again.
I hope that you could fix this issue.

Sincerely.

Carlo Bramini.
--
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


Hi Carlo,

Thanks for making me aware of this issue.

I am exceptionally busy at the moment so it may take me some time to 
debug this. IIRC the built-in regex support should have remained 
enabled - I'm not sure what's happened here.


Hamish McIntyre-Bhatty


I have updated the packages, and they should make it into the 
repositories soon - hopefully this now works for you. The new version is 
3.0.5.1-2.


Hamish McIntyre-Bhatty



OpenPGP_0x18F1759B3457223F.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
--
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: Error with wxWidgets 3.0.5 for CYGWIN.

[Hamish McIntyre-Bhatty via Cygwin]

On 26/02/2021 11:54, Carlo B. via Cygwin wrote:

Hello,
after updating some packages, I tried to rebuild my Kicad sources and
I discovered that I could not do it anymore. During the process, it
hangs with this error:

error: 'wxRE_ADVANCED' was not declared in this scope.

It seems that the new package of wxWidgets 3.0.5 had not been compiled
with built-in regex support, including wxRE_ADVANCED option. I
downgraded to wxWidgets 3.0.4 and I was able to build everything
again.
I hope that you could fix this issue.

Sincerely.

Carlo Bramini.
--
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


Hi Carlo,

Thanks for making me aware of this issue.

I am exceptionally busy at the moment so it may take me some time to 
debug this. IIRC the built-in regex support should have remained enabled 
- I'm not sure what's happened here.


Hamish McIntyre-Bhatty



OpenPGP_0x18F1759B3457223F.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
--
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: error running linker

[Tres Finocchiaro via Cygwin]

If this command is getting its parameter from a previous command, make
sure to sanitize the stderr that comes from Cygwin.  Normally, this
isn't a problem, but ant specifically included stderr and stdout
together when parsing a command.

https://github.com/java-native-access/jna/commit/2714a017c9fada761e3d175d1e03f1d3bccaa14f

This above example is using ant's "apply", but any ant executed output
can suffer from this problem where stderr is mixed with stdout.  It's
not a cygwin bug, but rather a nuance with ant that surfaces with
Cygwin.

- tres.finocchi...@gmail.com

On Fri, Jan 8, 2021 at 5:50 PM cygwinautoreply--- via Cygwin
 wrote:
>
> >Hi,
>
> >While running an ant build cc task (cpptasks: Compile tasks for Apache
> >Ant - cc (sourceforge.net)
> >), when
> >it reached the Link step I received the following output:
>
> >Starting Link
>
> > 1 [main] 5672 find_fast_cwd: WARNING: Couldn’t compute
> >FAST_CWD pointer.  Please report this problem to the public mailing list
> >cygwin@cygwin.com 
>
> > link: extra operand ‘/DLL’
>
> >I don’t know if the extra operand is the problem, I don’t supply it, it
> >is likely generated by the “outtype=’shared’” parameter of the cc task,
> >so I don’t have an easy means to experiment with changing that since I
> >need a shared library to be generated.
>
> >If you need any other info let me know.
>
> >Regards,
>
> >Rick Morgan
>
> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
> --
> 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
--
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: error running linker

[cygwinautoreply--- via Cygwin]

>Hi,

>While running an ant build cc task (cpptasks: Compile tasks for Apache 
>Ant - cc (sourceforge.net) 
>), when 
>it reached the Link step I received the following output:

>Starting Link

>                 1 [main] 5672 find_fast_cwd: WARNING: 
> Couldn’t compute 
>FAST_CWD pointer.  Please report this problem to the public mailing list 
>cygwin@cygwin.com 

>                 link: extra operand ‘/DLL’

>I don’t know if the extra operand is the problem, I don’t supply it, it 
>is likely generated by the “outtype=’shared’” parameter of the cc 
>task, 
>so I don’t have an easy means to experiment with changing that since I 
>need a shared library to be generated.

>If you need any other info let me know.

>Regards,

>Rick Morgan

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
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: Error compiling gengetopt

[Rafel Amer Ramon]

El 26/11/20 a les 18:47, Ken Brown ha escrit:

On 11/26/2020 12:25 PM, Rafel Amer Ramon wrote:

El 26/11/20 a les 17:31, Ken Brown ha escrit:

[Please don't top-post on this list.]

On 11/26/2020 10:51 AM, Rafel Amer Ramon wrote:


Hello,

I get the same error with the bash terminal and directory 
/usr/local/src


libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/usr/lacal/src/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//usr/local/src/gengetopt-2.23/src/../gl/.libs/libgnu.a 









OK, my guess was wrong.

I downloaded and built the package on my system without a problem, 
so something specific to your setup is causing this. Do you see 
anything suspicious earlier in the build?  You might try capturing a 
log of the build and sending it as an attachment to see if anyone 
here spots anything.  Also, please follow the problem-reporting 
guide at https://cygwin.com/problems.html, including the part about 
sending cygcheck output (as an attachment).


Ken


Hello,

I can't see anything strange. I attach the file cygcheck.out 
(cygcheck -s -v -r  > cygcheck.out),

and the file make.out (make > make.out 2>&1)


I think your PATH might be the problem.  I see several warnings like 
this in cygcheck.out:


  Warning: C:\Windows\system32\bash.exe hides C:\cygwin64\bin\bash.exe

And I also saw this in the configure.log that you sent me privately:

  checking for tar... /cygdrive/c/Windows/system32/tar

You need to be sure you're using Cygwin tools when building on 
Cygwin.  Note that if you had been working in a Cygwin bash shell, 
/etc/profile would have adjusted your profile appropriately.


Ken


Hello,

yes, the problem was the PATH. I have changed the order of the 
directories in the PATH and now I can compile

successfully the gengetopt program.

Thank you very much.

Best regards,

Rafel Amer

--
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: Error compiling gengetopt

[Ken Brown via Cygwin]

On 11/26/2020 12:25 PM, Rafel Amer Ramon wrote:

El 26/11/20 a les 17:31, Ken Brown ha escrit:

[Please don't top-post on this list.]

On 11/26/2020 10:51 AM, Rafel Amer Ramon wrote:


Hello,

I get the same error with the bash terminal and directory /usr/local/src

libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/usr/lacal/src/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//usr/local/src/gengetopt-2.23/src/../gl/.libs/libgnu.a 








OK, my guess was wrong.

I downloaded and built the package on my system without a problem, so 
something specific to your setup is causing this.  Do you see anything 
suspicious earlier in the build?  You might try capturing a log of the build 
and sending it as an attachment to see if anyone here spots anything.  Also, 
please follow the problem-reporting guide at https://cygwin.com/problems.html, 
including the part about sending cygcheck output (as an attachment).


Ken


Hello,

I can't see anything strange. I attach the file cygcheck.out (cygcheck -s -v -r 
 > cygcheck.out),

and the file make.out (make > make.out 2>&1)


I think your PATH might be the problem.  I see several warnings like this in 
cygcheck.out:


  Warning: C:\Windows\system32\bash.exe hides C:\cygwin64\bin\bash.exe

And I also saw this in the configure.log that you sent me privately:

  checking for tar... /cygdrive/c/Windows/system32/tar

You need to be sure you're using Cygwin tools when building on Cygwin.  Note 
that if you had been working in a Cygwin bash shell, /etc/profile would have 
adjusted your profile appropriately.


Ken
--
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: Error compiling gengetopt

[Rafel Amer Ramon]

El 26/11/20 a les 17:31, Ken Brown ha escrit:

[Please don't top-post on this list.]

On 11/26/2020 10:51 AM, Rafel Amer Ramon wrote:


Hello,

I get the same error with the bash terminal and directory /usr/local/src

libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/usr/lacal/src/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//usr/local/src/gengetopt-2.23/src/../gl/.libs/libgnu.a 







OK, my guess was wrong.

I downloaded and built the package on my system without a problem, so 
something specific to your setup is causing this.  Do you see anything 
suspicious earlier in the build?  You might try capturing a log of the 
build and sending it as an attachment to see if anyone here spots 
anything.  Also, please follow the problem-reporting guide at 
https://cygwin.com/problems.html, including the part about sending 
cygcheck output (as an attachment).


Ken


Hello,

I can't see anything strange. I attach the file cygcheck.out (cygcheck 
-s -v -r > cygcheck.out),

and the file make.out (make > make.out 2>&1)


Regards,

Rafel Amer







Cygwin Configuration Diagnostics
Current System Time: Thu Nov 26 17:52:20 2020

Windows 10 Ver 10.0 Build 17763 

Path:   C:\Program Files\Python39\Scripts
C:\Program Files\Python39
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Windows\System32\OpenSSH
C:\texlive\2020\bin\win32
C:\cygwin64\bin
C:\Program Files\Microsoft VS Code\bin
C:\Users\Rafel Amer\AppData\Local\Microsoft\WindowsApps
C:\Users\Rafel Amer\AppData\Local\atom\bin

Output from C:\cygwin64\bin\id.exe
UID: 197609(Rafel Amer)GID: 197121(Ninguno)
197121(Ninguno)545(Usuarios)
4(INTERACTIVE) 66049(INICIO DE SESIÓN EN LA CONSOLA)
11(Usuarios autentificados)15(Esta compañía)
113(Cuenta local)  4095(CurrentSession)
66048(LOCAL)   262154(Autenticación NTLM)
401408(Nivel obligatorio medio)

SysDir: C:\Windows\system32
WinDir: C:\Windows

PWD = '/usr/local/src/gengetopt-2.23'
HOME = '/home/Rafel Amer'
CYGWIN = 'nodosfilewarning'

USERDOMAIN = 'DESKTOP-8CFRJAQ'
OS = 'Windows_NT'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
PROCESSOR_LEVEL = '23'
PSModulePath = 'C:\Program 
Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules'
CommonProgramW6432 = 'C:\Program Files\Common Files'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/usr/local/src'
USERNAME = 'Rafel Amer'
LOGONSERVER = '\\DESKTOP-8CFRJAQ'
PROCESSOR_ARCHITECTURE = 'AMD64'
LOCALAPPDATA = 'C:\Users\Rafel Amer\AppData\Local'
COMPUTERNAME = 'DESKTOP-8CFRJAQ'
!:: = '::\'
SYSTEMDRIVE = 'C:'
USERPROFILE = 'C:\Users\Rafel Amer'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW'
SYSTEMROOT = 'C:\Windows'
USERDOMAIN_ROAMINGPROFILE = 'DESKTOP-8CFRJAQ'
PROCESSOR_IDENTIFIER = 'AMD64 Family 23 Model 113 Stepping 0, AuthenticAMD'
TMP = '/cygdrive/c/Users/RAFELA~1/AppData/Local/Temp'
PROCESSOR_REVISION = '7100'
NUMBER_OF_PROCESSORS = '1'
ProgramW6432 = 'C:\Program Files'
COMSPEC = 'C:\Windows\system32\cmd.exe'
APPDATA = 'C:\Users\Rafel Amer\AppData\Roaming'
TERM = 'xterm-256color'
WINDIR = 'C:\Windows'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PROGRAMFILES = 'C:\Program Files'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/cygdrive/c/Users/RAFELA~1/AppData/Local/Temp'
DriverData = 'C:\Windows\System32\Drivers\DriverData'
SESSIONNAME = 'Console'
ProgramFiles(x86) = 'C:\Program Files (x86)'
HOMEDRIVE = 'C:'
HOMEPATH = '\Users\Rafel Amer'
EXECIGNORE = '*.dll'
_ = '/usr/bin/cygcheck'

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Cygwin
  (default) = 0xff00

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64
  User:   Key: e022582115c10879 Path: C:\cygwin64

c:  hd  NTFS 50648Mb  56% CP CS UN PA FCQU  
d:  cd N/AN/A   

C:\cygwin64  /  system  binary,auto
C:\cygwin64\bin  /usr/bin   system  binary,auto
C:\cygwin64\lib  /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  userbinary,posix=0,auto

Found: C:\cygwin64\bin\awk
 -> C:\cygwin64\bin\gawk.exe
Found: C:\Windows\system32\bash.exe
Found: C:\cygwin64\bin\bash.exe
Warning: C:\Windows\system32\bash.exe hides C:\cygwin64\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\Windows\system32\certutil.exe
Not Found: clinfo
Found: C:\Windows\syst

Re: Error compiling gengetopt

[Ken Brown via Cygwin]

[Please don't top-post on this list.]

On 11/26/2020 10:51 AM, Rafel Amer Ramon wrote:


Hello,

I get the same error with the bash terminal and directory /usr/local/src

libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/usr/lacal/src/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//usr/local/src/gengetopt-2.23/src/../gl/.libs/libgnu.a 


OK, my guess was wrong.

I downloaded and built the package on my system without a problem, so something 
specific to your setup is causing this.  Do you see anything suspicious earlier 
in the build?  You might try capturing a log of the build and sending it as an 
attachment to see if anyone here spots anything.  Also, please follow the 
problem-reporting guide at https://cygwin.com/problems.html, including the part 
about sending cygcheck output (as an attachment).


Ken
--
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: Error compiling gengetopt

[Rafel Amer Ramon]

Hello,

I get the same error with the bash terminal and directory /usr/local/src

libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/usr/lacal/src/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//usr/local/src/gengetopt-2.23/src/../gl/.libs/libgnu.a


Regards,

Rafel Amer

El 26/11/20 a les 14:04, Ken Brown ha escrit:

On 11/26/2020 5:30 AM, Rafel Amer Ramon wrote:

Hello,
when I try to compile gengetopt with cygwin on Windows 10, I get the 
following error


libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/cygdrive/c/Users/Rafel 
Amer/Downloads/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//cygdrive/c/Users/Rafel 
Amer/Downloads/gengetopt-2.23/src/../gl/.libs/libgnu.a



Does someone know how I can solve this?


Try working in a directory with no spaces in its name.

Ken


--
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: Error compiling gengetopt

[Ken Brown via Cygwin]

On 11/26/2020 5:30 AM, Rafel Amer Ramon wrote:

Hello,
when I try to compile gengetopt with cygwin on Windows 10, I get the following 
error


libtool: link: (cd .libs/libgengetopt.lax/libgnu.a && ar x 
"/cygdrive/c/Users/Rafel Amer/Downloads/gengetopt-2.23/src/../gl/.libs/libgnu.a")


libtool: error: object name conflicts in archive: 
.libs/libgengetopt.lax/libgnu.a//cygdrive/c/Users/Rafel 
Amer/Downloads/gengetopt-2.23/src/../gl/.libs/libgnu.a



Does someone know how I can solve this?


Try working in a directory with no spaces in its name.

Ken
--
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: Error: "-gThe system cannot find the file specified." When bash script containing "cut" is run from cmd

[Matt D. via Cygwin]

Please ignore this. There was an error in my test case.
--
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: Error Message

[cygwinautoreply--- via Cygwin]

>Receiving the following error message, [main} bash 8264 find_fast_cwd:warning: 
>couldn't compute fast_cmd pointer
>Please report the problem to the public mailing list 
>cygwin@cygwin.com not found Invalid or corrupt 
>soceds install

>Thanks

>Bob N Coward
>Senior Information Systems Technologist
>Raytheon Technology Program Execution
>RI&S Digital Technology Program Execution

>+(601).469.8430   (office)
>bncow...@raytheon.com

>19859 Hwy 80 East
>Forest, Ms, 39074



https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
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: Error using cntlm

[cygwinautoreply--- via Cygwin]

>Hi,
>When I fire this command:
>“cntlm -c cntlm.ini -M http://www.google.de”
>I’m getting this error:
>“0 [main] cntlm 22772 find_fast_cwd: WARNING: Couldn't compute FAST_CWD 
>pointer.”


>Another problem is that I cann’t generate encrypted password, but maybe it 
>is problem z my organization network settings.
>“Password:
>Config profile  1/4...
>Connection to proxy failed, bailing out”

>MF
>This e-mail and the documents attached are covered business secret the Atos 
>group entities and contain confidential information intended solely for the 
>addressee. If you receive this e-mail in error, please notify the sender 
>immediately and destroy it. Atos Poland Global Services spółka z ograniczoną
> odpowiedzialnością with its registered office in Bydgoszcz (previously Atos 
>Global Delivery Center Polska spółka z ograniczoną odpowiedzialnością 
>spółka komandytowa), address: 85-240 Bydgoszcz, Kraszewskiego 1 , entered in 
>the register of entrepreneurs of the National Judicial Register under the 
>number 811198 by the District Court in Bydgoszcz, XIII Commercial 
>Department of the National Judicial Register, NIP: 5213207288, share capital 
>PLN 3 805 500. As its integrity cannot be secured on the Internet, the Atos 
>group entities liability cannot be triggered for the message content. Although 
>the sender endeavors to maintain a computer virus-free network, the sender 
>does not 
 warrant that this transmission is virus-free and will not be liable for any 
damages resulting from any virus transmitted.

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
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: Error

[cygwinautoreply]

>Hey man, im getting a error here: (deep_ne)
>C:\Users\User\PycharmProjects\Chapter10\gym_tensorflow\atari>cd .\atari-py
>&& make
>  1 [main] make 21104 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem to
>the public mailing list cygwin@cygwin.com
>make -C atari_py/ale_interface build
>make[1]: Entering directory
>`/cygdrive/c/Users/User/PycharmProjects/Chapter10/gym_tensorflow/atari/atari-py/atari_py/ale_interface'
>mkdir -p build && cd build && cmake .. && make -j4
>make[1]: /bin/sh: Command not found
>Makefile:4: recipe for target `build' failed
>make[1]: *** [build] Error 127
>make[1]: Leaving directory
>`/cygdrive/c/Users/User/PycharmProjects/Chapter10/gym_tensorflow/atari/atari-py/atari_py/ale_interface'
>Makefile:4: recipe for target `build' failed
>make: *** [build] Error 2


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error with Ns-2

[Robert Akromond]

Thank you for your response.
I will send you screenshots of the error I am getting .

On Sun, Feb 9, 2020, 7:59 PM Marco Atzeri  wrote:

> Am 09.02.2020 um 20:27 schrieb Robert Akromond:
> > Hello,
> > I am having difficulties in starting the server using startx or startwin
> or
> > xinit and xterm is also not working for me.
> > I hope to get solutions from you soon.
> >
> > Thank you.
> >
> > Kind regards,
> > Robert Akromond.
> >
>
> a bit more details ?
>
> What is the problem using startxwin ?
> What is the issue using the Xwin Server icon on the start menu list ?
>
> Please note that NS-2 is not a package provided by the Cygwin
> distribution, so we have no clue of your expectation.
>
> Regards
> Marco
>
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error with Ns-2

[Marco Atzeri]

Am 09.02.2020 um 20:27 schrieb Robert Akromond:

Hello,
I am having difficulties in starting the server using startx or startwin or
xinit and xterm is also not working for me.
I hope to get solutions from you soon.

Thank you.

Kind regards,
Robert Akromond.



a bit more details ?

What is the problem using startxwin ?
What is the issue using the Xwin Server icon on the start menu list ?

Please note that NS-2 is not a package provided by the Cygwin 
distribution, so we have no clue of your expectation.


Regards
Marco


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error running ssh windows binary in cygwin

[ASSI]

ravi r writes:
> Following directions mentioned in above error message, when I search for
>  cygwin1.dll
> I find two matches
> c:\cygwin64\bin
> and
> c:\cygwin64\usr\i686-pc-cygwin\sys-root\usr\bin

The latter would be the Cygwin DLL for the 32bit cross compilation toolchain.

> Went ahead and deleted
> c:\cygwin64\usr\i686-pc-cygwin\sys-root\usr\bin\cygwin1.dll
> opened a new cygwin terminal and the error from ssh.exe would not go away.

Why would you have this directory in PATH in the first place?

> I know there is a version of git available through cygwin install as
> well which does not have these errors. The git.exe which got installed
> from windows binary does not have any error in starting up. It is the
> ssh.exe which comes along with it which has the problem.

Again, if you have different installations on the same system, you
should have only one of them in PATH at any given time.  Also, Git for
Cygwin uses MSys2, not Cygwin; so again it is unclear if you really ran
the MSys2 ssh, it should not have looked for a cygwin1.dll.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error running ssh windows binary in cygwin

[Marco Atzeri]

Am 22.01.2020 um 23:30 schrieb ravi r:

Downloading windows git binary from
https://git-scm.com/download/win
   Git-2.25.0-64-bit.exe
and running the contained
Git/usr/bin/ssh.exe
in a cygwin terminal gives this error
   0 [main] ssh (20916) C:\cygwin64\usr\local\git\usr\bin\ssh.exe: *** fatal
   error - cygheap base mismatch detected - 0x18033F408/0x180317408.
   This problem is probably due to using incompatible versions of
the cygwin DLL.
   Search for cygwin1.dll using the Windows Start->Find/Search facility
   and delete all but the most recent version.  The most recent
version *should*
   reside in x:\cygwin\bin, where 'x' is the drive on which you have
   installed the cygwin distribution.  Rebooting is also suggested if you
   are unable to find another cygwin DLL.

Following directions mentioned in above error message, when I search for
  cygwin1.dll
I find two matches
 c:\cygwin64\bin
 and
 c:\cygwin64\usr\i686-pc-cygwin\sys-root\usr\bin


the first is a 64 bit and the second a 32bit used for cross compilation.
Have you installed every package available ? Why ?

https://cygwin.com/faq.html#faq.setup.everything



Went ahead and deleted
 c:\cygwin64\usr\i686-pc-cygwin\sys-root\usr\bin\cygwin1.dll
opened a new cygwin terminal and the error from ssh.exe would not go away.

I know there is a version of git available through cygwin install as
well which does not
have these errors. The git.exe which got installed from windows binary
does not have
any error in starting up. It is the ssh.exe which comes along with it
which has the problem.


Have you tried the ssh coming with Cygwin ?


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in installing cygwin

[cygwinautoreply]

> 2 [main] bash 12628 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem to
>the public mailing list.


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error running HEG

[Brian Inglis]

On 2019-11-20 03:17, Yamuna_Giambastiani wrote:
> Hello, i am new in this forum,
> i do not know if i am in the right section
> but, i am trying to use HEG for convert a HDF to GEOTiff, but it not works!
> i am at 8 point of the readme_install_Win (seven)

A little searching would have confirmed you are not, and found more appropriate
venues, but as you did not, and are having difficulties, you may want to consult
your IT development group, or a colleague with more experience in such matters.

You appear to be trying to install or build a NASA Java application

https://newsroom.gsfc.nasa.gov/sdptoolkit/HEG/HEGHome.html

so you may want to try reading the FAQ

https://newsroom.gsfc.nasa.gov/sdptoolkit/HEG/HEGFAQ_Problems.html

download the current release

https://newsroom.gsfc.nasa.gov/sdptoolkit/HEG/HEGDownload.html

follow the instructions


https://newsroom.gsfc.nasa.gov/sdptoolkit/HEG/HEG215/README_INSTALL_Win_v2.15

and the problem troubleshooting advice there;

subsribe to and post to a relevant mailing list

https://lists.nasa.gov/mailman/listinfo/hdf-eos

or email the development support team

mailto:heg-supp...@earthdata.nasa.gov


-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error "fatal: write failure on 'stdout': No error" in native console

[Duncan Roe]

Hi Audrey,

On Fri, Aug 16, 2019 at 01:36:58PM +0300, Andrey Repin wrote:
> Greetings, All!
>
> I'm trying to resolve the problem at my new workplace, which seems to be
> affecting the ability to use git with VS Code.
> It just does not see the repo, no matter if I point its nose directly to the
> directory.
>
> When toying around the terminal, I noticed that calling simple
>
> > git log | head -1
> commit 8f4c6f50a4c6becee2c6007fdb2e67be70fc06b6
> fatal: write failure on 'stdout': No error
>
> Bummer. I can't replicate it on my home system, which have more or less
> identical setup.
> Any pointers?
>
> P.S.
> This all happens on Win7 PRO.
>
>
> --
> With best regards,
> Andrey Repin
> Friday, August 16, 2019 13:32:30
>
> Sorry for my terrible english...

Cheap & cheerful solution:

> git log | head -1 2>/dev/null

You got your 1 line of output.

The head program closes stdin after reading "n" lines. That sends SIGPIPE to the
previous process, or EPIPE to write(), if SIGPIPE is caught. I suspect you are
seeing the latter, but with errno not getting set properly for some reason.

If you would care to experiment with a simple C program that outputs a few lines
and try catching SIGPIPE you may well come up with an STC.

Cheers ... Duncan.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error Message, Need help

[cygwinautoreply]

>system(paste('gzip -d',ff))
>  1 [main] gzip 42336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem to
>the public mailing list cygwin@cygwin.com

>gzip: stdin: unexpected end of file
>Warning message:
>running command 'gzip -d ' had status 1


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error

[cygwinautoreply]

>=C2=A02 [main] popdist 8740 find_fast_cwd: WARNING: Couldn't compute FAST_C=
>WD pointer.=C2=A0 Please report this problem tothe public mailing list cygw=
>i...@cygwin.com
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
>=A0 =C2=A0 Popdist version 1.2.4Built Oct=C2=A0 9 2012Copyright (c)=C2=A0 B=
>ernt Guldbrandtsen and Aarhus University=C2=A0 Foulum, 1997-2000,2003,2007,=
>2011-2012


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error message during compilation

[cygwinautoreply]

>3 [main] make 2520 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem to
>the public mailing list cygwin@cygwin.com.
>Please suggest me what to do for this type of error
>Thank you

>Nanaiah.M


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error running phoronix test suite iozone 1.9.5

[cygwinautoreply]

>I get the following error(s)
>"*1  [main] iozone 3684 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer*"
>*Clement C. T. Ajaegbu*


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error Reporting

[cygwinautoreply]

>Hi, I got this message when I was extracting a ROM: "2 [main] tar 2152
>find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  Please report
>this problem to
>the public mailing list cygwin@cygwin.com" though the ROM extraction was
>successful


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error message

[cygwinautoreply]

>Hi, I am trying to get astrotortilla to work. I see in the log file where I
>have an error.

> 

>Maybe you can help me figure out what the problem is from the log file. If
>you can help me great, if not please point me in the right direction to get
>help. I can supply the jpg file I am using if needed. I did try this same
>file on nova.astrometry.com and it worked.

> 

>The error message:

>2019-03-01 21:21:31,723 - astrotortilla - INFO -   2 [main] bash 16960
>find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  Please report
>this problem to

> 

>2019-03-01 21:21:31,832 - astrotortilla - INFO - the public mailing list
>cygwin@cygwin.com

> 

>Thanks, Jack

> 



https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error regarding find_fast_cwd

[Marco Atzeri]

Am 13.02.2019 um 06:22 schrieb Tokala, Bala Murali:

Dear Sir/Madam


  I am getting the follwing error . please help me in getting over it .



1 [main] lm32-elf-gdb 17116 find_fast_cwd: WARNING: Couldn't compute
FAST_CWD pointer.  Please report this problem to the public mailing list
cygwin@cygwin.com
.gdbinit: No such file or directory.



https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error Reporting

[Brian Inglis]

On 2019-01-31 19:49, Samuel Cape wrote:
> I'm trying to use the Render Street plugin to send my render job (which
> includes video files), and I encounter the following error:
> 1 [main] rsync 7388 find_fast_cwd: WARNING: Couldn't compute FAST_CWD 
> pointer.  Please report this problem to the public mailing list
> cygwin@cygwin.com
> So... here I am mailing the public mailing list.

This is just a warning to please upgrade Cygwin as explained at:

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

and please report the issue to whoever produces the software you are using.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error?

[Andrey Repin]

Greetings, Werner!

> C:\Users\xyz\Downloads\john179w2\john180j1w\run>rar2john.exe 
> hekate_ctcaer_4.5.rar
>    1 [main] rar2john 10060 find_fast_cwd: WARNING: Couldn't compute 
> FAST_CWD pointer.  Please report this problem to
> the public mailing list cygwin@cygwin.com
> hekate_ctcaer_4.5.rar:$rar5$16$b4081e037140981e3822e45c6f66b030$15$12e1ea2487855a151650a264e007deef$8$7ebc0a2416d330c4

No, this is a warning, not an error.
And it was fixed over a decade ago. Please update your Cygwin installation.
See https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings


-- 
With best regards,
Andrey Repin
Sunday, December 9, 2018 1:03:56

Sorry for my terrible english...
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error installation HEG conversion Tool

[Brian Inglis]

On 2018-11-08 06:37, laura champin wrote:
> I want to install HEG conversion Tool but HEG GUI disappears right after 
> opening. I open a MS DOS command window. In that window I change the
> directory to HEG's bin directory and type HEGTool.bat. and I have the message:
> C:\Users\l.champin\Downloads\hegWINv2.14_FullCyg\HEG_Win\bin>HEGTool
> 2 [main] hegtool 11632 find_fast_cwd: WARNING: Couldn't compute FAST_CWD 
> pointer. Please report this problem to the public mailing list
> cygwin@cygwin.com
> What's the problem? What can I do to resolve it?

This is just a warning to please upgrade Cygwin as explained at:

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

and please report the issue to whoever produces the software you are using.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error Message Kindle Fie Utility v0.9.9

[Marco Atzeri]

Am 30.10.2018 um 16:57 schrieb Greg Viola:

Apps Installer encountered the following issues:






   0 [main] cat 47360 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
pointer.  Please report this problem to




Hi Greg,
the warning is unrelated to your problem

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

It seems that whoever distributed  Kindle Fie Utility v0.9.9
has bundled an old copy of the cygwin1.dll
Please followup with them


Regards
Marco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error

[Marco Atzeri]

Am 22.10.2018 um 18:46 schrieb john doe:

On 10/22/2018 6:32 PM, sidrah ijaz wrote:

could not compute FAST_CWD pointer



Not sure if the above is a question.

https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings

HTH.



Joe,
It is. Adding original sender in copy.

Sidrah,
your mail is a record of short length.
If this was real problem and you were asking support you are supposed
to provide much more info than just copy the error message.
Have you thought that an error message can be shared by hundred of
application and to help you anyone should receive some informations ?
Or you think a customer support will magically know the details
of your problem that you missed to provide ?

In this case our faq explain the matter
https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings

and you can report the issue to whoever is distributing the software
you are using.

Regards
Marco



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error

[john doe]

On 10/22/2018 6:32 PM, sidrah ijaz wrote:
> could not compute FAST_CWD pointer
> 

Not sure if the above is a question.

https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings

HTH.

-- 
John Doe

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in opengrad software

[Michael Haubenwallner]

Hi,

On 09/25/2018 08:53 AM, nithan santiago wrote:
> Hi,
> i am using a Dell inspiron 5368 model with 7th gen i3 processor with 4 gb
> ram and runs in windows 10 64-bit version. I am getting an error in running
> this program(OpenGrADS), it shows that "couldn't compute FAST_CWD pointer",
> if u have solution please reply as soon as possible, thanking you in
> advance.
> 

unfortunately, web search engines seem to not find that FAQ entry yet:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

HTH,
/haubi/

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Thomas Wolff]

Am 31.08.2018 um 22:05 schrieb Eric Blake:

On 08/31/2018 02:48 PM, cyg Simple wrote:



Don't forget the possibility that '..' points to a symlink which Windows
will not understand.

$ mkdir -p /foo/baz
$ ln -s /foo /bar
$ cd /bar/baz
$ cygpath -w ..


Except .. never points to a symlink.  It always points to the physical 
directory that contains the current directory (that is, /foo, not 
/bar).  The shell can maintain a notion of a logical current directory 
(based on whether you use 'set -P' for physical or 'set +P' for 
logical; where bash defaults to +P), and in that mode, 'cd ..' behaves 
logically (acting as though you are now in /bar, rather than actually 
changing you to /foo).  But that still doesn't change the fact that 
'..' in file name resolution never resolves to a symlink, because the 
shell is merely rewriting your ".." to avoid passing it on to the 
syscalls, rather than the syscalls actually knowing about logical mode.
As a side-note, this is also the reason that you may be facing apparent 
inconsistency with path name completion,
like `ls ../[TAB]` suggesting you files and directories that do not 
exist once you run the command.

This is not cygwin-specific.

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Brian Inglis]

On 2018-08-31 16:34, Steven Penny wrote:
> On Fri, 31 Aug 2018 10:57:34, Corinna Vinschen wrote:
>> Long-standing behaviour.  ".." in Cygwin and ".." in Windows can totally
>> disagree.  The path is always convert to absolute at this point in favor
>> of correct output.  There's also the additional restriction (though
>> not in this case) that relative Windows paths must not be longer than
>> MAX_PATH (260) chars.
>> I'm certainly open to patches to the underlying cygwin_conv_path
>> function to change the Windows path to relative if possible.
> I am not understanding - it appears that "dot-dot" (..) is well defined by
> POSIX:
>> The special filename dot-dot shall refer to the parent directory of its
>> predecessor directory. As a special case, in the root directory, dot-dot may
>> refer to the root directory itself.
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13
> so it would appears that ".." would be an acceptable return value in any case.

See Eric Blake's response to other poster.
Proc FS entry /proc/self/cwd only links to the current working directory, and
may/does? not necessarily reflect the logical or physical path taken by cd to
get to the current directory: only the current shell tracks the logical or
physical path taken by cd to get to the current directory, and can interpret to
which directory .. refers.
If /proc/self/cwd tracked all processes' logical or physical paths taken by
chdir(2) to get to the current directory, that link might be used to resolve ..
unambiguously. Quoting Corinna: "PGA" ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Achim Gratz]

Steven Penny writes:
> I am not understanding - it appears that "dot-dot" (..) is well defined by
> POSIX:
[…]
> so it would appears that ".." would be an acceptable return value in any case.

Except that you've asked for a Windows path, not POSIX, and you have no
idea what Windows' idea of the CWD is once you start using that string
with a Windows application.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Steven Penny]

On Fri, 31 Aug 2018 10:57:34, Corinna Vinschen wrote:

Long-standing behaviour.  ".." in Cygwin and ".." in Windows can totally
disagree.  The path is always convert to absolute at this point in favor
of correct output.  There's also the additional restriction (though
not in this case) that relative Windows paths must not be longer than
MAX_PATH (260) chars.

I'm certainly open to patches to the underlying cygwin_conv_path
function to change the Windows path to relative if possible.


I am not understanding - it appears that "dot-dot" (..) is well defined by
POSIX:


The special filename dot-dot shall refer to the parent directory of its
predecessor directory. As a special case, in the root directory, dot-dot may
refer to the root directory itself.


http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13

so it would appears that ".." would be an acceptable return value in any case.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Eric Blake]

On 08/31/2018 02:48 PM, cyg Simple wrote:



Don't forget the possibility that '..' points to a symlink which Windows
will not understand.

$ mkdir -p /foo/baz
$ ln -s /foo /bar
$ cd /bar/baz
$ cygpath -w ..


Except .. never points to a symlink.  It always points to the physical 
directory that contains the current directory (that is, /foo, not /bar). 
 The shell can maintain a notion of a logical current directory (based 
on whether you use 'set -P' for physical or 'set +P' for logical; where 
bash defaults to +P), and in that mode, 'cd ..' behaves logically 
(acting as though you are now in /bar, rather than actually changing you 
to /foo).  But that still doesn't change the fact that '..' in file name 
resolution never resolves to a symlink, because the shell is merely 
rewriting your ".." to avoid passing it on to the syscalls, rather than 
the syscalls actually knowing about logical mode.


--
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[cyg Simple]

On 8/31/2018 4:57 AM, Corinna Vinschen wrote:
> On Aug 30 21:37, Steven Penny wrote:
>> It is my understanding that given relative input, "cygpath" shall produce
>> relative output unless given "-a" option. However I noticed a discrepancy. 
>> These
>> are all correct:
>>
>>$ cygpath .
>>.
>>
>>$ cygpath ..
>>..
>>
>>$ cygpath -w .
>>.
>>
>> This is not:
>>
>>$ cygpath -w ..
>>C:\cygwin64\home\
> 
> Long-standing behaviour.  ".." in Cygwin and ".." in Windows can totally
> disagree.  The path is always convert to absolute at this point in favor
> of correct output.  There's also the additional restriction (though
> not in this case) that relative Windows paths must not be longer than
> MAX_PATH (260) chars.
> 
> I'm certainly open to patches to the underlying cygwin_conv_path
> function to change the Windows path to relative if possible.

Don't forget the possibility that '..' points to a symlink which Windows
will not understand.

$ mkdir -p /foo/baz
$ ln -s /foo /bar
$ cd /bar/baz
$ cygpath -w ..

-- 
cyg Simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error in "cygpath" behavior

[Corinna Vinschen]

On Aug 30 21:37, Steven Penny wrote:
> It is my understanding that given relative input, "cygpath" shall produce
> relative output unless given "-a" option. However I noticed a discrepancy. 
> These
> are all correct:
> 
>$ cygpath .
>.
> 
>$ cygpath ..
>..
> 
>$ cygpath -w .
>.
> 
> This is not:
> 
>$ cygpath -w ..
>C:\cygwin64\home\

Long-standing behaviour.  ".." in Cygwin and ".." in Windows can totally
disagree.  The path is always convert to absolute at this point in favor
of correct output.  There's also the additional restriction (though
not in this case) that relative Windows paths must not be longer than
MAX_PATH (260) chars.

I'm certainly open to patches to the underlying cygwin_conv_path
function to change the Windows path to relative if possible.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


signature.asc
Description: PGP signature

Re: Error

[steve shepard]

Thank you, Andrey, for your helpful update.
My only two cents: Not every distribution uses the same installation directory 
for your product; I'd suggest those with this problem check the environment 
variables your project configuration uses.

Steve

From: cygwin-ow...@cygwin.com  on behalf of Andrey 
Repin 
Sent: Tuesday, July 31, 2018 1:11 PM
To: Medina, Adela; cygwin@cygwin.com
Subject: Re: Error

Greetings, Medina, Adela!

> 1 [main] make 1972 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer.  Please report this problem to
> the public mailing list cygwin@cygwin.com
> cd submodules && make all
> make: /bin/sh: Command not found
> Makefile:2: recipe for target `all' failed
> make: *** [all] Error 127

This is a WARNING, not an error. And the wording of it indicates that you are
using a very, very, very old Cygwin version. The probem was fixed over a
decade ago.
See http://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
for details.


--
With best regards,
Andrey Repin
Tuesday, July 31, 2018 16:09:58

Sorry for my terrible english...


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error

[Andrey Repin]

Greetings, Medina, Adela!

> 1 [main] make 1972 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer.  Please report this problem to
> the public mailing list cygwin@cygwin.com
> cd submodules && make all
> make: /bin/sh: Command not found
> Makefile:2: recipe for target `all' failed
> make: *** [all] Error 127

This is a WARNING, not an error. And the wording of it indicates that you are
using a very, very, very old Cygwin version. The probem was fixed over a
decade ago.
See http://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
for details.


-- 
With best regards,
Andrey Repin
Tuesday, July 31, 2018 16:09:58

Sorry for my terrible english...


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error when installing cygwin software

[Marco Atzeri]

Am 24.07.2018 um 13:39 schrieb Ngọc Anh Phạm:

Hi,I'm install cygwin 2.35 and now I am getting the following error:


Hi Phạm,

there is no version 2.35 as last one is 2.10.0-1
So I suspect you are installing something else or a very old version,
or you are confusing the version fo cygwin setup with the version of
the cygwin library.


+ Bash 872 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.


see
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings


I am using windows 10
I tried reinstalling
I tried againg uninstalling and installing in a different directory


Are you using the cygwin setup and following the guideline:
https://cygwin.com/cygwin-ug-net/setup-net.html


Can you give me a way to solve this problem?
Thanks so much!


Phạm Thị Ngọc Anh-0983693062


In case you have still problem and are you really trying
to install cygwin, please follow

Problem reports:   http://cygwin.com/problems.html


and provide as attachement the cygcheck.out

Regards
Marco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in PS2 Classic GUI

[Doug Henderson]

On 8 July 2018 at 07:24, Qaiser Farooq wrote:
> When i tried to encrypt WWE smack down here comes the pain ps2 game 4.4gb
> it showed me this error "invalid number of arguments for encryption"
>
> Please help

You may need to quote any file name that contains spaces..

HTH

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in PS2 Classic GUI

[Brian Inglis]

On 2018-07-08 09:42, Marco Atzeri wrote:
> Am 08.07.2018 um 15:24 schrieb Qaiser Farooq:
>> When i tried to encrypt WWE smack down here comes the pain ps2 game 4.4gb
>> it showed me this error "invalid number of arguments for encryption"
>>
>> Please help
>>
> please help us to help you.
> From your mail we have no clue of what you are doing and what is your
> expect result.
Believe he should be looking on http://aldostools.org/ for converting PS2 to PS3
format games but the tools use VB5 and that site was last updated about five
years ago.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in PS2 Classic GUI

[Marco Atzeri]

Am 08.07.2018 um 15:24 schrieb Qaiser Farooq:

When i tried to encrypt WWE smack down here comes the pain ps2 game 4.4gb
it showed me this error "invalid number of arguments for encryption"

Please help



please help us to help you.
From your mail we have no clue of what you are doing and what is your
expect result.



---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: ERROR: There was a serious problem creating a privileged user.

[Nuzhna Pomoshch via cygwin]

On 2018-05-22 20:21:50 Brian Inglis  wrote:
>On 2018-05-22 09:24, Nuzhna Pomoshch via cygwin wrote:
>> On Tue, 5/22/18, Marco Atzeri  wrote:
>> On 5/21/2018 11:53 PM, Nuzhna Pomoshch via cygwin wrote:
 Trying to configure ssh.
 Followed guides found on the internet (pretty much all the same).
 The problem comes when the script tries to create the user:
 *** Query: Create new privileged user account 'HOST\cyg_server' (Cygwin 
 name 'host cyg_server')? (yes/no) yes
 *** Info: Please enter a password for new user host+cyg_server. Please be 
 sure
 *** Info: that this password matches the password rules given on your 
 system.
 *** Info: Entering no password will exit the configuration.
 *** Query: Please enter the password:
 *** Query: Reenter:
 *** Info: User 'host+cyg_server' has been created with password 'password'.
 *** Info: If you change the password, please remember also to change the
 *** Info: password for the installed services which use (or will soon use)
 *** Info: the 'host+cyg_server' account.
 passwd: unknown user host+cyg_server
 *** Warning: Setting password expiry for user 'host+cyg_server' failed!
 *** Warning: Please check that password never expires or set it ot your 
 needs.
 No user or group 'host+cyg_server known.
 *** Warning: Assigning the appropriate privileges to user 
 'host+cyg_server' failed!
 *** ERROR: There was a serious problem creating a privileged user.
 *** Query: Do you want ot proceed anyway? (yes/no)
>>> It seems you miss the needed permission.
>>> Has your user admin privilege on the 'host' ?
>>> what system is ?
>> Yes, I ran the cygwin shell as administrator, and I
>> noticed (since it was the first time I had done that)
>> all of the files created in the home directory.
>> The system is Windows 7, 64-bit.
>
> Try setting up the cygserver service and creating the account with
> /bin/cygserver-config before setting up sshd with /bin/ssh-host-config.
>
> If you're going to run Cygwin services, multiple sessions, or many processes,
> especially in a domain, cygserver reduces the overhead.
>
> If you still have problems, run cygcheck -hrsv and attach the output to a 
> reply post.

That didn't work... the first time, but when I retried it, it did.
And strangely enough (I had to reinstall Windows and cygwin), the
exact same behavior occurred after the reinstallation (after running
cygserver-config, ssh-host-config failed the first time, and worked
the second time.

Thank you very much.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: ERROR: There was a serious problem creating a privileged user.

[Brian Inglis]

On 2018-05-22 09:24, Nuzhna Pomoshch via cygwin wrote:
> On Tue, 5/22/18, Marco Atzeri  wrote:
> On 5/21/2018 11:53 PM, Nuzhna Pomoshch via cygwin wrote:
>>> Trying to configure ssh.
>>> Followed guides found on the internet (pretty much all the same).
>>> The problem comes when the script tries to create the user:
>>> *** Query: Create new privileged user account 'HOST\cyg_server' (Cygwin 
>>> name 'host cyg_server')? (yes/no) yes
>>> *** Info: Please enter a password for new user host+cyg_server. Please be 
>>> sure
>>> *** Info: that this password matches the password rules given on your 
>>> system.
>>> *** Info: Entering no password will exit the configuration.
>>> *** Query: Please enter the password:
>>> *** Query: Reenter:
>>> *** Info: User 'host+cyg_server' has been created with password 'password'.
>>> *** Info: If you change the password, please remember also to change the
>>> *** Info: password for the installed services which use (or will soon use)
>>> *** Info: the 'host+cyg_server' account.
>>> passwd: unknown user host+cyg_server
>>> *** Warning: Setting password expiry for user 'host+cyg_server' failed!
>>> *** Warning: Please check that password never expires or set it ot your 
>>> needs.
>>> No user or group 'host+cyg_server known.
>>> *** Warning: Assigning the appropriate privileges to user 'host+cyg_server' 
>>> failed!
>>> *** ERROR: There was a serious problem creating a privileged user.
>>> *** Query: Do you want ot proceed anyway? (yes/no)
>> It seems you miss the needed permission.
>> Has your user admin privilege on the 'host' ?
>> what system is ?
> Yes, I ran the cygwin shell as administrator, and I
> noticed (since it was the first time I had done that)
> all of the files created in the home directory.
> The system is Windows 7, 64-bit.

Try setting up the cygserver service and creating the account with
/bin/cygserver-config before setting up sshd with /bin/ssh-host-config.

If you're going to run Cygwin services, multiple sessions, or many processes,
especially in a domain, cygserver reduces the overhead.

If you still have problems, run cygcheck -hrsv and attach the output to a reply
post.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: ERROR: There was a serious problem creating a privileged user.

[Nuzhna Pomoshch via cygwin]

On Tue, 5/22/18, Marco Atzeri  wrote:

On 5/21/2018 11:53 PM, Nuzhna Pomoshch via cygwin wrote:
> > Trying to configure ssh.
> > 
> > Followed guides found on the internet (pretty much all the same).
> > 
> > The problem comes when the script tries to create the user:
> > 
> > 
> > *** Query: Create new privileged user account 'HOST\cyg_server' (Cygwin 
> > name 'host cyg_server')? (yes/no) yes
> > *** Info: Please enter a password for new user host+cyg_server. Please be 
> > sure
> > *** Info: that this password matches the password rules given on your 
> > system.
> > *** Info: Entering no password will exit the configuration.
> > *** Query: Please enter the password:
> > *** Query: Reenter:
> >
> > *** Info: User 'host+cyg_server' has been created with password 'password'.
> > *** Info: If you change the password, please remember also to change the
> > *** Info: password for the installed services which use (or will soon use)
> > *** Info: the 'host+cyg_server' account.
> > 
> > passwd: unknown user host+cyg_server
> > *** Warning: Setting password expiry for user 'host+cyg_server' failed!
> > *** Warning: Please check that password never expires or set it ot your 
> > needs.
> > No user or group 'host+cyg_server known.
> > *** Warning: Assigning the appropriate privileges to user 'host+cyg_server' 
> > failed!
> > *** ERROR: There was a serious problem creating a privileged user.
> > *** Query: Do you want ot proceed anyway? (yes/no)
 
> It seems you miss the needed permission.
> Has your user admin privilege on the 'host' ?
> what system is ?
 
Hi. Thanks for the reply.

Yes, I ran the cygwin shell as administrator, and I
noticed (since it was the first time I had done that)
all of the files created in the home directory.

The system is Windows 7, 64-bit.

Nuzhna

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error using git-svn (module List::Util: No such process at /usr/share/perl5/5.26/XSLoader.pm line 96)

[Achim Gratz]

Ivan Garcia Sainz-Aja writes:
> I fixed my problem with git-svn downgrading  perl-Scalar-List-Utils to
> version 1.49 (instead of 1.50) from here
>
> http://mirrors.kernel.org/sourceware/cygwin/x86/release/
> perl-Scalar-List-Utils/
>
> I'm  attaching the file cygcheck.out

This doesn't show the module you talked about installed at all, several
other base packages seem to be missing from your installation and you've
apparently got some really unhealthy mixture of versions w.r.t. Git
itself (but I can't be sure about that information based on the other
two observations).  Whatever you're using to install your Cygwin is
probably not setup.exe or you've been messing with the installation in
some other way that fools cygcheck.  Please properly re-install Cygwin
with setup.exe before asking for further assistance here.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error using git-svn (module List::Util: No such process at /usr/share/perl5/5.26/XSLoader.pm line 96)

[Ivan Garcia Sainz-Aja]

 Hi Adam

I fixed my problem with git-svn downgrading  perl-Scalar-List-Utils to
version 1.49 (instead of 1.50) from here

http://mirrors.kernel.org/sourceware/cygwin/x86/release/
perl-Scalar-List-Utils/

I'm  attaching the file cygcheck.out

Thanks a lot for your help

Iván García

-- cygchek.out ---

Cygwin Configuration Diagnostics
Current System Time: Tue May 22 12:40:02 2018

Windows 10 Professional Ver 10.0 Build 16299

Running under WOW64 on AMD64

Path: C:\Users\IGSAIN~1\DOCUME~1\MOBAXT~1\slash\bin
C:\Users\IGSAIN~1\DOCUME~1\MobaXterm\slash\bin
C:\WINDOWS
C:\WINDOWS\system32

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

LD_LIBRARY_PATH = '/bin'
PWD = '/home/mobaxterm'
CYGWIN = 'nodosfilewarning glob:ignorecase proc_retry:360'
HOME = '/home/mobaxterm'

USERDOMAIN_ROAMINGPROFILE = 'INDRA'
HOMEPATH = '\Users\igsainzaja'
APPDATA = 'C:\Users\igsainzaja\AppData\Roaming'
ProgramW6432 = 'C:\Program Files'
MOBANOACL = 'true'
OneDrive = 'C:\Users\Administrator\OneDrive'
SSH_PAGEANT_PID = '11924'
SHELL = '/bin/bash.exe'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 94 Stepping 3, GenuineIntel'
HISTSIZE = '36000'
WINDIR = 'C:\WINDOWS'
HADOOP_HOME = 'D:\workspaces\bin\hadoop-common-2.2.0-bin-master'
SYMLINKS = 'C:/Users/IGSAIN~1/DOCUME~1/MobaXterm/slash/'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/home/mobaxterm/eclipse/PortalXunta.svn'
USERDOMAIN = 'INDRA'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
UATDATA = 'C:\WINDOWS\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
LC_ALL = 'es_ES.UTF-8'
GIT_EDITOR = '/bin/vim.exe'
!:: = '::\'
TEMP = '/tmp'
EXPORTED_DISPLAY = '10.8.0.193:0.0 '
COMMONPROGRAMFILES = 'C:\Program Files (x86)\Common Files'
SSH_AUTH_SOCK = '/tmp/ssh-WzgHrK/agent.2892'
TMOUT = '0'
USERNAME = 'igsainzaja'
PROCESSOR_LEVEL = '6'
CURRENT_USER_NAME = 'igsainzaja  '
ProgramFiles(x86) = 'C:\Program Files (x86)'
LIBGL_ALWAYS_INDIRECT = '1'
DWMMODE = 'no'
PSModulePath = 'C:\Program
Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules'
LOCALE = 'es_ES.UTF-8'
PUTTYHOME = 'D:\workspaces'
SYSTEMDRIVE = 'C:'
PROCESSOR_ARCHITEW6432 = 'AMD64'
JAVA_HOME = 'D:\workspaces\java\jdk1.8.0_161'
EDITOR = '/bin/vim.exe'
POPUPMODE = 'no'
MY_IP_ADDRESS = '10.8.0.193  '
VERSION = '10.5'
USERPROFILE = 'C:\Users\igsainzaja'
LANG = 'es_ES.UTF-8'
WINPATH =
'C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;D:\workspaces\java\jdk1.8.0_161\bin;D:\workspaces\bin\apache-maven-3.5.3\bin;C:\Program
Files\nodejs\;C:\Program Files (x86)\Yarn\bin\;C:\Program Files\Sublime
Text
3;D:\workspaces\bin\apache-ant-1.10.3\bin;D:\workspaces\bin\hadoop-common-2.2.0-bin-master\bin;C:\Users\igsainzaja\AppData\Local\Microsoft\WindowsApps;C:\Users\igsainzaja\AppData\Roaming\npm;C:\Users\igsainzaja\AppData\Local\Yarn\bin;'
PS1 = '\[\033]0;$PWD\007\]
\[\033[33m\][\D{%Y-%m-%d %H:%M.%S}]\[\033[0m\]  \[\033[35m\]\w\[\033[0m\]
\[\033[36m\][\u.\h]\[\033[0m\] \[\033(0\]b\[\033(B\] '
LOGONSERVER = '\\CORGRE12GC01'
KRB5_CONFIG = '/etc/krb5.conf'
CommonProgramW6432 = 'C:\Program Files\Common Files'
PROCESSOR_ARCHITECTURE = 'x86'
LOCALAPPDATA = 'C:\Users\igsainzaja\AppData\Local'
KRB5CCNAME = 'FILE:/etc/krb5_cc_cache'
HISTCONTROL = 'ignoredups'
ProgramData = 'C:\ProgramData'
EXECIGNORE = '*.dll'
SHLVL = '1'
USERDNSDOMAIN = 'INDRA.ES'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
LANGUAGE = 'es_ES.UTF-8'
HOMEDRIVE = 'C:'
COMSPEC = 'C:\WINDOWS\system32\cmd.exe'
TMP = '/tmp'
SYSTEMROOT = 'C:\WINDOWS'
PROCESSOR_REVISION = '5e03'
LC_CTYPE = 'es_ES.UTF-8'
PROMPT_COMMAND = 'r0=$?;if [ -z "$NP" ]; then i0=0;s0="";while [ "$i0" -lt
"${COLUMNS:-80}" ];do s0="q$s0";i0=$[$i0+1];done;builtin echo -ne
"\n\E[1;30m\E(0$s0\E(B\E[0m"; [ $r0 == 0 ] && builtin echo -ne
"\e[1A\e[32m\e(0d\e(B\e[0m\e[1B" || builtin echo -ne
"\e[1A\e[31m\e(0e\e(B\e[0m\e[1B";else unset NP;fi;history -a'
MY_COMPUTER_NAME = 'IGSAINZAJA10   '
VAGRANT_DETECTED_OS = 'cygwin'
PROGRAMFILES = 'C:\Program Files (x86)'
DISPLAY = '127.0.0.1:0.0'
NUMBER_OF_PROCESSORS = '4'
GIT_PAGER = '/bin/busybox.exe less -R'
SESSIONNAME = 'Console'
PUTTYTMP = 'C:\Users\IGSAIN~1\DOCUME~1\MobaXterm\slash\tmp'
HISTTIMEFORMAT = '[%Y-%m-%d %H:%M:%S] '
HISTFILE = '/home/mobaxterm/.bash_history'
TERMNUM = '2'
COMPUTERNAME = 'IGSAINZAJA10'
_ = '/bin/cygcheck'


obcaseinsensitive set to 1

Cygwin installations found in the registry:

c:  hd  NTFS122879Mb  44% CP CS UN PA FC OSDisk
d:  hd  NTFS350169Mb   3% CP CS UN PA FC Datos
f:  cd N/AN/A

D:\workspaces  /home/igsainzaja  user
binary,posix=0
D:\workspaces  /home/mobaxterm   user
binary,posix=0
C:\Users\IGSAIN~1\DOCUME~1\MOBAXT~1\slash  / system
binary,auto
C:\Users\IGSAIN~1\DOCUME~1\MOBAXT~1\slash\bin  /usr/bin  system
binary,auto
C:\Users\

Re: Error using git-svn (module List::Util: No such process at /usr/share/perl5/5.26/XSLoader.pm line 96)

[Adam Dinwoodie]

On Tue, 22 May 2018 at 09:35, Ivan Garcia Sainz-Aja wrote:
> Hi all,

> I'm getting the following error using git-svn (I think the only change I
> made was that I updated subversion)

> ➤ git svn rebase
> Can't load

'/usr/lib/perl5/vendor_perl/5.26/i686-cygwin-threads-64int/auto/List/Util/Util.dll'
> for module List::Util: No such process at
/usr/share/perl5/5.26/XSLoader.pm
> line 96.
>   at /usr/lib/perl5/vendor_perl/5.26/i686-cygwin-threads-64int/List/Util.pm
> line 23.
> Compilation failed in require at
> /usr/lib/perl5/vendor_perl/5.26/i686-cygwin-threads-64int/Scalar/Util.pm
> line 23.
> Compilation failed in require at
/usr/share/perl5/vendor_perl/5.26/Error.pm
> line 48.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/5.26/Error.pm line 48.
> Compilation failed in require at /usr/share/perl5/vendor_perl/5.26/Git.pm
> line 104.
> BEGIN failed--compilation aborted at
> /usr/share/perl5/vendor_perl/5.26/Git.pm line 104.
> Compilation failed in require at /usr/share/perl5/Git/SVN.pm line 24.
> BEGIN failed--compilation aborted at /usr/share/perl5/Git/SVN.pm line 24.
> Compilation failed in require at /usr/libexec/git-core/git-svn line 21.
> BEGIN failed--compilation aborted at /usr/libexec/git-core/git-svn line
21.

> --
> versions are:
> svn, version 1.9.7 (r1800392)
> git version 2.16.2
> perl (v5.26.1)


> Any idea how to make git-svn work again?

Hi Iván,

It looks like something has gone wrong with the Perl dependencies. Can you
please send in a cygcheck.out file per the problem report guidelines:

> Problem reports:   http://cygwin.com/problems.html

That should help us work out what's gone wrong here.

Adam

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: ERROR: There was a serious problem creating a privileged user.

[Marco Atzeri]

On 5/21/2018 11:53 PM, Nuzhna Pomoshch via cygwin wrote:

Trying to configure ssh.

Followed guides found on the internet (pretty much all the same).

The problem comes when the script tries to create the user:


*** Query: Create new privileged user account 'HOST\cyg_server' (Cygwin name 
'host+cyg_server')? (yes/no) yes
*** Info: Please enter a password for new user host+cyg_server. Please be sure
*** Info: that this password matches the password rules given on your system.
*** Info: Entering no password will exit the configuration.
*** Query: Please enter the password:
*** Query: Reenter:

*** Info: User 'host+cyg_server' has been created with password 'password'.
*** Info: If you change the password, please remember also to change the
*** Info: password for the installed services which use (or will soon use)
*** Info: the 'host+cyg_server' account.

passwd: unknown user host+cyg_server
*** Warning: Setting password expiry for user 'host+cyg_server' failed!
*** Warning: Please check that password never expires or set it ot your needs.
No user or group 'host+cyg_server known.
*** Warning: Assigning the appropriate privileges to user 'host+cyg_server' 
failed!
*** ERROR: There was a serious problem creating a privileged user.
*** Query: Do you want ot proceed anyway? (yes/no)



It seems you miss the needed permission.
Has your user admin privilege on the 'host' ?
what system is ?


Problem reports:   http://cygwin.com/problems.html



Regards
Marco

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error Report

[Brian Inglis]

On 2018-04-21 17:58, Henrique Oliveira wrote:
> I'm found this problem with instructions to send you guys on top, not sure
> what's wrong but happy to comply, let me know what else info you need.
> Microsoft Windows [Version 10.0.16299.371]
> (c) 2017 Microsoft Corporation. All rights reserved.
> C:\Users\Tingao>ls -l
>   0 [main] ls 15288 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer.  Please report this problem to
> the public mailing list cygwin@cygwin.com

This is just a warning to please upgrade Cygwin as explained at:

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

and please report the issue to whoever distributes the software that installed
the old Cygwin version.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error no 2 ,3

[Brian Inglis]

On 2018-04-21 01:21, Geetakshi Kandpal wrote:
> 1. I've already installed cygwin and NS2 software successfully but as soon
> as I give the command 'startx' in the cygwin shell , I get error no 2 and 3. 
> (Unable to connect to X server.)

Install a local X server by selecting and installing xinit and cygwin-x-doc
packages, while upgrading Cygwin as explained below, and at:

https://x.cygwin.com/

> 2. Also at the beginning it says 'couldn't compute FAST_CWD pointer. Please 
> report this problem to the public mailing list cygwin@cygwin.com'.

This is just a warning to please upgrade Cygwin as explained at:

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

and please report the issue to whoever distributes the software you are using.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in Cygwin 32 Bit in WIN 10 OS 64bit

[Marco Atzeri]

On 29/03/2018 08:02, SRI HARSHA Bulusu wrote:

Hi,


While running the build of software,i have encountered the following error

*[main] make 12276 E:\tools\cygwin\bin\make.exe: *** fatal error - couldn't
allocate heap, Win32 error 487, base 0x112, top 0x131, reserve_size
2027520, allocsize 2031616, page_const 4096*

*1961286814 [main] make 19884 child_info::sync: wait failed, pid 12276,
Win32 error 4390*

*1961330811 [main] make 19884 fork: child -1 - died waiting for longjmp
before initialization, retry 0, exit code 0x100, errno 11*

*make[3]: module.mak : 89: fork: Resource temporarily unavailable*



The first suggestion is to use the 64bit version of cygwin instead of 
the 32 bit; this reduce a lot the risk of fork failures.



As alternative, please provide the cygcheck.out
as mentioned on

Problem reports:   http://cygwin.com/problems.html


I suspect you have too many packages installed

Regards
Marco

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in Cygwin 32 Bit in WIN 10 OS 64bit

[Brian Inglis]

On 2018-03-29 09:02, SRI HARSHA Bulusu wrote:
> While running the build of software,i have encountered the following error
> "
> *[main] make 12276 E:\tools\cygwin\bin\make.exe: *** fatal error - couldn't
> allocate heap, Win32 error 487, base 0x112, top 0x131, reserve_size
> 2027520, allocsize 2031616, page_const 4096*
> *1961286814 [main] make 19884 child_info::sync: wait failed, pid 12276,
> Win32 error 4390*
> *1961330811 [main] make 19884 fork: child -1 - died waiting for longjmp
> before initialization, retry 0, exit code 0x100, errno 11*
> *make[3]: module.mak : 89: fork: Resource temporarily unavailable*
> "
> I check in cygwin FAQ and found it was due to *fork() failure*, and i have
> tried every step mentioned but same error is being encountered
> Please support me to eliminate the error

Have you tried downloading the latest setup-x86[_64].exe, and run it to upgrade
all packages to the latest release, with all Cygwin processes terminated first?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in Delta Copy

[Adam Dinwoodie]

On 26 March 2018 at 12:45, Alfonso Querol wrote:
> Hello,
>
> I'm using DeltaCopy V1.4 in a Windows Server 2012R2 Essentials and I have
> the next error although the copy goes aparently well.
>
> "Executing: rsync.exe  -v -rlt -z --chmod=a=rw,Da+x --delete
> "/cygdrive/C/x/xx/" "xxx.xxx.xxx.xx::ServMnDatos/x/"
>
>   0 [main] rsync 2564 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer.  Please report this problem to the public mailing list
> cygwin@cygwin.com"
>
> What's happening?
>
> Thank you very much
>
> Best Regards
>
> Alfonso

Hi Alfonso,

It looks like wherever you got DeltaCopy from is using an old copy of
Cygwin. This isn't something this mailing list list can help with;
you'll need to report this to whoever supports DeltaCopy.

There's a little more information at
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings.

Adam

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Error in Generating XWin

[Marco Atzeri]

On 24/03/2018 06:51, Roshan Jha wrote:

Respected Sir,

I am facing problem in starting XWin using (Startx). It shows some fatal
error such as not connecting to X-server, or resource not available, or
connection refused.


Dear Roshan,
you are a bit vague.
You need to be more precise on what you are doing and
the exact error messages.

In cygwin the proper way to start X server is to use startxwin.


Along with it, "1 [main] bash 1744 find_fast_cwd: WARNING: Couldn't compute
FAST_CWD pointer." Also there on Cygwin command prompt.

Please resolve this issue also suggest me how to fix these issues.

Roshan Jha


The warning seems to indicate that you are using an old version

Please follow guidelines

Problem reports:   http://cygwin.com/problems.html

and provide as attachment the cygcheck.out

Regards
Marco

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: error

[Marco Atzeri]

On 23/03/2018 22:10, Arthur Philippi Bianco wrote:

1 [main] sh 7968 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  
Please report this problem to
the public mailing list cygwin@cygwin.com


Hi Arthur,
we assume you are using a software that includes an old version of 
cygwin1.dll shared library


https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings

Please asks who distribute that software to upgrade their distribution

Regards
Marco



--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple