Hi
A new version of 'openldap/libopenldap2_3_0/openldap-devel' has been uploaded
to a server near you.
Please make sure to backup your database before installing the new
version. !!!
DESCRIPTION:
Lightweight Directory Access Protocol clients, servers and libraries.
CYG
I get a message box with the following error trying to run
any cygwin program:
The instruction at "0x6100365f" referenced memory at
"0x006ada90".
The memory could not be "written".
id.exe, bash.exe etc. All of them produce the error.
Somtimes, like 1 out of 50 or less a program will succeed.
For
Hi Mikkel,
I too have had this problem, as has another Cygwin user on this
mailing list. I am now attempting to install Cygwin once more to
check whether this problem still exists. If it does, it could be the
result of a recent change to a package.
I will let you know how things go.
Hugh
On
Hi Mikkel,
I have tried to install Cygwin, with no luck. The installation did
not even finish the final configuration before resulting in errors.
By this, I mean 'bash.exe' and 'id.exe' were terminated, resulting in
a Microsoft Error Reporting service window appearing.
It would appear that ther
Mikkel Erup wrote:
I get a message box with the following error trying to run
any cygwin program:
The instruction at "0x6100365f" referenced memory at
"0x006ada90".
The memory could not be "written".
id.exe, bash.exe etc. All of them produce the error.
Somtimes, like 1 out of 50 or less a prog
Hugh McMaster wrote:
Hi Mikkel,
I have tried to install Cygwin, with no luck. The installation did
not even finish the final configuration before resulting in errors.
By this, I mean 'bash.exe' and 'id.exe' were terminated, resulting in
a Microsoft Error Reporting service window appearing.
It
--- "Larry Hall (Cygwin)" <[EMAIL PROTECTED]>
wrote:
> Mikkel Erup wrote:
> > I get a message box with the following error trying to run
> > any cygwin program:
> >
> > The instruction at "0x6100365f" referenced memory at
> > "0x006ada90".
> > The memory could not be "written".
> >
> > id.exe,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I had to make this patch in order to use perl_postinst from the git
cygport instructions.
2006-11-27 Eric Blake <[EMAIL PROTECTED]>
* perl.cygclass (perl_postinst): Don't assume PERL_VENDORLIB
exists.
- --
Life is short - so eat de
--- Mikkel Erup <[EMAIL PROTECTED]> wrote:
>
> --- "Larry Hall (Cygwin)" <[EMAIL PROTECTED]>
> wrote:
>
> > Mikkel Erup wrote:
> > > I get a message box with the following error trying to run
> > > any cygwin program:
> > >
> > > The instruction at "0x6100365f" referenced memory at
> > > "0x0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 11/27/2006 7:13 AM:
> I had to make this patch in order to use perl_postinst from the git
> cygport instructions.
>
> 2006-11-27 Eric Blake <[EMAIL PROTECTED]>
>
> * perl.cygclass (perl_postinst): Don't assume PERL_
On 27 November 2006 14:06, Mikkel Erup wrote:
> Making sh.exe a copy of bash.exe and running the installer to
> reinstall produces the same error for bash.exe, ash.exe, sed.exe,
> sh.exe, rm.exe, cmp.exe and a some others (The instruction at
> "0x6100365f" referenced memory at "0x006ada90". The m
Looks like initially a path problem, plus an X-problem
I found out that at least one of the reasons grace and gracebat would not run
from the DOS command line
was that the directory for cygX11R6.dll was not in the path. I fixed that and
also put the actual path for gracebat
. c:cygwinusrsharegrac
On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
>On 27 November 2006 14:06, Mikkel Erup wrote:
>
>
>> Making sh.exe a copy of bash.exe and running the installer to
>> reinstall produces the same error for bash.exe, ash.exe, sed.exe,
>> sh.exe, rm.exe, cmp.exe and a some others (The instr
Christopher Faylor wrote:
On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
On 27 November 2006 14:06, Mikkel Erup wrote:
Making sh.exe a copy of bash.exe and running the installer to
reinstall produces the same error for bash.exe, ash.exe, sed.exe,
sh.exe, rm.exe, cmp.exe and a some
On 27 November 2006 16:53, Larry Hall (Cygwin) wrote:
>
> I'm with Dave and Mikkel in believing that the difference between safe mode
> and not is significant. I'm betting on virus scanners/firewalls or some
> network driver.
Or Logitech. Never let us forget Logitech. Never let us forget
Thanks. Indeed, I conclude that I must have edited /etc/profile long,
long ago (before I understood that this is not advisable), and saved it
in DOS-style format. I see in various discussions that bash has
recently been made intolerant of DOS-style line endings, explaining my
observation. (I
On Mon, Nov 27, 2006 at 11:52:55AM -0500, Larry Hall (Cygwin) wrote:
>Christopher Faylor wrote:
>>On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
>>>On 27 November 2006 14:06, Mikkel Erup wrote:
>>>
>>>
Making sh.exe a copy of bash.exe and running the installer to
reinstall produ
Christopher Faylor wrote:
> The address in question is in cygwin's cygthread handling code.
> Historically, this has been affected by things like scanners/firewalls
> and special drivers, so this is a good thought.
The clincher for me is when he said it works in safe mode without
networking, but
[EMAIL PROTECTED] wrote:
> Looks like initially a path problem, plus an X-problem
>
> I found out that at least one of the reasons grace and gracebat would not run
> from the DOS command line
Oh! You never said anything about cmd.exe. Naturally cygwin links only
work in a cygwin shell. bash, ash,
The archive contains repeated messages to the effect that Cygwin has
no concept of "hidden" files (except for dot-files), totally ignores
the "hidden" attribute, etc.
However, while I can create, read, add to (using ">>") and delete
files with this attribute set, I cannot overwrite them. For examp
On 11/26/06, Dr. Volker Zell wrote:
A new version of 'openldap/libopenldap2_3_0/openldap-devel' has been uploaded
to a server
near you.
Thanks for the update. I appreciate it!
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/proble
On Nov 27 18:23, John Smith wrote:
> The archive contains repeated messages to the effect that Cygwin has
> no concept of "hidden" files (except for dot-files), totally ignores
> the "hidden" attribute, etc.
>
> However, while I can create, read, add to (using ">>") and delete
> files with this at
Hi!
Windows XP Professional Ver 5.1 Build 2600 Service Pack 2
$ cygcheck -c | grep -E "man|cygwin"
apache2-manual 2.2.2-1 OK
cygwin 1.5.22-1 OK
cygwin-doc 1.4-4OK
cygwin-x-doc 1.0.4-1 OK
he
>DaveK wrote:
>You wouldn't by any chance be using any kind of firewall or
>internet
>security packages, would you? Something by Norton/McAffee,
>perhaps?
I am using outpost pro but that is not started in safe mode with
network where Cygwin produces the errors described.
Cygwin only works for me
On Saturday 25 November 2006 10:12 pm, Linda Walsh wrote:
> Vladimir Dergachev wrote:
> > This is curious - how do you find out fragmentation of ext3 file ? I do
> > not know of a utility to tell me that.
>
> ---
> There's a debugfs for ext2/ext3 that allows you to dump all of the
> segments
Hi,
I am looking for some help on the recommended method of getting gcc
-mno-cygwin to link to msvcr80, without linking to msvcrt. At the moment,
even when I specify -lmsvcr80 the resulting binary has a dependency on
msvcrt.dll
Looking at the specs file, -mno-cygwin always links with -lmsv
--- Mikkel Erup <[EMAIL PROTECTED]> wrote:
> >DaveK wrote:
> >You wouldn't by any chance be using any kind of firewall or
> >internet
> >security packages, would you? Something by Norton/McAffee,
> >perhaps?
>
> I am using outpost pro but that is not started in safe mode
> with
> network where
On Mon, Nov 27, 2006 at 02:25:00PM -0500, Vladimir Dergachev wrote:
>On Saturday 25 November 2006 10:12 pm, Linda Walsh wrote:
>> Vladimir Dergachev wrote:
>> > This is curious - how do you find out fragmentation of ext3 file ? I do
>> > not know of a utility to tell me that.
>>
>> ---
>> Ther
>
> Looking at the specs file, -mno-cygwin always links with
> -lmsvcrt, so
> short of editting the specs file, how is it possible to link
> only with
> msvcr80?
>
If you had posted this to the mingw list someone might have suggested:
cp -f /lib/mingw/libmsvcr80.a /tmp/libmsvcrt.a
gcc -mno
Danny,
> If you had posted this to the mingw list someone might have suggested:
Sorry, cygwin specs file looked like a cygwin problem to me :-)
> cp -f /lib/mingw/libmsvcr80.a /tmp/libmsvcrt.a
> gcc -mno-cygwin -L/tmp foo.c
Thanks for the suggestion. Still involves an extra build step to make
Some programs, most notably cron, expect /usr/sbin/sendmail
to point to mailer program such as exim or ssmtp.
Due to a buggy "ln -s" (now fixed in coreutils-6.6-2, thanks to Eric Blake),
a link /usr/sbin/sendmail.exe was sometimes created to point to
/usr/bin/exim.exe, which does not exist.
If th
Pierre A. Humblet wrote:
> Some programs, most notably cron, expect /usr/sbin/sendmail
> to point to mailer program such as exim or ssmtp.
>
> Due to a buggy "ln -s" (now fixed in coreutils-6.6-2, thanks to Eric Blake),
> a link /usr/sbin/sendmail.exe was sometimes created to point to
> /usr/bin/
Christopher Faylor wrote:
I was hoping that this discussion about ext3 would die a natural death but
it looks like I have to make the observation that this really has nothing
to do with Cygwin
---
Don't know what "cygwin" you are talking about, but the one I
download from cygwin.com seems t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Actually, that isn't all that is needed, since git creates
> /usr/lib/perl5/site_perl/5.8/cygwin/auto/Git/.packlist, and that .packlist
> also needs the same treatment. Maybe I need to figure out how to make git
> use PERL_VENDORLIB, instead of patc
Pierre A. Humblet wrote:
>>It doesn't quite work, the link created is still "sendmail.exe ->
>>/usr/bin/exim.exe".
>>
>>But this works: `ln -s /usr/bin/exim. /usr/sbin/sendmail`
>
> Thanks, but did you update to coreutils-6.6-2 ?
> Otherwise I hope Eric Blake will see your mail!
No, I still have
Hi everyone,
After doing some analysis of this issue, I have determined the problem
to most likely be Agnitum Outpost Firewall. I am not disputing your
findings (Mikkel, anyone else), but all of the evidence that I have
learned point to this. In fact, I installed the trial version 4.0 of
Outpos
Αρχικό μήνυμα από Volker Quetschke <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
> > Looks like initially a path problem, plus an X-problem
> >
> > I found out that at least one of the reasons grace and gracebat would not
> run
> > from the DOS command line
> Oh! You never said anything about
Four different patchsets. They should all apply independently with only
minor fuzz. I know you're too busy at the moment, Yaakov (congrats!),
to review these patches -- I just wanted to update them to latest
cygport CVS so they don't bitrot.
Short summary:
(1) Updated mixed download protocol
38 matches
Mail list logo
