Cygwin 1.7.1 sprintf() with format string having 8th bit set

[Joseph Quinsey]

Hello,

In Cygwin 1,7.1, sprintf() with the format string having an 8th bit set
appears to be broken. Sample code (where I've indicated the backslashes in
the comments, in case they are stripped out by the mailer):

#include 

int main (void)
{
unsigned char foo[30] = "";
unsigned char bar[30] = "";
unsigned char xxx[30] = "";
sprintf (foo, "\100%s", "ABCD"); /* this is backslash one zero zero   */
sprintf (bar, "\300%s", "ABCD"); /* this is backslash three zero zero */
sprintf (xxx, "\300ABCD");   /* this is backslash three zero zero */
printf ("%d %d %d %d %d\n", foo[0],foo[1],foo[2],foo[3],foo[4]);
printf ("%d %d %d %d %d\n", bar[0],bar[1],bar[2],bar[3],bar[4]);
printf ("%d %d %d %d %d\n", xxx[0],xxx[1],xxx[2],xxx[3],xxx[4]);
return 0;
}

gives:

64 65 66 67 68
0 0 0 0 0
192 65 66 67 68

The second line of the output should be the same as the third.

This problem is likely to affect programs using xterm as a pseudo-terminal.
The number octal 300 (decimal 192) isn't significant here.

Regards, Joe Quinsey



--
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: chmod in cygwin

[René Berber]

Linda Armelle Nzumotcha Tchoumkam wrote:
> 
> I am a new user of cygwin in windows xp.
> I want to run an executable program connected to cygwin.
> I use the command chmod as ( “[ugoa]*<[-+=]<[rwxXst]*|[ugo]>>+”  write “chmod
> a+x /C/Program/flow”)
> But I don’t get to the executable program. I receive this message:
> chmod a+x /C/Program/flow : No such file or directory
--^
Just what it says, you probably want:

chmod a+x /cygdrive/c/Program/flow

assuming "Program" is not really "Program Files" and "flow" is an actual
file or directory, not "flow.exe" or something else.

Hope this helps.
-- 
René Berber


--
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: using a serial port with cygwin

[Larry Hall (Cygwin)]

On 01/01/2010 10:16 PM, Rance Hall wrote:

Ive been reading up on this and I think I have a handle on knowing
that I can use comx in cygwin or maybe /dev/ttySx  with my usb-serial
adapter.


Use the /dev/ttySx form when in the Cygwin world.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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: chmod in cygwin

[Rosario D. Contarino]

If it can be of any help, why don't you try to execute some other
programs instead of chmod and see if you get the same error,
for example instead of "chmod a+x /C/Program/flow" something like
"ls -d /C/Program/flow" and see if works.

If it does then we can say something can be wrong with chmod, if it
doesn't then chmod was right and there must be something wrong on
finding that file with the path you gave ... just a suggestion.

Cheers
Dario


Linda Armelle Nzumotcha Tchoumkam wrote:
> 
> I am a new user of cygwin in windows xp.
> I want to run an executable program connected to cygwin.
> I use the command chmod as ( “[ugoa]*<[-+=]<[rwxXst]*|[ugo]>>+”  write “chmod
> a+x /C/Program/flow”)
> But I don’t get to the executable program. I receive this message:
> chmod a+x /C/Program/flow : No such file or directory
> 
> I already read http://cygwin.com/faq/faq_4.html#SEC45
> 
> Really,  I don’t  know if the command is true.
> 
> What’s wrong?
> 
> Thanks
> 
> 
> --
> 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: git stopped working with 1.7.1

[David Antliff]

On Mon, Jan 4, 2010 at 15:06, Kevin Layer wrote:
> I'm not using the git protocol.  Note the single slash.  The machine
> is named `git', which is what is confusing you.  Anything of the form
> "foo:/path" uses SSH, which is what this is using.

Yes, you're right, I'm so used to seeing git://server syntax that I
was a bit thrown by the git:/path syntax.

-- David.

--
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: Chagrin 1.7.1 install halting on Windows 7

[Larry Hall (Cygwin)]

On 01/02/2010 12:24 PM, Durwin wrote:

I have just received an Alienware laptop with Windows7.  I downloaded
and ran the current setup from website.  The install process will stop
at various stages, not always the same place.  By stop, I mean it looks
as if it is working, but it never proceeds past that point.  I believe
it does all the install stages, but will stop at different places after
the install.

A few times the install completed.  When testing those times, I would
run bash from Windows command line (just as the .bat file does).  Once I
got some memory error I can't recall.  The rest of the times I get the
Cygwin console opening, but goes away imediately without every
displaying a prompt.  All through this, not one error message.


In this case, you want to start a Windows command prompt and run
c:\cygwin\cygwin.bat from there.  This will keep the command prompt
window open so you can see any complaint.


My search on this issue showed a few people with simular problem.  One
had same issue with command line window opening and closing but was using
1.5 and their problem went away when they used 1.7.  I suspect the
problem is the install (even though it completed install a few times).
I ran msconfig and removed all none Microsoft processes but still could
not get the install to complete.


Look at /var/log/setup.log.full for any complaints.  My WAG is
.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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

chmod in cygwin

[Linda Armelle Nzumotcha Tchoumkam]

I am a new user of cygwin in windows xp.
I want to run an executable program connected to cygwin.
I use the command chmod as ( “[ugoa]*<[-+=]<[rwxXst]*|[ugo]>>+”  write “chmod
a+x /C/Program/flow”)
But I don’t get to the executable program. I receive this message:
chmod a+x /C/Program/flow : No such file or directory

I already read http://cygwin.com/faq/faq_4.html#SEC45

Really,  I don’t  know if the command is true.

What’s wrong?

Thanks


--
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: 1.7.1: Does 'chere' work with Vista 64b? Can't tell by me.

[Lee D. Rothstein]

Dave wrote:

Lee D. Rothstein wrote:
  

Dave wrote:

 > Check HKEY_CLASSES_ROOT\Directory\Shell\cygwin_bash. It's value should
 > be the context menu item text, "Mintty Bash"

Value was null.

 > It should have one subkey, command, whose value is the command to run
 > "c:\_0\bin\mintty ...".

Value was null.



Either registry virtualisation, or redirection is interfering.




My guess is the latter. This is consistent with Larrys' report of chere
working on 64 bit Windows 7, as Microsoft states HKLM/SOFTWARE/Classes
is shared on W7 and redirected+reflected on vista, server 2003, server
2008, xp. 

I'm not on windows right now, but does regtool have the ability to
control redirection/reflection or whether it writes to the 32/64 bit
version of the key? That's what chere would need to operate correctly.
Otherwise it needs to resort to outputting a .reg file and installing it.

  
I doubt that you're asking me, but if you are: I can barely parse your 
question, much less answer meaningfully.

Did you include the '-e /bin/xhere /bin/bash "%L"'? That's the bit that
selects the folder.

  

No, I hadn't but I have since and lo' and behold, it works. Thanks.

Chere still broken, although now I personally don't need it.


--
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: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Larry Hall (Cygwin)]

On 01/01/2010 04:52 PM, Lee Rothstein wrote:

Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)


NTFS junctions are for directories only..  For files and directories, one could
use "mklink" on Vista and newer, with the caveats mentioned here
. 
Oh and

for all those wondering, this still isn't enough to be a drop-in replacement
for Cygwin's symbolic links unfortunately.  If you're curious about this, see
the email archives for discussions about it.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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: git stopped working with 1.7.1

[Kevin Layer]

Brian L.  wrote:

>> I'm seeing very similar bad behavior from cygwin+git on win7 x64 as
>> well as winxp x86. This bug is not confined to 64 bit platforms. This
>> bug is new in 1.7.x--I have cygwin 1.5 installs on both of these
>> machines that do not exhibit this failure.
>> 
>> The problem seems to be rooted in cygwin's openssh package. If I point
>> GIT_SSH at plink.exe (from the putty distribution) and configure
>> pageant properly for keyless login then git works fine.

Good sleuthing!


--
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: git stopped working with 1.7.1

[Kevin Layer]

David Antliff  wrote:

>> On Thu, Dec 24, 2009 at 07:55, Kevin Layer  wrote:
>> >  la...@hobart128 /c/tmp
>> >  $ git clone git:/repo/git/acl acl.test
>> >  Initialized empty Git repository in /c/tmp/acl.test/.git/
>> >  remote: Counting objects: 9205, done.
>> >  remote: Compressing objects: 100% (3300/3300), done.
>> >  fatal: The remote end hung up unexpectedly
>> >  fatal: early EOFs:  62% (5708/9205)
>> >  fatal: index-pack failed
>> 
>> I'm no git expert, but that looks to me like the remote side (where
>> the repository is stored) is experiencing the error while it's
>> preparing data for transfer, and your local git is simply reporting
>> the remote error. It also looks like the remote side is actually the
>> same machine but you're using the git:// protocol to access it without
>> specifying a remote server. I've never tried this and would have
>> expected instead to see something like:

I'm not using the git protocol.  Note the single slash.  The machine
is named `git', which is what is confusing you.  Anything of the form
"foo:/path" uses SSH, which is what this is using.

The server is hanging up, yes, but perhaps the client isn't sending
the right responses.

>> Since it looks like the remote is on the same machine as your shell,
>> do you have write access to the actual repository? If so, you could
>> run git-fsck on the repository to make sure it's intact.

No, it's on a different machine, but there is absolutely nothing wrong
with the repo.

I've tried *THREE* Windows machines now.  On all, git stops working
when cygwin is upgraded.  Works before.  Doesn't work after.  Period.

It is not a problem on the server.  There are 10+ of people using it
every minute of the day and no one has had a problem.  Ever.

>> What about other repositories, do they behave the same way, or is your
>> problem restricted to this one?

It's random (at what percentage) where it dies (with this repo).  It
randomly dies with other repos, too.

I did install 1.5.25 on the 64-bit Windows 7 machine and git works
fine.  I've sucked an enormous amount of data off the git server with
it, too, and not one problem.

Kevin

--
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: Revamp cygwin.com project page?

[Christopher Faylor]

On Mon, Jan 04, 2010 at 01:36:06AM +0100, Thomas Wolff wrote:
>I've set up a sample at ...

You're putting me in the situation of practically begging me to be mean.
As much as everyone thinks I may enjoy that, I really don't.

But, since you asked.  I *really* don't like the redesigned red left
menubar.

Since Corinna isn't around to weigh in on this and since this is a
situation of "It ain't broke", I don't think I want to encourage people
to promote their designs.  This is especially true given that I have
little patience for public tweaking of things like this since it is just
begging to be a bike shed situation.

cgf

--
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: Revamp cygwin.com project page?

[Thomas Wolff]

Reini Urban schrieb:

2009/12/26 Kristopher Ives:
  

Thanks. I can modify the colors and the logo idea was just to see what
people thought. The design was very short work and was my attempt at
giving back to the Cygwin project. I was needing feedback and wanted
to know if this was a possibility.



I also dislike the color (brown?) and new logo, but the layout could
definitely need
a refresh.
But please no MS-like light blue as the new postgresql page.
  

And please, no MS-like boring fonts either.


Christopher Faylor had written:

Thanks for the offer but I don't like the color scheme or the
newly-invented logo.  There also isn't enough to go on in this page to
really decide if it's worth changing especially since I can't look at
the html and so, don't know how hard it would be to maintain -
especially since that look and feel would have to be propagated to all
the other cygwin pages.
I've set up a sample at http://towo.net/cygwin/cygwin.html to 
demonstrate that a lot can be tuned with minimal modification of the 
actual HTML page (just one line, the reference to the style sheet).

So the modified navigation area is completely style-sheet-driven only.

By the way, wasn't the discussion going towards the fancy new hippo icon 
to replace the edgy C?
Actually I had the idea to modify the hippo slightly to carve a letter C 
along the shape of its bottom...
Maybe someone with more experience in graphics tools could give it a 
try..


Thomas

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

Extracting arpack-96-2-src.tar.bz2

[Stephen Grant Brown]

Dear All


From the attached set.log.full file it can be seen that


2010/01/04 11:06:19 Extracting from 
file://O:\CygWIN-1p7_Downloads/http%3a%2f%2fcygwin.lilengine.com%2f/release/arpack/arpack-96-2-src.tar.bz2


a few times.

Is this correct behaviour?

It also does on subsequent runs of setup.exe

If it is not the correct behaviour, where do I look to debug this issue?

Yours Sincerely Stephen Grant Brown


setup.log.full
Description: Binary data
--
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: cygwin_create_path

[Andy Koppe]

2010/1/3 Andy Koppe:
> I'm having a spot of trouble changing mkshortcut to use the
> wchar_t-enabled cygwin_create_path instead of the deprecated
> cygwin_conv_to_full_win32_path & co. When converting to a Windows path
> using CCP_POSIX_TO_WIN_W, the result is a path starting with "\\?\",
> e.g. "\\?\C:\cygwin\bash.exe".
>
> Yet unfortunately the IShellLink::SetPath method does not appear to
> accept such paths, instead returning failure and leaving the link
> target unset. Therefore, is there a simple way to get from the full
> path to a "normal" path such as "C:\cygwin\bash.exe"? Simply dropping
> the "\\?\" wouldn't work for network paths. I haven't managed to find
> a solution on MSDN.

Handling this as follows now:
- If the path starts with "\\?\UNC\", replace that with "\\" (for
network paths).
- Otherwise, if the path starts with "\\?\", just remove that.

Andy


>
> Andy
>

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

License violation? (was: CygTeXmacs starting error)

[Yaakov (Cygwin/X)]

On 03/01/2010 05:48, Kalle Mikkola wrote:

I unzipped CygTeXmacs to a directory


Sounds strange, but the CygTeXmacs installation[1] includes an OLD 
cygwin1.dll (and an assortment of other packages), but the sources are 
not included in the download, I see no link thereto on the webpage, nor 
can I find them anywhere on their FTP server[2].



Yaakov
Cygwin/X

[1] http://www.texmacs.org/tmweb/download/windows.en.html
[2] ftp://ftp.texmacs.org/pub/TeXmacs/

--
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: select() and named pipes

[Christopher Faylor]

On Sun, Jan 03, 2010 at 05:58:46PM +0100, Enrico Forestieri wrote:
>On Wed, Dec 23, 2009 at 03:12:19AM +0100, Enrico Forestieri wrote:
>> On Tue, Dec 22, 2009 at 07:37:14PM -0500, Christopher Faylor wrote:
>> > On Tue, Dec 22, 2009 at 11:43:09PM +0100, Enrico Forestieri wrote:
>> > >I am experiencing a problem with select() and named pipes in cygwin
>> > >1.7.  The attached test case segfaults on the select() call, but works
>> > >fine with both cygwin 1.5 and linux.
>> > 
>> > Thanks for the test case.  This should be fixed in the next Cygwin
>> > snapshot but it will not be fixed (of course?) in 1.7.1 which is now
>> > available from the Cygwin web site.
>> 
>> I confirm that with the 20091222 snapshot the crash does not occur
>> anymore. However, there's still something wrong. Indeed, running the
>> test case in a terminal and issuing "echo foo > /tmp/pipe" from another
>> one, the program exits without printing the expected "foo".
>
>Apparently, the problem is due to the O_NONBLOCK flag used in the open()
>call. Taking away O_NONBLOCK, everything works.

I'm still tinkering with fifos.  I hope to have some fixes for Cygwin 1.7.2
but no guarantees.

cgf

--
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: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[tuli tanssi]

> You could create a Windows symbolic link using the Windows 'mklink'
> tool though, and it should work both in cmd.exe and in Cygwin.

Thanks for the info and Corinna's quote.

Probably I'll just create windows symlinks like from
c:\users\tuli\bin\gcc.exe to c:\cygwin\bin\gcc-3.exe
so that cygwin updates wouldn't break my modifications.

Cheers,
Tuli

--
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: select() and named pipes

[Enrico Forestieri]

On Wed, Dec 23, 2009 at 03:12:19AM +0100, Enrico Forestieri wrote:
> On Tue, Dec 22, 2009 at 07:37:14PM -0500, Christopher Faylor wrote:
> > On Tue, Dec 22, 2009 at 11:43:09PM +0100, Enrico Forestieri wrote:
> > >I am experiencing a problem with select() and named pipes in cygwin
> > >1.7.  The attached test case segfaults on the select() call, but works
> > >fine with both cygwin 1.5 and linux.
> > 
> > Thanks for the test case.  This should be fixed in the next Cygwin
> > snapshot but it will not be fixed (of course?) in 1.7.1 which is now
> > available from the Cygwin web site.
> 
> I confirm that with the 20091222 snapshot the crash does not occur
> anymore. However, there's still something wrong. Indeed, running the
> test case in a terminal and issuing "echo foo > /tmp/pipe" from another
> one, the program exits without printing the expected "foo".

Apparently, the problem is due to the O_NONBLOCK flag used in the open()
call. Taking away O_NONBLOCK, everything works.

This bug is causing an infinite loop in an application. The loop can
be reproduced by the slightly modified test case attached here.

When O_NONBLOCK is used, after issuing "echo foo > /tmp/pipe", read()
always returns -1 and sets errno to EAGAIN. However, according to
http://www.opengroup.org/onlinepubs/009695399/functions/read.html
this should only occur when reading from an empty pipe or fifo
and some process has the pipe open for writing and O_NONBLOCK is set.
Here, the fifo is not empty (as reported by select), and thus that
should not happen.

-- 
Enrico
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#define FIFONAME "/tmp/pipe"

int main(void)
{
int fd;
int nsel;
fd_set readfds;
FD_ZERO(&readfds);

if (mkfifo(FIFONAME, 0600) < 0) {
perror("mkfifo");
exit(1);
}

fd = open(FIFONAME, O_RDONLY | O_NONBLOCK);

if (fd < 0) {
perror("open");
remove(FIFONAME);
exit(2);
}

FD_SET(fd, &readfds);
do {
nsel = select(fd + 1, &readfds, 0, 0, 0);
} while (nsel == -1 && (errno == EINTR || errno == EAGAIN));

if (nsel == -1) {
perror("select");
exit(3);
}

if (FD_ISSET(fd, &readfds)) {
char buf[100];
int status;
int count = 0;
printf("%d: ", ++count);
while ((status = read(fd, buf, sizeof(buf) - 1))) {
if (status > 0) {
buf[status] = '\0';
printf("%s", buf);
} else if (errno == EAGAIN) {
printf("\n%d: ", ++count);
} else {
perror("read");
break;
}
}
}

close(fd);
remove(FIFONAME);
return 0;
}

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

cygwin_create_path

[Andy Koppe]

I'm having a spot of trouble changing mkshortcut to use the
wchar_t-enabled cygwin_create_path instead of the deprecated
cygwin_conv_to_full_win32_path & co. When converting to a Windows path
using CCP_POSIX_TO_WIN_W, the result is a path starting with "\\?\",
e.g. "\\?\C:\cygwin\bash.exe".

Yet unfortunately the IShellLink::SetPath method does not appear to
accept such paths, instead returning failure and leaving the link
target unset. Therefore, is there a simple way to get from the full
path to a "normal" path such as "C:\cygwin\bash.exe"? Simply dropping
the "\\?\" wouldn't work for network paths. I haven't managed to find
a solution on MSDN.

Andy

--
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: GCC, -rdynamic option is unrecognized by GCC.

[Claude Sylvain]

Dave Korn wrote:

> Cesar Strauss wrote:
>> but failed with undefined references when switching to gcc 4.3.4. They
>> seem to be related to some inline functions in toporouter.c.
>
>   The meaning of "extern inline" changed, to match c99.  See, for example:
>
> http://sourceware.org/ml/newlib/2007/msg00292.html
>
> and the references therein.
>

- Not sure if I understand how to apply the modification referred in
  "http://sourceware.org/ml/newlib/2007/msg00292.html";.

- But, I do the following:
- In "toporouter.c", replaced all "inline" keywords by
  "_ELIDABLE_INLINE" macro (found in "/usr/include/stdio.h").
  Result:  This do not solve the link problem!?

- In "toporouter.c", replaced all "inline" keywords by
  "extern inline" keywords.
  Result:  This solve the link problem.

- Is there some requirements (in a project), to be able to use
  "_ELIDABLE_INLINE" macro correctly?


Regards
Claude


--
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: [ANNOUNCEMENT] New: Updated: {ncursesw/libncursesw10/libncursesw-devel/ncursesw-demo}-5.7-18

[Andy Koppe]

2010/1/2 Charles Wilson:
> ncurses is a package that provides character and terminal handling
> libraries, including 'gui-like' panels and menus.  It is often used
> instead of termcap. ncursesw provides a version of this library and
> related tools compiled to support wide characters (that is, wchar_t
> rather than char).

Good stuff. Thanks!

Andy

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

[ANNOUNCEMENT] Updated: findutils-4.5.5-1

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A new release of findutils, 4.5.5-1, is available, leaving 4.5.4-1 as
previous.

NEWS:
=
This is a new upstream release.  Upstream news is attached.  See also
/usr/share/doc/findutils/.

DESCRIPTION:

The findutils package contains programs which will help you locate files
on your system.  The find utility searches through a hierarchy of
directories looking for files which match a certain set of criteria (such
as a filename pattern).  The xargs utility builds and executes command
lines from standard input arguments (usually lists of file names generated
by the find command).  The locate utility scans a database of filenames
and displays matches.  The updatedb utility builds the database for locate.

UPDATE:
===
To update your installation, click on the "Install Cygwin now" link on the
http://cygwin.com/ web page.  This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'findutils' from
the 'Base' category (it should already be selected).

DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need to
find a mirror which has this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html

QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

- --
Eric Blake
volunteer cygwin findutils maintainer

CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message.  Send email
to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktAnnEACgkQ84KuGfSFAYAGcgCg1ucpanEv/zzjbyLc2ZqGL6Oq
OycAoIOXXTq1ctzX0A7cwHlXZ72k85y8
=yPOJ
-END PGP SIGNATURE-
* Major changes in release 4.5.5, 2009-07-06

xargs now handles the case where the system's actual exec limits are
smaller than the value of ARG_MAX at compile time.  Very few platforms
normally have this property, but it is possible to configure some Unix
systems this way.

** Bug Fixes

#26587: Fix a typo in -execdir documentation (it says -exec by mistake
in the text).

#26537: find -prune now makes sure it has valid stat() information.

#22708: Exit status 126 and 127 from the utility invoked from xargs
now makes xargs return 123, meaning that exit status values 126 and
127 now unambigously mean that the utility could not be run or could
not be found, respectively.

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

[ANNOUNCEMENT] New: libncurses10-5.7-18; Updated: {ncurses/libncurses-devel/ncurses-demo}-5.7-18

[Charles Wilson]

ncurses is a package that provides character and terminal handling
libraries, including 'gui-like' panels and menus.  It is often used
instead of termcap.  Like the (new) ncursesw packages, it is
compiled with support for reentracy, and uses and uses the same ABI
number ("10" on cygwin for historical reasons; "ABI 6" according to
the upstream ncurses developers). ncurses is not compiled with full
multi-thread support, as that slows operation drastically (see below).

Note that this "reentrancy" support doesn't magically make your client
programs/libraries re-entrant. Internal to libncurses, all calls carry
a specific context variable.  However, the POSIX curses interface
still specifies calls that operate on the "current screen" -- an
obvious re-entrancy violation. Clients must instead use the non-POSIX
extensions provided by ncurses, to ensure that all curses operations are
actually re-entrant. That is:
  POSIX:  int addch(const chtype ch);
  REENTRANT:  int waddch(WINDOW *win, const chtype ch);
Naturally, if reentrancy is not a concern, the POSIX interface can
continue to be used as always. See the man pages for more information.

Clients can be made threadsafe, by universally using the reentrant
interfaces, and managing mutexes on the WINDOW* variables manually. If
ncurses were compiled with full thread support, the WINDOW object would
itself contain a mutex, and all ncurses calls would use it to manage
access. This slows ncurses to a crawl -- even in single-thread
applications. Therefore, I believe the better choice is to compile ncurses
with support for re-entrancy, so that multi-thread client apps that
actually NEED thread safety can use it, and make intelligent decisions


This is feature release, and an update to latest upstream. It is compiled
with support for reentrancy, and so breaks the previous ABI.  Therefore,
the runtime package and DLLs have been renamed to reflect the new ABI.

[[ compiled using gcc-4.3.4-3 ]]

As expected now that cygwin-1.7.1 has been officially released, this
ncurses package is available exclusively for cygwin-1.7.


MAINTAINERS:
You must now specify explicitly -I/usr/include/ncurses when compiling
against ncurses. The package no longer provides in the top /usr/include
directory symlinks to the header files in /usr/include/ncurses. This is
for compatibility/interop with the wide ncurses library.

cygwin-1.7 now supports UTF-8 encoding by default. It is expected that
the "wide char" version of ncurses, ncursesw, will be of increasing
utility for clients as time goes on. Maintainers, I recommend that you
first attempt to rebuild your applications against libncursesw, and only
use libncurses if it doesn't work, and you can't figure out how to fix
it right away.  See ncursesw.README for more information.


CHANGES since 5.7-16

o Update to 20091227 patchset
o compile with reentrancy and various other ABI-breaking changes (also
  don't use broken-linker). Now at ncurses API #6 (that is, cygwin
  ncurses ABI #10).
o Fix hint files
o Remove symlinks in /usr/include/ to /usr/include/ncurses/*
o Because the API changes (upstream "ABI 5" vs "ABI 6") are handled
  transparently by macros, we assist clients that explicitly search
  for ncurses5-config by providing it as a symlink to ncurses6-config.
  (Suggestion by Yaakov Selkowitz)
o Add symlinks in /usr/lib/ncurses/ to the import, static, and
  libtool libs in /usr/lib/.  Also symlink pkgconfig.

Charles Wilson
volunteer ncurses[w] maintainer for cygwin



To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is
available starting at this URL.


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

[ANNOUNCEMENT] Updated: tack-1.07-1

[Charles Wilson]

The tack program is a diagnostic that is designed to create and verify
the correctness of terminfo entries.  This program can be used to create
new terminal descriptions that are not included in the standard terminfo
database.

[[ compiled using gcc-4.3.4-3 ]]

As expected now that cygwin-1.7.1 has been officially released, this
tack package is available exclusively for cygwin-1.7.

CHANGES (since 1.06-12)

o Routine update to latest upstream release
o Rebuilt against ncursesw-5.7-18 (and libncursesw10)

-- 
Charles Wilson
volunteer tack maintainer for cygwin



To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is
available starting at this URL.


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

[ANNOUNCEMENT] New: Updated: {ncursesw/libncursesw10/libncursesw-devel/ncursesw-demo}-5.7-18

[Charles Wilson]

ncurses is a package that provides character and terminal handling
libraries, including 'gui-like' panels and menus.  It is often used
instead of termcap. ncursesw provides a version of this library and
related tools compiled to support wide characters (that is, wchar_t
rather than char).

Note that ncursesw does NOT contain man pages for the applications;
they are provided by the ncurses package under the 'narrow' names (e.g.
'man clear' for clearw.exe). Similarly, the libncursesw-devel package
does NOT contain man pages about the API; these are provided by the
'narrow' libncurses-devel package.

This is the first official release of ncurses compiled to support
wide characters, and can be installed simultaineously with the "narrow"
ncurses package(s). Like recent (narrow) ncurses packages, it is
compiled with support for reentrancy, and uses the same ABI number
("10" on cygwin for historical reasons; "ABI 6" according to the
upstream ncurses developers). ncurses is not compiled with full
multi-thread support, as that slows operation drastically (see below).

Note that this "reentrancy" support doesn't magically make your client
programs/libraries re-entrant. Internal to libncurses, all calls carry
a specific context variable.  However, the POSIX curses interface
still specifies calls that operate on the "current screen" -- an
obvious re-entrancy violation. Clients must instead use the non-POSIX
extensions provided by ncurses, to ensure that all curses operations are
actually re-entrant. That is:
  POSIX:  int addch(const chtype ch);
  REENTRANT:  int waddch(WINDOW *win, const chtype ch);
Naturally, if reentrancy is not a concern, the POSIX interface can
continue to be used as always. See the man pages for more information.

Clients can be made threadsafe, by universally using the reentrant
interfaces, and managing mutexes on the WINDOW* variables manually. If
ncurses were compiled with full thread support, the WINDOW object would
itself contain a mutex, and all ncurses calls would use it to manage
access. This slows ncurses to a crawl -- even in single-thread
applications. Therefore, I believe the better choice is to compile ncurses
with support for re-entrancy, so that multi-thread client apps that
actually NEED thread safety can use it, and make intelligent decisions
about where they need to incur the mutex locking overhead.


[[ compiled using gcc-4.3.4-3 ]]

As expected now that cygwin-1.7.1 has been officially released, this
ncursesw package is available exclusively for cygwin-1.7.

MAINTAINERS:
To use the wide version of ncurses, you must specify explicitly
-I/usr/include/ncursesw and -L/usr/include/libncursesw when compiling
and linking. See /usr/share/doc/Cygwin/ncursesw.README for more
information on how libncursesw-devel can assist you in arranging that
these flags are properly passed to your clients.

cygwin-1.7 now supports UTF-8 encoding by default. It is expected that
the "wide char" version of ncurses, ncursesw, will be of increasing
utility for clients as time goes on. Maintainers, I recommend that you
first attempt to rebuild your applications against libncursesw, and only
use libncurses if it doesn't work, and you can't figure out how to fix
it right away.  See ncursesw.README for more information.


Charles Wilson
volunteer ncurses[w] maintainer for cygwin



To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is
available starting at this URL.


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

UPDATE on [1.7.1 hangs on 000-cygwin-post-install.sh]

[Rosario D. Contarino]

Hi all,

I've been moving on this issue, which still remains unresolved, and I
would like to share with you all few improvements I think could help on
better focus where the problem could be.

Still there is no way to let the "setup.exe" complete properly its run
and it always ends on the last part, while running the 000-postinstall
and on the log file a bash error "couldn't allocate" appears.

(all details on this can be found in my previous message, just as a
summary, I'm trying to install 1.7.1 on Windows XP Sp3).

Well, apart form checking all the possible devices or software which
could have eventually interfered without success, I simply ended the
setup.exe process which was still stuck at that point, by pressing the
cancel button.

The installation process ends before executing all the scripts contained
into the /etc/postinstall

I simply open a bash shell, I execute them manually in alphabetic order
and none of them ends with any error.

Still, the previous bash.exe process which hanged during the standard
setup with the above mentioned error, is still alive and I kill it with
the Windows Task Manager.

At this point a first question:

1) Is it enough to run the shell scripts included into /etc/postinstall
   to properly complete their package installation or there should be
   something else to do which is normally done by the setup.exe
   process?

Afterwards I was trying to execute again the "setup.exe" to add new
packages (vim).

Again the setup proces goes well till exactly the same point where he
tries to execute the vim.sh under /etc/postinstall and again it hangs
with the same bash error. I terminate the setup by clicking on cancel
button, I run manually the vim.sh and I kill the bash.exe process with
the Windows Task Manager.

Obviously, invocating bash.exe within the setup.exe process leads to its
failure in this specific environment.

Hope this will help to fix it.

Any feedback will be greatly appreciated.

All the best
Dario



--
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: 1.7.1: Does 'chere' work with Vista 64b? Can't tell by me.

[Dave]

Lee D. Rothstein wrote:
> Dave wrote:
> 
>  > So chere has managed to set the keys, and read them back fine. What
>  > happens when you run the following command in cmd (all one line)?
> 
>  > C:\_0\bin\mintty.exe --icon=c:\_0\cygicons-hippo-vista-0.dll,10 - -e
>  > /bin/xhere /bin/bash.exe "c:\Program Files"
> 
> I think 'mintty'/'bash' window flashes open and closed. Menu item
> for Cygwin remanined cygwin_bash. Command doesn't work in exactly
> the same way as before.
> 
>  >> If you're out of ideas, might you give me some clues to look for
>  >> bad keys in the registry?
> 
>  > Check HKEY_CLASSES_ROOT\Directory\Shell\cygwin_bash. It's value should
>  > be the context menu item text, "Mintty Bash"
> 
> Value was null.
> 
>  > It should have one subkey, command, whose value is the command to run
>  > "c:\_0\bin\mintty ...".
> 
> Value was null.

Either registry virtualisation, or redirection is interfering.




My guess is the latter. This is consistent with Larrys' report of chere
working on 64 bit Windows 7, as Microsoft states HKLM/SOFTWARE/Classes
is shared on W7 and redirected+reflected on vista, server 2003, server
2008, xp. 

I'm not on windows right now, but does regtool have the ability to
control redirection/reflection or whether it writes to the 32/64 bit
version of the key? That's what chere would need to operate correctly.
Otherwise it needs to resort to outputting a .reg file and installing it.

> However, your registry key comments were helpful.  Okay, now
> we're gettin' somewhere. Where? You tell me.
> 
> When I 'regedit'ed the registry with what you specified in the
> above paragraphs, using "Mintty_Bash" &:
> 
>   C:\_0\bin\mintty.exe --icon=c:\_0\cygicons-hippo-vista-0.dll,10 -
> 
> the 'mintty'/'bash' window opens, but not to the folder indicated.


Did you include the '-e /bin/xhere /bin/bash "%L"'? That's the bit that
selects the folder.

Dave.

--
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: Building core cygwin packages which only come with patch files over gnu.org packages

[Yaakov (Cygwin/X)]

On 03/01/2010 00:53, neil.mowb...@calgacus.com wrote:

Okay, so I get the general idea.  First you get the cygwin-src package.
Unpack it and
run cygport on the coreutils-7.0-2.cygport file with download option.


If you are rebuilding an existing source package, you don't need to 
download it again, the sources are already there.



This downloads the original gnu package and applies the two patch files.
coreutils-7.0-2.src.patch and coreutils-7.0-2.cygwin.patch.

> I assume the second patch is for cygwin specific files that

aren't present in the orginal gnu package -- is this correct?


Correct.  There may be other patches as well, if PATCH_URI is defined.


Yaakov

--
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: Building core cygwin packages which only come with patch files over gnu.org packages

[Marco Atzeri]

--- Dom 3/1/10, Neil.Mowbray ha scritto:
> By the way, when I try to build it
> says Automake 1.10a is required.
> However, this version isn't
> an option under cygwin, only 1.10.3, 1.10.2, etc.  How
> do I fixed this, hack
> configure.ac?
> 

$ cygcheck -c -d |grep automake
automake   4-10
automake1.10   1.10.3-1
automake1.11   1.11.1-1
automake1.41.4p6-10
automake1.51.5-10
automake1.61.6.3-11
automake1.71.7.9-10
automake1.81.8.5-10
automake1.91.9.6-10


I guess automake 1.11 is what you need.

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