[ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Yaakov (Cygwin/X)]

I have released a new version of cygport for cygwin-1.7.

New features:

* SRC_URI accepts .tar.xz archives.
* LDFLAGS defaults to "-Wl,--enable-auto-import" (prev. empty).
Note: This is a temporary change until a new binutils release is made 
which will do this by default.

* MAKEOPTS defaults to "-j[number_of_cores + 1]" (prev. -j2).
* Automatically creates manifests for programs whose names trigger UAC.
* Files in /var/games are automatically handled with /etc/defaults.
* cygpatch: Reversed patches generate a warning instead of failing.
* kde3.cygclass: Avoid -fvisibility with gcc4 (invalid for PE/COFF).
* kde4.cygclass: Ditto. Updated for KDE4.2 and Qt4.5.
* wxwidgets.cygclass: Default to Unicode builds. Removed MSW support.
* cygport-bash-completion: Now ships with cygport.

Bug fixes:

* Improved gettext handling with libtool2.
* cygpatch: Fixed .cygwin.patch application with deep SRC_DIR.
* make_etc_defaults: Makes sure target directory exists before copying.
* gtk2-perl.cygclass: Build fixes for perl-Cairo.


Yaakov


CYGWIN-ANNOUNCE UNSUBSCRIBE INFO


If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then 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.


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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Corinna Vinschen]

On Jun  6 10:49, Corinna Vinschen wrote:
> On Jun  6 01:15, Dave Korn wrote:
> > Corinna Vinschen wrote:
> > 
> > > Not good.  I'm puzzled where this allocated 68K region is exactly coming
> > > from, but it really looks like something which occurs in or near dlopen.
> > > 
> > > I'm going to debug this further tomorrow.  I guess that goes without
> > > saying, but I'd be glad for any help.
> > 
> >   I'll just suggest that these problems can often be debugged more easily in
> > windbg than gdb, what with gflags/appverifier heap tracking, !vad, !heap, 
> > and
> > related commands.  The gflags FLG_HEAP_ENABLE_TAG_BY_DLL might come in 
> > handy here.
> 
> Right.  You might have noticed in my mail that I refer to WinDbg
> already.  It has a couple of invaluable helpers.  !vprot is one of my
> favorites, as well as the many available display formats in the memory
> window.
> 
> This morning I woke up and suddenly knew what's going on.  It's the size
> of a structure, which had a size of 320 bytes before.  Now it has a size
> of 65596 bytes since the filename stored in it is now a potentially 32K
> long wide character string.  The structure must be shrinked again.  I
> guess I have a patch by tonight.

Done.  The per-DLL structure is used to keep track of certain aspects of
each DLL linked at the executable or loaded at runtime.  In the latter
case, the post-fork procedure re-loads the DLL into the child.

The structure is allocated right after the space occupied by the DLL
itself, using VirtualAlloc.  I changed the struct layout so that the
size depends on the length of the pathname to the DLL.  In most, if not
all cases this will fit into a single 4K page.

The one problem with VirtualAlloc is the fact that it only allocates
memory on a 64K boundary.  So the DLL struct will be allocated exactly
in the next DLL slot in memory, wasting one place where a DLL can be
loaded.  However, in most cases the DLL itself will not occupy the
entire 64K slot, but one or more 4K pages are left free, which will
never be used while the application is running.

So I applied another patch this morning, which allocates a section
object (file mapping in Win32 speak) instead.  The NT kernel specifc
AT_ROUND_TO_PAGE flag allows to allocate section objects on 4K page
boundaries, rather than only on 64K allocation boundaries.  This allows
to allocate the DLL struct right after the DLL, in a memory slot which
will never collide with any further allocation or DLL.

The only downside is that the AT_ROUND_TO_PAGE flag is not supported by
WOW64, so the DLL struct will still be allocated on 64K boundaries on
64 bit Windows.

I tested this change on XP 32 bit, 2K8 32 bit, W7 32 bit, and W7 64 bit,
by running `cygport automake1.11 compile' and a subsequent `make check',
which uses perl (and thus run-time loaded DLLs) a lot.


HTH,
Corinna

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

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

Re: Problems with gmp and mpfr after rebasing - was Re: [ANNOUNCEMENT] gmp-4.3.1-1 for cygwin-1.7

[Marc Girod]

David Billinghurst wrote:
> 
> The new builds are available for testing.  You really only need the new 
> DLLs.  These are in
>   - libgmp3-4.3.1-3.tar.bz2,
>   - libgmpxx4-4.3.1-3.tar.bz2
>   - libmpfr1-2.4.1-3.tar.bz2
> 
I could once again download them with wget,
but not find them from any mirro.
This time the extraction worked.
I'll test them soon now...
Marc
-- 
View this message in context: 
http://www.nabble.com/-ANNOUNCEMENT--gmp-4.3.1-1-for-cygwin-1.7-tp23690044p23908840.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Problems with gmp and mpfr after rebasing - was Re: [ANNOUNCEMENT] gmp-4.3.1-1 for cygwin-1.7

[Marc Girod]

Marc Girod wrote:
> 
> I'll test them soon now...
> 
Installed, rebased, and yes!
At least expr works now!
Thanks,
Marc
-- 
View this message in context: 
http://www.nabble.com/-ANNOUNCEMENT--gmp-4.3.1-1-for-cygwin-1.7-tp23690044p23908982.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

fcntl (locking) bug?

[Margit Schubert-While]

This is 1.5.25 but also happens on earlier versions.
It would appear that placing a shared read lock
on a file open for input/output is preventing the
the process itself from writing.
Consider -

#include 
#include 
#include 
#include 
#include 
#include 
#include 
int
main ()
{
int fd;
struct flocklock;

errno = 0;
fd = open ("TESTFILE", O_CREAT | O_TRUNC | O_WRONLY, 0777);
printf("Open for write - Errno %d\n", errno);
if (fd >= 0) {
errno = 0;
if (write (fd, "TESTtest", 8) != 8) {
printf ("Write error - %d\n", errno);
close (fd);
return 1;
}
errno = 0;
close (fd);
printf("Close after write - Errno %d\n", errno);
}
fd = open ("TESTFILE", O_RDWR, 0);
printf("Open for I/O - Errno %d\n", errno);
if (fd < 0) {
return 1;
}
memset (&lock, 0, sizeof (struct flock));
lock.l_type = F_RDLCK;
lock.l_whence = SEEK_SET;
lock.l_start = 0;
lock.l_len = 0;
errno = 0;
if (fcntl (fd, F_SETLK, &lock) < 0) {
printf ("Lock error - %d\n", errno);
close (fd);
return 1;
}
errno = 0;
if (write (fd, "test", 4) != 4) {
printf ("Write I/O error - %d\n", errno);
}
memset (&lock, 0, sizeof (struct flock));
lock.l_type = F_UNLCK;
lock.l_whence = SEEK_SET;
lock.l_start = 0;
lock.l_len = 0;
errno = 0;
if (fcntl (fd, F_SETLK, &lock) < 0) {
printf ("Unlock error - %d\n", errno);
close (fd);
return 1;
}
close (fd);
return 0;
}

This always prodcues -
Write I/O error - 13
ie. EACCES

Margit


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

Re: Trying to install CPAN Math::GMP. Can libgmp3 provide -libgmp?

[Marc Girod]

Marc Girod wrote:
> 
> Thanks, because my own (naive) attempt failed on the configure stage,
> because of expr dumping core.
> 
Thanks to the fixes to libgmp-3 by Bill, expr works for me now,
and I could successfully build and install libssh2-1.1 from the sources.
Marc
-- 
View this message in context: 
http://www.nabble.com/Re%3A-Re%3A-Trying-to-install-CPAN-Math%3A%3AGMP.-Can-libgmp3-provide--libgmp--tp23850368p23909246.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Trying to install CPAN Math::GMP. Can libgmp3 provide -libgmp?

[Marc Girod]

Marc Girod wrote:
> 
> Thanks to the fixes to libgmp-3 by Bill[...]
> 
I meant David! Sorry.
-- 
View this message in context: 
http://www.nabble.com/Re%3A-Re%3A-Trying-to-install-CPAN-Math%3A%3AGMP.-Can-libgmp3-provide--libgmp--tp23850368p23909269.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: LFTP issue

[Andrew Schulman]

> According to the LFTP documentation, I should be able to do:
> 
> ls | grep 
> 
> and
> 
> ls | less
> 
> both of which only return something if I , if I don't 
> it just sits there.
> 
> I don't have access to a Linux machine, so I can't verify if this is a
> cygwin lftp issue, or an lftp issue in general.

Thanks for the report.  I just tried this on my linux host and it works fine
there.  I don't have a Cygwin host here but will check the behavior you report
on Monday.

Unfortunately, I don't have any idea what would make this happen in Cygwin and
not in Linux.  For the Cygwin package I just compile the upstream source, with
no changes.  Best chance would be to report this problem upstream:  see
http://lftp.yar.ru/list.html, or gmane.network.lftp.user.

Are you running Cygwin 1.5, or 1.7?  Upgrading to 1.7 would be worth a try if
you haven't yet.

BTW, lftp is currently stuck at version 3.7.6 in Cygwin, because I can't get any
later versions to run there-- they all segfault at start.  I've been meaning to
report this problem upstream, too.  So obviously there are some Cygwin problems
with lftp right now.

Andrew.


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

cygwin multi window and copy paste issues

[samitj]

Hello,
I upgraded my cygwin packages to latest versions and unfortunately I did not
back up previous versions and now nothing is working. I was hoping the new
packages are atleast stable before they are released to the public. 

I used to be able to get multiple xterm window view using 'startx' but now
either it keeps crashing or gives a bad single window interface. 

The copy paste (using mouse middle button) is no longer working between
windows applications and xterm. This used to work.

Can you tell me what I need to do to revert to a stable version which gives
me the simple and stable features as before?

thank you,

Sam
-- 
View this message in context: 
http://www.nabble.com/cygwin-multi-window-and-copy-paste-issues-tp23909700p23909700.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: fcntl (locking) bug?

[Corinna Vinschen]

On Jun  7 11:15, Margit Schubert-While wrote:
> This is 1.5.25 but also happens on earlier versions.
> It would appear that placing a shared read lock
> on a file open for input/output is preventing the
> the process itself from writing.

Cygwin up to release 1.5.25 implements fcntl locks using Windows file
locking calls.  Windows semantics disallow write access to a shared lock
for all processes, even the one setting up the first lock.  Only an
exclusive lock allows the locking process to write.

This is supposed to be fixed in Cygwin 1.7 which will use an entire
different mechanism to implement POSIX locks.


Corinna

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

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

Re: LFTP issue

[Chris Sutcliffe]

> Thanks for the report.  I just tried this on my linux host and it works fine
> there.  I don't have a Cygwin host here but will check the behavior you report
> on Monday.

Good to know it works properly in linux.

> Unfortunately, I don't have any idea what would make this happen in Cygwin and
> not in Linux.  For the Cygwin package I just compile the upstream source, with
> no changes.  Best chance would be to report this problem upstream:  see
> http://lftp.yar.ru/list.html, or gmane.network.lftp.user.

Will do.

> Are you running Cygwin 1.5, or 1.7?  Upgrading to 1.7 would be worth a try if
> you haven't yet.

I'm running 1.7.

> BTW, lftp is currently stuck at version 3.7.6 in Cygwin, because I can't get 
> any
> later versions to run there-- they all segfault at start.  I've been meaning 
> to
> report this problem upstream, too.  So obviously there are some Cygwin 
> problems
> with lftp right now.

I compiled 3.7.14 (the latest as of this email) with no issue and it
runs fine, unfortunately it exhibits the same behaviour.

Cheers!

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org

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

Re: cygwin multi window and copy paste issues

[samitj]

someone please help me. I want to go back to the version which did this and
worked fine. I have a lot of production stuff dependent on this and nothing
is working from my new version. All I wanted to do was to install rsync and
ended up reinstalling all this crap and now in a big mess. Can someone
please tell me what I need to do in order to revert to the below version ??



$ startx

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4

Contact: cygwin-xf...@cygwin.com

XWin was started with the following command line:

X :0 -multiwindow -clipboard

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0007
winSetEngine - Multi Window or Rootless => ShadowGDI
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per
pixel
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 800 depth: 32
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp
32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
-- 
View this message in context: 
http://www.nabble.com/cygwin-multi-window-and-copy-paste-issues-tp23909700p23909962.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Ken Brown]

On 6/7/2009 4:23 AM, Corinna Vinschen wrote:

I tested this change on XP 32 bit, 2K8 32 bit, W7 32 bit, and W7 64 bit,
by running `cygport automake1.11 compile' and a subsequent `make check',
which uses perl (and thus run-time loaded DLLs) a lot.


I don't have the expertise to follow this thread in detail, but I have 
one question from the user's point of view.  Are your patches strictly 
designed to solve problems in Vista and later, or might they have a 
(positive) impact under XP?


I'm asking because I run XP and have occasionally had mysterious cygwin 
problems (for instance I wasn't able to build emacs 22.3 using cygport 
because the build kept hanging when many subprocesses were called).  And 
I recall at least two other users (Steffen Sledz and Angelo Graziosi) 
who have reported problems that seemed to resemble BLODA but that 
couldn't be tracked down.  I don't think they were running Vista, but 
I'm not sure.


Ken

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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Corinna Vinschen]

On Jun  7 07:37, Ken Brown wrote:
> On 6/7/2009 4:23 AM, Corinna Vinschen wrote:
>> I tested this change on XP 32 bit, 2K8 32 bit, W7 32 bit, and W7 64 bit,
>> by running `cygport automake1.11 compile' and a subsequent `make check',
>> which uses perl (and thus run-time loaded DLLs) a lot.
>
> I don't have the expertise to follow this thread in detail, but I have  
> one question from the user's point of view.  Are your patches strictly  
> designed to solve problems in Vista and later, or might they have a  
> (positive) impact under XP?

They are designed to fix a generic problem introduced in 1.7 due to the
long pathname support, not a Vista-only problem.  It was a coincidence
that the guys involved in the discussion of that issue were running
Vista/W7.

The only difference of Vista/W7 to earlier system is the additional ASLR
feature which could help to plaster over the issue in a non-reproducible
way.  */me ducks to escape Chucks slap*


Corinna

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

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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Charles Wilson]

Yaakov (Cygwin/X) wrote:

> * Improved gettext handling with libtool2.

Does this require the (not-yet-officially-released) gettext-0.17-11
package, or does it work correctly with the current gettext-0.17-10?

--
Chuck

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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Charles Wilson]

Corinna Vinschen wrote:
> The only difference of Vista/W7 to earlier system is the additional ASLR
> feature which could help to plaster over the issue in a non-reproducible
> way.  */me ducks to escape Chucks slap*

No slap from me. Your analysis shows conclusively that ASLR is and
always was a red herring.  "For every complex problem, there is a
solution that is simple, neat, and wrong." (H.L.Mencken)

I'm now really glad that the peflagsall functionality was kept separate,
and not made an automatic part of rebaseall.

--
Chuck

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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Charles Wilson]

Corinna Vinschen wrote:
> The structure is allocated right after the space occupied by the DLL
> itself, using VirtualAlloc.  I changed the struct layout so that the
> size depends on the length of the pathname to the DLL.  In most, if not
> all cases this will fit into a single 4K page.
...
> However, in most cases the DLL itself will not occupy the
> entire 64K slot, but one or more 4K pages are left free, which will
> never be used while the application is running.

So, while the following are probably not practical concerns, there are
still a few failure modes, correct?

1) if the ImageSize of the DLL is between N*64k-4k+1 and N*64k, the next
4k page allocated for the struct will again clobber the next DLL's ImageBase

2) if the length of the actual pathname to the DLL is more than 2k wide
characters (e.g. 4k bytes) then issue #1 is made increasingly likely,
because the "dangerous DLL size" becomes N*64k-M*4k+1 .. N*64k, with
1 I tested this change on XP 32 bit, 2K8 32 bit, W7 32 bit, and W7 64 bit,
> by running `cygport automake1.11 compile' and a subsequent `make check',
> which uses perl (and thus run-time loaded DLLs) a lot.

Hallelujah!

--
Chuck

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

fcntl (locking) bug?

[Margit Schubert-While]

>> This is 1.5.25 but also happens on earlier versions.
>> It would appear that placing a shared read lock
>> on a file open for input/output is preventing the
>> the process itself from writing.

Corinna scribeth :
> Cygwin up to release 1.5.25 implements fcntl locks using Windows file
> locking calls.  Windows semantics disallow write access to a shared lock
> for all processes, even the one setting up the first lock.  Only an
> exclusive lock allows the locking process to write.

Hmm. Unfortunate and not intuitive. Hmm - fcntl is in the
Cygwin SUSV3 compat list 
-http://cygwin.com/cygwin-api/compatibility.html#std-susv3  ?

SUSV3 mandates this functionality.
Maybe an addendum somewhere or an entry
in http://cygwin.com/cygwin-api/std-notes.html ?

Margit 



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

Re: cygwin multi window and copy paste issues

[Jon TURNEY]

samitj wrote:


I used to be able to get multiple xterm window view using 'startx' but now
either it keeps crashing or gives a bad single window interface. 


The copy paste (using mouse middle button) is no longer working between
windows applications and xterm. This used to work.


1) Change the defaultserver args line in /usr/bin/startx as described in this 
post http://cygwin.com/ml/cygwin-xfree/2009-05/msg00039.html


> Can you tell me what I need to do to revert to a stable version which gives
> me the simple and stable features as before?

2) Post X related questions to the cygwin-xfree list

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

doc about the cygwin vfs?

[jean-luc malet]

I would like to see if I can implement a fuse extention in cygwin vfs...
where can I find usefull hints about the cygwin vfs system?
thanks
JLM

-- 
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Andy Koppe]

> 2) if the length of the actual pathname to the DLL is more than 2k wide
> characters (e.g. 4k bytes) then issue #1 is made increasingly likely,

Surely anyone with paths like that deserves all the pain that comes
their way. 2k characters means 85 levels of "Documents and Settings".
:)

Andy

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

Re: cygwin multi window and copy paste issues

[samitj]

I keep getting this error:
sj...@dksjdksj~
$ startx
xauth:  creating new authority file /cygdrive/c/Documents and
Settings/samitj/.se
rverauth.8172

giving up.
xinit:  Connection refused (errno 111):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

NOw if I start using this command:
X :0 -multiwindow -clipboard

I get the multiple windows.

I dont get the copy paste between windows and unix applications. How do I
enable this?

Also, how do I disable the menu at the top of the xterm?

Why is it crashing so often now?

Has anyone tried Exceed is it more stable than this? I wish I never tried to
upgrade to current version. I lost everything now..



Jon TURNEY wrote:
> 
> samitj wrote:
>> 
>> I used to be able to get multiple xterm window view using 'startx' but
>> now
>> either it keeps crashing or gives a bad single window interface. 
>> 
>> The copy paste (using mouse middle button) is no longer working between
>> windows applications and xterm. This used to work.
> 
> 1) Change the defaultserver args line in /usr/bin/startx as described in
> this 
> post http://cygwin.com/ml/cygwin-xfree/2009-05/msg00039.html
> 
>  > Can you tell me what I need to do to revert to a stable version which
> gives
>  > me the simple and stable features as before?
> 
> 2) Post X related questions to the cygwin-xfree list
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/cygwin-multi-window-and-copy-paste-issues-tp23909700p23911804.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: OpenSSH server installation error on Windows Vista Business/Ultimate

[Paul August]

David,

I am still having trouble to set up OpenSSH server. Following the
suggestions below, I run mmc.exe to make sure the Administrator account
is enabled. Then I logon the Administrator account and from there I
reinstalled cygwin from scratch. However, when I run ssh-host-config -y
again, I still got the same error message.

The machine I tried above is a laptop running Windows Vista Business
32bit.

Any more clues?
Paul.



David Christensen wrote:
> Paul August wrote:
> 
>> *** Warning: The file /etc/passwd is not readable by all.
>> *** Warning: Please run 'chmod +r /etc/passwd'.
>> *** Warning: The file /etc/group is not readable by all.
>> *** Warning: Please run 'chmod +r /etc/group'.
>> *** ERROR: Problem with LocalSystem or Adminstrator IDs
>> Does anyone have a clue how to deal with this problem? Is there
>> anybody who successfully installed OpenSSH server on their Vista
>> Business/Ultimate PCs?
> 
> I just built a machine using a Windows Vista Ultimate with SP1 32-bit
> OEM DVD this weekend.  Once Vista was installed and activated, I
> discovered that the Administrator account was disabled by default.  I
> did some work using the administrator-level account I created during
> installation, but I didn't like this approach -- I wanted the real
> Administrator account.  So, I STFW and enabled it using the Local Users
> and Groups MMC console:
> 
> http://technet.microsoft.com/en-us/library/cc766343.aspx
> 
> I finished up with the real Administrator account, including installing
> Cygwin and sshd.  I made the changes noted above plus another (/var?),
> and had the script create an account to run sshd.  sshd works.
> 
> 
> HTH,
> 
> David
> 
> 


  

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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Charles Wilson]

Andy Koppe wrote:
>> 2) if the length of the actual pathname to the DLL is more than 2k wide
>> characters (e.g. 4k bytes) then issue #1 is made increasingly likely,
> 
> Surely anyone with paths like that deserves all the pain that comes
> their way. 2k characters means 85 levels of "Documents and Settings".

No one will ever need more than 640k of RAM (W. Gates).

--
Chuck

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

Re: cygwin multi window and copy paste issues

[Andrew DeFaria]

samitj wrote:

I keep getting this error:
sj...@dksjdksj~
$ startx
xauth: creating new authority file /cygdrive/c/Documents and
Settings/samitj/.se
rverauth.8172

giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.

NOw if I start using this command:
X :0 -multiwindow -clipboard

I get the multiple windows.

I dont get the copy paste between windows and unix applications. How do I
enable this?

Also, how do I disable the menu at the top of the xterm?

Why is it crashing so often now?

Has anyone tried Exceed is it more stable than this? I wish I never 
tried to

upgrade to current version. I lost everything now..
As was pointed out to you, you'll get better responses if you post to 
the cygwin-xfree list.


Meantime, if all you are doing is multiple ASCII terminals and wish to 
paste text between them and Windows applications then you can use rxvt, 
which does not require a heavy X server process.

--
Andrew DeFaria 
Imagination is more important than knowledge. - Albert Einstein


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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Yaakov (Cygwin/X)]

On 07/06/2009 07:08, Charles Wilson wrote:

Does this require the (not-yet-officially-released) gettext-0.17-11
package, or does it work correctly with the current gettext-0.17-10?


It does use autopoint -V, if that's what you're asking, which was what I 
meant with my earlier message:


http://cygwin.com/ml/cygwin/2009-06/msg00189.html

I didn't realize that you hadn't pushed it yet; my apologies.


Yaakov

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

[ANNOUNCEMENT] Updated: mintty-0.4.0-1

[Andy Koppe]

MinTTY is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
MinTTY is based on code from PuTTY 0.60 by Simon Tatham and team.

This is a feature release. Thanks to everyone who tried the betas and
release candidates. Special thanks to Thomas Wolff, the author of the
Unicode editor mined (http://towo.net/mined), who did a lot of testing
and provided plenty of bug reports and suggestions for improvements.

CHANGES
===

Incompatible change:
- The control sequences sent by the mousewheel outside application
mouse mode have changed. The previous scheme that tied the encoding to
the "modifier for scrolling with cursor keys" was a bad idea, because
it meant that the configuration of any program using it had to change
depending on that setting. The following lines in ~/.lesskey are now
needed for mousewheel support in less. (Remember to run the lesskey
command after editing .lesskey)

\eOa back-line
\eOb forw-line
\e[1;2a back-screen
\e[1;2b forw-screen

User interface changes:
- The options dialog gained an Apply button and no longer blocks
terminal output. Options have been rearranged, hopefully for the
better.
- The row and column settings in the options now control the default
size only, to avoid accidentally saving the current size.
- Added a context menu command and the shortcut Alt+F10 for returning
the terminal to its defaults size.
- The official shortcut for the fullscreen mode now is Alt+F11.
Alt+Enter continues to work, but might eventually be removed or used
for something else.
- The font size can be changed with Ctrl+plus, Ctrl+minus, or
Ctrl+Mousewheel. Ctrl+zero goes back to the configured font size.
- The command line cursor can be placed by clicking with the mouse, if
the "Clicks place cursor" on the Mouse page of the options is enabled.
This works by sending cursor key codes, but there are a few rough
edges. In particular, when clicking on a command line that does not
actually allow cursor movement, the cursor key codes are treated as
input.
- The command to run can now be set using the SHELL environment variable.
- New --log command line option enables logging of terminal output to a file.
- New --hold command line option controls whether to keep the window
open after the command running in MinTTY has exited. This can be set
to 'always', 'never', or 'error'. The default is 'never'; and 'error'
enables the 0.3 behaviour.
- PuTTY's option for setting the maximum number of lines in the
scrollback buffer is back. (Previously that was fixed to 65535.)
- The exit confirmation dialog when there are child processes can be disabled.
- A utmp entry is created only if requested using the new --utmp
option. (This is because utmp logging seems to often hang for about
half a minute on Windows 7, for whatever reason.)
- Decreasing the window size once again crops lines, because the
attempted fix for this turned out to have a bug.
- As is standard on Windows, AltGr now is always treated the same as Ctrl+Alt.

Changes to the terminal emulation:
- MinTTY now has its own identity, instead of pretending to be an old
xterm. The ^E answerback string is "mintty", the ^[[c primary device
attribute command reports a vt100, and the ^[[>c secondary DA command
reports terminal type 77 (ASCII 'M') and version 400. The TERM
variable remains set to "xterm", to avoid termcap/terminfo trouble.
- Applications can get the whole numpad to send "application keypad
mode" sequences by enabling "DECKPAM" and disabling "DECCKM". This
diverges from xterm's behaviour in its default "PC-style function key"
setting, but allows applications to tell numpad keys apart from their
equivalents on the small keypads.
- The (non-standard) keycodes for Ctrl combinations with digit and
number keys have changed. They remain based on application keypad
codes, but they now follow xterm's pattern for encoding modifier keys,
e.g. Ctrl+1 is sent as "^[[1;5q".
- Xterm's "modifyOtherKeys" mode for encoding key combinations without
standard keycodes is now supported, whereby the 'CSI u' format enabled
by setting the "formatOtherKeys" resource to 1 in xterm is used.
- The vt100 line drawing character set and the SCO/VGA graphical
character set are now supported in Unicode mode.
- xterm OSC sequences for changing text, cursor and other colours are supported.
- A SIGWINCH signal is sent when a font with a different "CJK
Ambiguous Width" is selected, so that applications can adjust their
output accordingly.
- The Windows keyboard layout is no longer consulted for Ctrl(+Shift)
combinations, because non-English layouts often have control
characters in unintuitive places. For example, on the German keyboard
the ^^ character can now be obtained by pressing Ctrl+^ instead of
Ctrl+Shift+6.

More on these changes can be found at
http://code.google.com/p/mintty/is

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Christopher Faylor]

On Sun, Jun 07, 2009 at 10:23:08AM +0200, Corinna Vinschen wrote:
>The structure is allocated right after the space occupied by the DLL
>itself, using VirtualAlloc.  I changed the struct layout so that the
>size depends on the length of the pathname to the DLL.  In most, if not
>all cases this will fit into a single 4K page.

It doesn't have to be that way if this is causing problems.  Maybe it
would make sense to store these things in the cygheap now since I think
the allocation-next-to-the-dll predates the cygheap.  If that isn't
appropriate then we could also just store the information in some
easily-relocatable block and copy that block to forked processes.

cgf

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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Charles Wilson]

Yaakov (Cygwin/X) wrote:
> On 07/06/2009 07:08, Charles Wilson wrote:
>> Does this require the (not-yet-officially-released) gettext-0.17-11
>> package, or does it work correctly with the current gettext-0.17-10?
> 
> It does use autopoint -V, if that's what you're asking, which was what I
> meant with my earlier message:
> 
> http://cygwin.com/ml/cygwin/2009-06/msg00189.html
> 
> I didn't realize that you hadn't pushed it yet; my apologies.

No problem. I'll upload it now.  gettext-0.17-4 for cygwin-1.5 with a
similar change will follow later.

--
Chuck

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

Re: Trying to install CPAN Math::GMP. Can libgmp3 provide -libgmp?

[Marc Girod]

Reini Urban wrote:
> 
> I successfully ran all Net-SSH-Perl-1.34 tests.
> 
Now I could build Math::GMP, so I did as well.
Same problems with make tests for Math::Pari
Marc
-- 
View this message in context: 
http://www.nabble.com/Re%3A-Re%3A-Trying-to-install-CPAN-Math%3A%3AGMP.-Can-libgmp3-provide--libgmp--tp23850368p23913594.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

[ANNOUNCEMENT] [1.7] Updated: {gettext/gettext-devel/libgettextpo0/libintl8/libasprintf0}-0.17-11

[Charles Wilson]

gettext is the GNU package which provides 'national language support'
for other programs. It includes a number of utility programs.

Feature enhancement. (Required for cygport-0.9.6)

This release is specific for cygwin-1.7.  There is, as yet, no "matching"
release for cygwin-1.5. 

[[ compiled using gcc-3.4.4-999 and g++-3.4.4-999 ]]
This is important to note, because libasprintf0 is a C++ library.
Later updates MAY use g++-4.3. When (if) that happens, there will
be a backwards-incompatibile change to the libasprintf0 DLL, BUT
the dll version number, contrary to typical practice on cygwin, will
NOT be incremented. See this thread for more information:
http://cygwin.com/ml/cygwin-apps/2009-04/msg00034.html

Changes since gettext-0.17-10

* Enable -V option for autopoint (helps work around
  bug with packages that use both libtool and gettext,
  but specify AM_GNU_GETTEXT_VERSION < 0.17. Because
  older gettext had a bug that caused difficulties with
  libtool, the -V option allows to automatically update
  the package to this version of gettext during the auto-
  reconf process, without manually patching the target
  package's configure.in.

-- 
Charles Wilson
volunteer gettext 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.



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

RE: OpenSSH server installation error on Windows Vista Business/Ultimate

[David Christensen]

Paul August wrote:

> David,

Please address your messages to the list.  If you wish to hire me, I
prefer silver and gold U.S. coins.  :-)


> I am still having trouble to set up OpenSSH server. Following the
> suggestions below,

Which suggestions?  Please copy/ paste/ indent/ reformat the text you
wish to comment upon into your message, and then reply immediately below
so we don't have to guess/ infer.


> I run mmc.exe to make sure the Administrator account is enabled. Then
> I logon the Administrator account and from there I reinstalled cygwin
> from scratch.

Please provide more information.  I am unaware of formal Cygwin install
and uninstall mechanisms (e.g. *.msi, Add/Remove Programs, scripts,
etc.), and so follow my own seat-of-the-pants procedures
(http://cygwin.com/ml/cygwin/2009-05/msg00720.html).  Please document
what you did/ do so that it can be repeated/ troubleshot.


> However, when I run ssh-host-config -y

Don't use the -y option.  Automagic is bad when you're troubleshooting
(unless, of course, you're troubleshooting the automagic ;-).


> again, I still got the same error message.

If you mean:

>>> *** Warning: The file /etc/passwd is not readable by all.
>>> *** Warning: Please run 'chmod +r /etc/passwd'.
>>> *** Warning: The file /etc/group is not readable by all.
>>> *** Warning: Please run 'chmod +r /etc/group'.
>>> *** ERROR: Problem with LocalSystem or Adminstrator IDs

The warnings contain the solution (assuming you know Unix; do you know
Unix?).  Start a Cygwin Bash shell and run the commands:

chmod +r /etc/passwd

chmod +r /etc/group

Then, run ssh-host-config again.  You will get one or two more sets of
warnings/ errors with solutions.  Follow the instructions and repeat.  I
recall it taking three or four passes and that Vista took more work than
XP.


> The machine I tried above is a laptop running Windows Vista Business
> 32bit.
> Any more clues?

Please:

1.  Confirm that you have installed Cygwin using the (real Vista)
Administrator account.  Only use this account when administering Cygwin.

2.  Run Cygwin Setup and make sure your installation is up to date.

3.  Run "cygcheck" per http://cygwin.com/problems.html and save
cygcheck.out.

4.  Open a Cygwin Bash shell and attempt to configure the OpenSSH
server.

5.  If you're still stuck, reply to the list (cc myself if you like),
attach cygcheck.out, include your console session (at the end or
attached as a *.txt file), and copy/ paste key lines from the console
session into your message with your thoughts/ comments/ questions.

6.  When you do figure it out, post a summary to the list so that
everyone benefits.  (I am constantly rebuilding my machines with various
flavors of Windows, Linux, BSD, etc., and have run into vaguely familiar
problems only to STFW and find my own solutions posted on the web!)


HTH,

David


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

Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: Cygwin 1.7 release (was ...)]

[Corinna Vinschen]

On Jun  7 08:42, Charles Wilson wrote:
> Corinna Vinschen wrote:
> > The structure is allocated right after the space occupied by the DLL
> > itself, using VirtualAlloc.  I changed the struct layout so that the
> > size depends on the length of the pathname to the DLL.  In most, if not
> > all cases this will fit into a single 4K page.
> ...
> > However, in most cases the DLL itself will not occupy the
> > entire 64K slot, but one or more 4K pages are left free, which will
> > never be used while the application is running.
> 
> So, while the following are probably not practical concerns, there are
> still a few failure modes, correct?
> 
> 1) if the ImageSize of the DLL is between N*64k-4k+1 and N*64k, the next
> 4k page allocated for the struct will again clobber the next DLL's ImageBase

Yes, but that was always the case, even before Cygwin 1.7, since the
method is not exactly new.  The only new property is that the pathname
is stored as wchar_t and that it can have a length of up to 32K.  So far
the next 64K slot was always taken.  Now it's only taken if the DLL
occupies the last page in the 64K slot by itself, or...

> 2) if the length of the actual pathname to the DLL is more than 2k wide
> characters (e.g. 4k bytes) then issue #1 is made increasingly likely,
> because the "dangerous DLL size" becomes N*64k-M*4k+1 .. N*64k, with
> 1 (e.g. M=16, for 64k bytes in the struct) then the new solution devolves
> to the status quo ante.

... the path is very long.

> 3) This new solution can never work properly for WOW64

Right.  However, even without my patch to utilize the trailing pages
in a 64K slot, we're at least back to the "usual" rebase problem.
On 32 bit OSes, it got better now.

Anyway, the discussion is moot since Chris' patch to use cygheap to
store the per-DLL struct seems to work nicely.


Corinna

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

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

Re: fcntl (locking) bug?

[Corinna Vinschen]

On Jun  7 14:45, Margit Schubert-While wrote:
> Corinna scribeth :
> > Cygwin up to release 1.5.25 implements fcntl locks using Windows file
> > locking calls.  Windows semantics disallow write access to a shared lock
> > for all processes, even the one setting up the first lock.  Only an
> > exclusive lock allows the locking process to write.
>
> Hmm. Unfortunate and not intuitive. 

For people used to the Win32 API, it is ;)

>  Hmm - fcntl is in the
> Cygwin SUSV3 compat list  
> -http://cygwin.com/cygwin-api/compatibility.html#std-susv3  ?
> SUSV3 mandates this functionality.
> Maybe an addendum somewhere or an entry
> in http://cygwin.com/cygwin-api/std-notes.html ?

Doesn't matter anyway.  We're heading straight to the 1.7 release
anyway.  It would make more sense if you could give the fcntl locking
mechanism in Cygwin 1.7 a try.


Corinna

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

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

Re: doc about the cygwin vfs?

[Corinna Vinschen]

On Jun  7 16:35, jean-luc malet wrote:
> I would like to see if I can implement a fuse extention in cygwin vfs...
> where can I find usefull hints about the cygwin vfs system?

There's no documentation because there's no vfs.


Corinna

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

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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Yaakov (Cygwin/X)]

On 07/06/2009 12:11, Charles Wilson wrote:

No problem. I'll upload it now.  gettext-0.17-4 for cygwin-1.5 with a
similar change will follow later.


I'm not sure that will be necessary.  cygport is only using autopoint -V 
on cygwin-1.7; I have not backported that fix to the cygwin-1.5 version, 
as the latter is very close to being EOL'd.



Yaakov

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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.6-1

[Charles Wilson]

Yaakov (Cygwin/X) wrote:
> I'm not sure that will be necessary.  cygport is only using autopoint -V
> on cygwin-1.7; I have not backported that fix to the cygwin-1.5 version,
> as the latter is very close to being EOL'd.

Since I plan to keep my packages for 1.5 up to date [*] until 1.7 is
released, it's easier for me to keep them the same...

[*] ESPECIALLY the autotools. Until VERY recently, the whole "failed to
remap" problem has been much much worse (mostly just for ME, apparently)
under pickone(cygwin-1.7|Vista) -- which made autoreconf...tricky.  So
my fallback has been to do the autoreconf step on cyg1.5 when necessary,
which is only possible if both autotoolchains are identical.  This may
soon be a moot point, once Corinna's/cgf's fix for the issue gets in to
cygwin-1.7.0-49 or so.

Until then, I'll be hacking my cygport-0.4.x on cygwin-1.5 to also use
-V for precisely this reason.

--
Chuck

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

[ANNOUNCEMENT] Updated: {aprutil1,libaprutil1,libaprutil1-devel}-1.3.4-3

[David Rothenberger]

A new version the Apache Portable Runtime utilities library is now
available for download.

NEWS:
=
This release addresses two security vulnerabilities by applying
patches from Debian.

"kcope" discovered a flaw in the handling of internal XML entities
in the apr_xml_* interface that can be exploited to use all
available memory. This denial of service can be triggered remotely
in the Apache mod_dav and mod_dav_svn modules. (No CVE id yet)

Matthew Palmer discovered an underflow flaw in the
apr_strmatch_precompile function that can be exploited to cause a
daemon crash. The vulnerability can be triggered (1) remotely in
mod_dav_svn for Apache if the "SVNMasterURI"directive is in use, (2)
remotely in mod_apreq2 for Apache or other applications using
libapreq2, or (3) locally in Apache by a crafted ".htaccess" file.
(CVE-2009-0023)

Other exploit paths in other applications using libaprutil1 may exist.

If you use Apache, or if you use svnserve in standalone mode, you
need to restart the services after you upgraded the libaprutil1
package.

This package includes plugins for ldap, PostgreSQL, and SQLite3. It
is still linked against libdb4.2.

DESCRIPTION:

The mission of the Apache Portable Runtime (APR) project is to
create and maintain software libraries that provide a predictable
and consistent interface to underlying platform-specific
implementations. The primary goal is to provide an API to which
software developers may code and be assured of predictable if not
identical behaviour regardless of the platform on which their
software is built, relieving them of the need to code special-case
conditions to work around or take advantage of platform-specific
deficiencies or features.

DOWNLOAD:
=
Note that downloads from sourceware.org (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.

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://cygwin.com/lists.html

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


-- 
David Rothenberger    daver...@acm.org




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

[ANNOUNCEMENT] [1.7] Updated: {aprutil1,libaprutil1,libaprutil1-devel}-1.3.4-4

[David Rothenberger]

A new version the Apache Portable Runtime utilities library is now
available for download. This version is built for Cygwin 1.7.

NEWS:
=
This release addresses two security vulnerabilities by applying
patches from Debian.

"kcope" discovered a flaw in the handling of internal XML entities
in the apr_xml_* interface that can be exploited to use all
available memory. This denial of service can be triggered remotely
in the Apache mod_dav and mod_dav_svn modules. (No CVE id yet)

Matthew Palmer discovered an underflow flaw in the
apr_strmatch_precompile function that can be exploited to cause a
daemon crash. The vulnerability can be triggered (1) remotely in
mod_dav_svn for Apache if the "SVNMasterURI"directive is in use, (2)
remotely in mod_apreq2 for Apache or other applications using
libapreq2, or (3) locally in Apache by a crafted ".htaccess" file.
(CVE-2009-0023)

Other exploit paths in other applications using libaprutil1 may exist.

If you use Apache, or if you use svnserve in standalone mode, you
need to restart the services after you upgraded the libaprutil1
package.

This package includes plugins for ldap, PostgreSQL, and SQLite3. It
is still linked against libdb4.2.

DESCRIPTION:

The mission of the Apache Portable Runtime (APR) project is to
create and maintain software libraries that provide a predictable
and consistent interface to underlying platform-specific
implementations. The primary goal is to provide an API to which
software developers may code and be assured of predictable if not
identical behaviour regardless of the platform on which their
software is built, relieving them of the need to code special-case
conditions to work around or take advantage of platform-specific
deficiencies or features.

DOWNLOAD:
=
Note that downloads from sourceware.org (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.

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://cygwin.com/lists.html

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


-- 
David Rothenberger    daver...@acm.org



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

[ANNOUNCEMENT] Updated: {gettext/gettext-devel/libgettextpo0/libintl8/libasprintf0}-0.17-4

[Charles Wilson]

gettext is the GNU package which provides 'national language support'
for other programs. It includes a number of utility programs.

Feature enhancement.

[[ compiled using gcc-3.4.4-999 and g++-3.4.4-999 ]]

This will most likely be the final gettext update for the cygwin-1.5
distribution; future development will continue with gettext-0.17-11 for
cygwin-1.7.

Changes since gettext-0.17-3

* Enable -V option for autopoint (helps work around
  bug with packages that use both libtool and gettext,
  but specify AM_GNU_GETTEXT_VERSION < 0.17. Because
  older gettext had a bug that caused difficulties with
  libtool, the -V option allows to automatically update
  the package to this version of gettext during the auto-
  reconf process, without manually patching the target
  package's configure.in.

-- 
Charles Wilson
volunteer gettext 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.



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

Re: LFTP issue

[Dave Korn]

Andrew Schulman wrote:

> Unfortunately, I don't have any idea what would make this happen in Cygwin and
> not in Linux.

  First thought that springs to my mind: what kind of console is in use here?
 What is the setting of CYGWIN=(no)tty?  And does Ctrl+D work as well as Ctrl+C?

cheers,
  DaveK

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

mousewheel in xterm, vim (was: mintty-0.4.0-1)

[David Arnstein]

On Sun, Jun 07, 2009 at 05:29:21PM +0100, Andy Koppe wrote:
> - The control sequences sent by the mousewheel outside application
> mouse mode have changed. The previous scheme that tied the encoding to
> the "modifier for scrolling with cursor keys" was a bad idea, because
> it meant that the configuration of any program using it had to change
> depending on that setting. The following lines in ~/.lesskey are now
> needed for mousewheel support in less. (Remember to run the lesskey
> command after editing .lesskey)
> 
> \eOa back-line
> \eOb forw-line
> \e[1;2a back-screen
> \e[1;2b forw-screen

This works well and I am pleased to have this feature. This might be
off-topic, but can anyone suggest how to get mousewheel working with
1. X11 xterm windows, while at shell prompt.
2. X11 xterm windows, while in vim.

Thanks for any suggestions.

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

Re: mousewheel in xterm, vim (was: mintty-0.4.0-1)

[Andy Koppe]

2009/6/8 David Arnstein:
> can anyone suggest how to get mousewheel working with
> 1. X11 xterm windows, while at shell prompt.

Not sure that's possible/practical. What would you expect it to do?

> 2. X11 xterm windows, while in vim.

Put this line in ~/.vimrc:
:set mouse=a

Andy

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