[ANNOUNCEMENT] Updated: openldap-2.3.30-1/libopenldap2_3_0-2.3.30-1/openldap-devel-2.3.30-1

[Dr. Volker Zell]

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.


CYGWIN NEWS:


 o Routine update
 o Switched to cygport build framework


OpenLDAP NEWS
=

OpenLDAP 2.3 Change Log
---

OpenLDAP 2.3.30 Release
Fixed slapd authzTo/authzFrom URL matching (ITS#4744)
Fixed slapd syncrepl consumer memory leaks (ITS#4746)
Fixed slapd-hdb livelock (ITS#4738)
Fixed slapo-ppolicy external quality check (ITS#4741)
Documentation
Fixed ldapsearch(1) man page acknowledgement (ITS#4743)

OpenLDAP 2.3.29 Release
Fixed liblber/libldap error codes on Windows (ITS#4606)
Fixed libldap string length assert (ITS#4740)
Fixed liblunicode case mapping (ITS#4724)
Fixed slapd ldapi:// socket permissions (ITS#4709)
Fixed slapd c_writewaiters assert (ITS#4696, #4736)
Fixed slapo-accesslog purge contextCSN bug (ITS#4704)
Fixed slapo-accesslog modify/replace bug (ITS#4728)
Fixed slapo-dynlist leaks (ITS#4664)
Fixed slapo-ppolicy leaks (ITS#4665)
Fixed slapo-syncprov deadlock (ITS#4720)
Build environment
Added selection of ODBC (ITS#4735)
Documentation
Fixed slapd-ldap/meta(5) rebind-as-user usage (ITS#4715)
Fixed slapd-ldap/meta(5) missing network-timeout (ITS#4718)

OpenLDAP 2.3.28 Release
Fixed libldap ldap.conf max line length (ITS#4669)
Fixed libldap use keepalive for syncrepl (ITS#4708)
Fixed liblutil LDIF CR/LF parsing bug (ITS#4635)
Fixed librewrite LDAP map parsing bug
Fixed librewrite map double free bug
Added ldapsearch bad filter pattern check (ITS#4647)
Fixed slapd global access controls initialization (ITS#4654)
Fixed slapd setting c_sasl_bindop only on SASL binds
Fixed slapd max line length issue (ITS#4651)
Fixed slapd return code not being propagated (ITS#4565)
Fixed slapd integerBitAndMatch (ITS#4672)
Fixed slapd syncrepl modrdn new superior (ITS#4695)
Fixed slapd-ldap retry with idassert (ITS#4686)
Fixed slapd-meta DN massage error code handling (ITS#4711)
Fixed slapd-monitor locking with scope "subordinate" (ITS#4668)
Fixed slapd-perl deletes (ITS#2612)
Fixed slapd-perl backend initialization (ITS#4358)
Fixed slapd-perl finding interpreter inside a thread (ITS#4358)
Fixed slapo-ppolicy pwdChangedTime behavior (ITS#4692)
Fixed slapo-translucent ldapmodify crash (ITS#4673)
Documentation
Updated ldapsearch(1) options (ITS#4371,4526,4647)
Fixed slapd.access(5) non-optional dn= error (ITS#4522)

OpenLDAP 2.3.27 Release
Fixed libldap dangling pointer issue (previous fix was broken) 
(ITS#4405)

OpenLDAP 2.3.26 Release
Fixed libldap dnssrv bug with "not present" positive statement 
(ITS#4610)
Fixed libldap dangling pointer issue (ITS#4405)
Fixed slapd incorrect rebuilding of replica URI (ITS#4633)
Fixed slapd DN X.509 normalization crash (ITS#4644)
Fixed slapd-monitor operations order via callbacks (ITS#4631)
Fixed slapd-sql undefined filter handling (ITS#4604)
Fixed slapo-accesslog purge task during shutdown
Fixed slapo-ppolicy handling of default policy (ITS#4634)
Fixed slapo-ppolicy logging verbosity when using default policy
Fixed slapo-syncprov incomplete sync on restart issues (ITS#4622)

OpenLDAP 2.3.25 Release
Fixed liblber ber_bvreplace_x argument checks
Add libldap_r TLS concurrency workaround (ITS#4583)
Fixed liblutil password length bug
Add slapd glue/subordinate conflict check (ITS#4614)
Fixed slapd acl selfwrite bug (ITS#4587)
Fixed slapd bconfig "require" and "none" handling (ITS#4574)
Fixed slapd bconfig segfault when ldapadding new schema entries
Fixed slapd syncrepl no rootdn bug (ITS#4582)
Fixed slapd syncrepl contextCSN issue (ITS#4622)
Fixed slapd-bdb/hdb lock bug with virtual root (ITS#4572)
Fixed slapd-bdb/hdb modrdn new entry disappearing bug (ITS#4616)
Fixed slapd-bdb/hdb cache job issue
Fixed slapo-syncprov need new CSN with delete syncID sets (ITS#4534)
Fixed slapo-syncprov startup when lastmod is off (ITS#4613)
Fixed slapo-accesslog cn=config purge bug (ITS#4595)
Fixes slapo-auditlog DB initialization
Fixed slapo-ppolicy password hashing bug (ITS#4575)
Fixed slapo-ppolicy password modify pwdMustChange reset bug (ITS#4576)
Fixed slapo-ppolicy control can be critical (ITS#4596)
Fixed slapo-retco

1.5.22: Error from anything using the cygwin dll

[Mikkel Erup]

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 example I just ran uname from a windows command window
and it worked the first time, then failed several times.
Sometimes the cygwin.bat script will start the bash shell and not
show the above message box. In that case the first lines read
"5 [main] bash 3316 dll_crt0_1: internal error: couldn't
determine location of thread function on stack. Expect signal
errors.".
Any commands from the bash shell will still produce the error
message box described above, though.
The setup program didn't succeed normally either because ash.exe
and bash.exe crashed showing the message box described earlier.
If I boot into safe mode cygwin works but not if I boot into
safe mode with network.
I tried killing all processes not vital to running Windows as
well as stopping all services. 
Cygwin programs kept producing the error, though.
Output from cygcheck -s -v -r is attached.

Mikkel


 

Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

cygcheck.out
Description: 3924260979-cygcheck.out
--
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: 1.5.22: Error from anything using the cygwin dll

[Hugh McMaster]

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 27/11/06, 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 program will succeed.
For example I just ran uname from a windows command window
and it worked the first time, then failed several times.
Sometimes the cygwin.bat script will start the bash shell and not
show the above message box. In that case the first lines read
"5 [main] bash 3316 dll_crt0_1: internal error: couldn't
determine location of thread function on stack. Expect signal
errors.".
Any commands from the bash shell will still produce the error
message box described above, though.
The setup program didn't succeed normally either because ash.exe
and bash.exe crashed showing the message box described earlier.
If I boot into safe mode cygwin works but not if I boot into
safe mode with network.
I tried killing all processes not vital to running Windows as
well as stopping all services.
Cygwin programs kept producing the error, though.
Output from cygcheck -s -v -r is attached.


--
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: 1.5.22: Error from anything using the cygwin dll

[Hugh McMaster]

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 there is something incredibly wrong with Cygwin
at the moment.  There are many possible causes, however.  Such causes
could include, a new release of a package, a new Cygwin Dynamic
Library, etc.

Hugh

--
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: 1.5.22: Error from anything using the cygwin dll

[Larry Hall (Cygwin)]

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 program will succeed.
For example I just ran uname from a windows command window
and it worked the first time, then failed several times.
Sometimes the cygwin.bat script will start the bash shell and not
show the above message box. In that case the first lines read
"5 [main] bash 3316 dll_crt0_1: internal error: couldn't
determine location of thread function on stack. Expect signal
errors.".
Any commands from the bash shell will still produce the error
message box described above, though.
The setup program didn't succeed normally either because ash.exe
and bash.exe crashed showing the message box described earlier.
If I boot into safe mode cygwin works but not if I boot into
safe mode with network.
I tried killing all processes not vital to running Windows as
well as stopping all services. 
Cygwin programs kept producing the error, though.

Output from cygcheck -s -v -r is attached.



That's because the installation is not complete.  As you describe it,
it's a chicken'n'egg thing.  Perhaps removing '/bin/sh' (if it exists)
and making it a copy of '/bin/bash' will allow 'setup.exe' to finish?

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

--
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: 1.5.22: Error from anything using the cygwin dll

[Larry Hall (Cygwin)]

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 would appear that there is something incredibly wrong with Cygwin
at the moment.  There are many possible causes, however.  Such causes
could include, a new release of a package, a new Cygwin Dynamic
Library, etc.



And, there is incredibly little in this report that helps anyone here
help you figure out where your problem is.  Content-free problem reports
serve no useful purpose.  If you're interested in reporting a problem,
please read and follow the problem reporting guidelines at:



Following these guidelines will give people on this list some basis for
helping you find the problem you're having.  For example, Mikkel's report
allowed me to understand that his installation was incomplete.  From there,
I could suggest one possible course of action:



The more high-quality the problem report, the better the feedback. :-)


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

--
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: 1.5.22: Error from anything using the cygwin dll

[Mikkel Erup]

--- "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, bash.exe etc. All of them produce the error.
> > Somtimes, like 1 out of 50 or less a program will succeed.
> > For example I just ran uname from a windows command window
> > and it worked the first time, then failed several times.
> > Sometimes the cygwin.bat script will start the bash shell and
> not
> > show the above message box. In that case the first lines read
> > "5 [main] bash 3316 dll_crt0_1: internal error: couldn't
> > determine location of thread function on stack. Expect signal
> > errors.".
> > Any commands from the bash shell will still produce the error
> > message box described above, though.
> > The setup program didn't succeed normally either because
> ash.exe
> > and bash.exe crashed showing the message box described
> earlier.
> > If I boot into safe mode cygwin works but not if I boot into
> > safe mode with network.
> > I tried killing all processes not vital to running Windows as
> > well as stopping all services. 
> > Cygwin programs kept producing the error, though.
> > Output from cygcheck -s -v -r is attached.
> 
> 
> That's because the installation is not complete.  As you
> describe it,
> it's a chicken'n'egg thing.  Perhaps removing '/bin/sh' (if it
> exists)
> and making it a copy of '/bin/bash' will allow 'setup.exe' to
> finish?

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 memory could
not be "written"). Will try booting to safe and install from
the hdd to see if it lets the installer complete.
I am also wondering why cygwin works if I boot to safe mode
without network. As I said it doesn't work if I boot to safe
mode with network.


 

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.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/

cygport bug

[Eric Blake]

-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 dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFavJ984KuGfSFAYARAjgUAJ96iZdE/PffXorEkovS47eD496jwgCguzNd
/qZNE2wPDiFySLr47Oc1q9U=
=KWA8
-END PGP SIGNATURE-
--- /usr/lib/cygport/lib/perl.cygclass.orig 2006-11-27 07:05:30.115969000 
-0700
+++ /usr/lib/cygport/lib/perl.cygclass  2006-11-27 07:09:06.350344000 -0700
@@ -108,7 +108,9 @@
_EOF
fi
 
-   find ${D}${PERL_VENDORLIB} -name .packlist -exec sed -i -e "s:${D}::g" 
'{}' +
+   if test -d ${D}${PERL_VENDORLIB} ; then
+   find ${D}${PERL_VENDORLIB} -name .packlist -exec sed -i -e 
"s:${D}::g" '{}' +
+   fi
 }
 
 src_compile() {

--
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: 1.5.22: Error from anything using the cygwin dll

[Mikkel Erup]

--- 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
> > > "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 example I just ran uname from a windows command window
> > > and it worked the first time, then failed several times.
> > > Sometimes the cygwin.bat script will start the bash shell
> and
> > not
> > > show the above message box. In that case the first lines
> read
> > > "5 [main] bash 3316 dll_crt0_1: internal error: couldn't
> > > determine location of thread function on stack. Expect
> signal
> > > errors.".
> > > Any commands from the bash shell will still produce the
> error
> > > message box described above, though.
> > > The setup program didn't succeed normally either because
> > ash.exe
> > > and bash.exe crashed showing the message box described
> > earlier.
> > > If I boot into safe mode cygwin works but not if I boot
> into
> > > safe mode with network.
> > > I tried killing all processes not vital to running Windows
> as
> > > well as stopping all services. 
> > > Cygwin programs kept producing the error, though.
> > > Output from cygcheck -s -v -r is attached.
> > 
> > 
> > That's because the installation is not complete.  As you
> > describe it,
> > it's a chicken'n'egg thing.  Perhaps removing '/bin/sh' (if
> it
> > exists)
> > and making it a copy of '/bin/bash' will allow 'setup.exe' to
> > finish?
> 
> 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 memory
> could
> not be "written"). Will try booting to safe and install from
> the hdd to see if it lets the installer complete.
> I am also wondering why cygwin works if I boot to safe mode
> without network. As I said it doesn't work if I boot to safe
> mode with network.
> 
> 
>  
>

> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.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/
> 
> 

Reinstalling from local hdd in safe mode without network allowed
the installer to complete. The problem persists in normal mode,
though


 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

--
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: cygport bug

[Eric Blake]

-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_VENDORLIB
>   exists.

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 patching cygport; any advice from other
maintainers who have made a package with an included perl module?

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFavTY84KuGfSFAYARAob5AKDKje/1Da9EAFCEWMMrBySsF6B2wQCggv3w
1u/O2OvrC+nuu3gmX7ES86o=
=It1g
-END PGP SIGNATURE-

--
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: 1.5.22: Error from anything using the cygwin dll

[Dave Korn]

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 memory could
> not be "written"). Will try booting to safe and install from
> the hdd to see if it lets the installer complete.
> I am also wondering why cygwin works if I boot to safe mode
> without network. As I said it doesn't work if I boot to safe
> mode with network.

  You wouldn't by any chance be using any kind of firewall or internet
security packages, would you?  Something by Norton/McAffee, perhaps?


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

Installation problem(?) for grace: HOW DO I GET old xorgs?

[moka]

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:cygwinusrsharegracebin before c:cygwinbin, so  a command would look
for the actual executables
 before the symlinks. 
So I run
c:mydir> c:cygwinusrsharegracebingracebat test.dat -hdevice JPEG
-printfile gtest.jpg
or
c:mydir> gracebat test.dat -hdevice JPEG -printfile gtest.jpg

It runs instantly, but produced NO file gtest.jpg

(Before adding the actual executable directory to the path before the bin, it
just hung there)


Also, if I try to run grace by clicking on its icon(not the symlink), it does
nothing
If I run
c:mydir> grace
it does nothing

but if I do
c:mydir> ash

$grace
 I get back 
grace>1

If I do 
c:mydir> xmgrace
I get  Can't open display
Failed initializing GUI, exiting

So, it looks like an X-problem. How do I go about  solving it?Αρχικό μήνυμα από

[EMAIL PROTECTED]:

> Ok, thanks and sorry for including raw emails. Now
> 1) I removed all mingw from the path, rebooted, ran ash, /bin/rebaseall
> and rebooted
> 
> cat still works
> grace and gracebat do not(no complaints, but they produce nothing)
> 2) Do other x-programs work? I tried xterm and got back cygX11-6.dll not
> found
> in path
> So could this be a broken installation  or am I missing something in
> patrh(just
> c:cygwinbin)?
> > 
> > > Looking at your cygcheck one sees that you are "hiding" a lot of cygwin
> > > programs with MinGW and other stuff. Reorganize your PATH to solve this.
> > > 
> > > You also never told us if xmgrace works.
> > Oh, sorry, you did. Never mind. Do other X programs work?
> > 
> >   Volker
> > 
> > > I mean can you work with the
> > > grace GUI if you just use the program itself and not gracebat.
> > > 
> > >   Volker
> > 
>  ImageMagick  6.3.0.1-2
> > In fact, your cygcheck output shows that you already have the latest
> > version of ImageMagick.
> >
> 
> > So, everything seems to be ok and what I should do is get rid of MINGW?
> > I installed this before cygwin when I was trying to get a Perl module
> > DBD-Oracle
> >  to work...
> > So just get rid of D:MINGW ?
> 
> Or at least remove it from your PATH.
> 



--
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: 1.5.22: Error from anything using the cygwin dll

[Christopher Faylor]

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 instruction at
>> "0x6100365f" referenced memory at "0x006ada90". The memory could
>> not be "written"). Will try booting to safe and install from
>> the hdd to see if it lets the installer complete.
>> I am also wondering why cygwin works if I boot to safe mode
>> without network. As I said it doesn't work if I boot to safe
>> mode with network.
>
>  You wouldn't by any chance be using any kind of firewall or internet
>security packages, would you?  Something by Norton/McAffee, perhaps?

And, this wouldn't be a situation of multiple cygwins on the machine,
would it?

And, as has been previously requested, cygcheck output would be useful.

(No, cygcheck is not a cygwin program.  It does run a cygwin program
but any error you get should not stop cygcheck from providing useful
output)

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: 1.5.22: Error from anything using the cygwin dll

[Larry Hall (Cygwin)]

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 others (The instruction at
"0x6100365f" referenced memory at "0x006ada90". The memory could
not be "written"). Will try booting to safe and install from
the hdd to see if it lets the installer complete.
I am also wondering why cygwin works if I boot to safe mode
without network. As I said it doesn't work if I boot to safe
mode with network.

 You wouldn't by any chance be using any kind of firewall or internet
security packages, would you?  Something by Norton/McAffee, perhaps?


And, this wouldn't be a situation of multiple cygwins on the machine,
would it?

And, as has been previously requested, cygcheck output would be useful.



Actually, Mikkel was good enough to provide the 'cygcheck' output with his
original message. :-)



There's no other cygwin1.dll found, though that was my first thought too.

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.


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

--
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: 1.5.22: Error from anything using the cygwin dll

[Dave Korn]

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 Logitech
and their truly wondrous "process monitor".  How anyone ever managed to get a
webcam to work without first installing software that hooks into every single
process in your entire operating system, I don't know.  Thank god Logitech
were able to see the light.  I can only imagine teh entire internuts would be
totally b0rk by now if it wasn't for their mad-leet coding skillz.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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-installed /etc/profile supplied appears to be DOS-type text file

[Rex Godby]

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'll delete my hand-altered /etc/profile and let it be 
overwritten by the official Cygwin version.)  Rex


On 26/11/2006 22:21, Dave Korn wrote:

On 26 November 2006 14:33, Rex Godby wrote:


After updating Cygwin today (26 November 2006), the installed version of
/etc/profile appeared to become a DOS-type text file rather than a Unix-type
text file.  That caused severe problems (e.g. "unknown command") when
starting up the Cygwin login shell.  Correcting the file type back to Unix
seems to have solved the problem.


  There aint no CRs in the one I just downloaded:


..

  Is it possible you've made local modifications to your /etc/profile, so it
no longer gets upgraded by setup.exe?

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/

Re: 1.5.22: Error from anything using the cygwin dll

[Christopher Faylor]

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 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 memory could
not be "written"). Will try booting to safe and install from
the hdd to see if it lets the installer complete.
I am also wondering why cygwin works if I boot to safe mode
without network. As I said it doesn't work if I boot to safe
mode with network.
>>> You wouldn't by any chance be using any kind of firewall or internet
>>>security packages, would you?  Something by Norton/McAffee, perhaps?
>>
>>And, this wouldn't be a situation of multiple cygwins on the machine,
>>would it?
>>
>>And, as has been previously requested, cygcheck output would be useful.
>
>
>Actually, Mikkel was good enough to provide the 'cygcheck' output with his
>original message. :-)
>
>

Huh!  Well, it's hardly *my* fault that I have to scroll down in the archives
to see the attachment.

Ok, well, maybe it is my fault, but they really should improve the archives
so that it is clear that there is an attachment.

Ok, well, maybe I'm responsible for the format of the archives but...

.
.
.

I got nothin'.

Sorry for missing this.  I would still do a check for other copies of
cygwin1.dll however.

>There's no other cygwin1.dll found, though that was my first thought too.
>
>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.

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.

I have seen something like this myself in the past but it was so sporadic
that I was never able to track it down and I haven't seen it in months.

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: 1.5.22: Error from anything using the cygwin dll

[Brian Dessent]

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 not in safe mode with networking... Kind of screams
"shoddy VPN client" or somesuch.

Brian

--
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: Installation problem(?) for grace: HOW DO I GET old xorgs?

[Volker Quetschke]

[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, zsh, tcsh, ... pick your poison.

> was that the directory for  cygX11R6.dll was not in the path. I fixed that and
> also put the actual path for gracebat
Well, using cygwin.bat would have solved that for you too. (And would
have given you a nice bash prompt.)

> . c:cygwinusrsharegracebin before c:cygwinbin, so  a command would look
Looks really funny, you lost your backslashes in the mail ;)

> for the actual executables
>  before the symlinks. 
> So I run
> c:mydir> c:cygwinusrsharegracebingracebat test.dat -hdevice JPEG
> -printfile gtest.jpg
> or
> c:mydir> gracebat test.dat -hdevice JPEG -printfile gtest.jpg
> 
> It runs instantly, but produced NO file gtest.jpg
> 
> (Before adding the actual executable directory to the path before the bin, it
> just hung there)
> 
> 
> Also, if I try to run grace by clicking on its icon(not the symlink), it does
> nothing
> If I run
> c:mydir> grace
> it does nothing
No wonder, half of it's paths are missing. Start it from a shell ...

> 
> but if I do
> c:mydir> ash
> 
> $grace
>  I get back 
> grace>1

like you did here.

> If I do 
> c:mydir> xmgrace
> I get  Can't open display
> Failed initializing GUI, exiting
> 
> So, it looks like an X-problem. How do I go about  solving it?Αρχικό μήνυμα 
> από

The X-problem seems to be that the X-server is not running. Try using
startxwin.bat. (This one actually works if you "click" on it.) *shudder*

  Volker


-- 
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature

Files with Win32 "hidden" attribute

[John Smith]

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

jaipur:~$ echo xxx >foo
jaipur:~$ echo yyy >foo
jaipur:~$ attrib +h foo
jaipur:~$ echo zzz >foo
bash: foo: Permission denied
jaipur:~$ echo zzz >bar
jaipur:~$ cp bar foo
cp: cannot create regular file `foo': Permission denied
jaipur:~$ attrib -h foo
jaipur:~$ echo zzz >foo
jaipur:~$ cp bar foo
jaipur:~$

In case this is happening because of some local misconfiguration, I've
attached cygcheck output.

If it is actually a genuine problem, is it something that can be
fixed? It's a nuisance having Cygwin's behaviour affected by something
it officially takes no notice of.

John Smith

--
Dr J. D. Smith   *  [EMAIL PROTECTED]
Faculty of Oriental Studies  *  http://bombay.indology.info
Sidgwick Avenue  *  Tel. +44 (0)1223 335140
Cambridge CB3 9DA*  Fax  +44 (0)1223 335110

Cygwin Configuration Diagnostics

Current System Time: Mon Nov 27 17:37:00 2006



Windows XP Professional Ver 5.1 Build 2600 Service Pack 2



Path:   C:\cygwin\home\john\bin

C:\cygwin\usr\local\bin

C:\cygwin\usr\local\bin

C:\cygwin\bin

C:\cygwin\bin

C:\cygwin\usr\X11R6\bin

.

C:\cygwin\bin

C:\cygwin\usr\X11R6\bin

c:\WINDOWS\system32

c:\WINDOWS

c:\WINDOWS\System32\Wbem

c:\WINDOWS\system32\gs\gs8.13\bin

c:\Program Files\Common Files\GTK\2.0\bin

c:\gcc-2.95.2\bin

c:\Program Files\FDK1.6-Win4\Tools\Programs\makeotf\exe

c:\Program Files\PuTTY

C:\cygwin\usr\X11R6\bin

C:\cygwin\usr\X11R6\bin



Output from C:\cygwin\bin\id.exe (nontsec)

UID: 1004(john) GID: 513(None)

0(root) 513(None)   544(Administrators) 545(Users)



Output from C:\cygwin\bin\id.exe (ntsec)

UID: 1004(john) GID: 513(None)

0(root) 513(None)   544(Administrators) 545(Users)



SysDir: C:\WINDOWS\system32

WinDir: C:\WINDOWS



USER = 'john'

PWD = '/home/john'

CYGWIN = 'binmode tty ntsec '

HOME = '/home/john'

MAKE_MODE = 'unix'



LESSKEY = '/home/john/.less'

HOMEPATH = '\Documents and Settings\john'

NNTPSERVER = 'nntp-serv.cam.ac.uk'

MANPATH = 
'/home/john/man:/usr/local/man:/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man'

APPDATA = 'C:\Documents and Settings\john\Application Data'

HOSTNAME = 'jaipur'

XKEYSYMDB = '/usr/X11R6/lib/X11/XKeysymDB'

SHELL = '/bin/bash'

TERM = 'xterm'

PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 13 Stepping 6, GenuineIntel'

HISTSIZE = '1000'

WINDIR = 'C:\WINDOWS'

TEXDOCVIEW_txt = 'cygstart %s'

GS_LIB = '/home/john/ghostscript'

VFFONTS = '.:/home/john/tex/fonts/vf::'

TEXDOCVIEW_dvi = 'cygstart %s'

MFPOOL = '.::'

WINDOWID = '16777230'

OLDPWD = '/cygdrive/f/cygwin/home/john'

USERDOMAIN = 'JAIPUR'

MINEDKEYMAP = 'ac'

OS = 'Windows_NT'

ALLUSERSPROFILE = 'C:\Documents and Settings\All Users'

XAPPLRESDIR = '/usr/X11R6/lib/X11/app-defaults'

HISTFILESIZE = '1000'

XTERM_SHELL = '/bin/bash'

XCMSDB = '/usr/X11R6/lib/X11/Xcms.txt'

LS_COLORS = 
'no=00:fi=00:di=01;38:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:'

TEMP = '/cygdrive/c/DOCUME~1/john/LOCALS~1/Temp'

COMMONPROGRAMFILES = 'C:\Program Files\Common Files'

XNLSPATH = '/usr/X11R6/lib/X11/locale'

TEXPOOL = '.::'

TERMCAP = 'xterm-r6|xterm|xterm X11R6 
version:am:km:mi:ms:xn:co#80:it#8:li#40:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:ae=^O:al=\E[L:as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:ei=\E[4l:ho=\E[H:im=\E[4h:is=\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E>:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kd=\EOB:ke=\E[?1l\E>:kh=\E[1~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:md=\E[1m:me=\E[m:mr=\E[7m:nd=\E[C:rc=\E8:sc=\E7:se=\E[m:sf=^J:so=\E[7m:sr=\EM:ta=^I:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:ue=\E[m:up=\E[A:us=\E[4m:kb=\010:'

TEXFONTS = '.:/home/john/tex/fonts/tfm::'

LESSCHARDEF = '8bcccbcc18b.'

USERNAME = 'john'

PAGER = 'less -s'

GS_PROG = 'C:\Program Files\gs\gs8.51\bin\gswin32.exe'

TEXDOCVIEW_pdf = 'cygstart %s'

PROCESSOR_LEVEL = '6'

MFBASES = '.:/home/john/mf/bases::'

LESSEDIT = '%E %f ?lm-g %lm.'

FP_NO_HOST_CHECK = 'NO'

jaipur = '89.241.153.40'

INPUTRC = '/home/john/.inputrc'

GS_OPTIONS = '-sPAPERSIZE=a4'

SYSTEMDRIVE = 'C:'

CYGWIN_ROOT = '\cygwin'

EDITOR = 'emacs -nw'

LANG = 'C'

TEXDOCVIEW_html

Re: [ANNOUNCEMENT] Updated: openldap-2.3.30-1/libopenldap2_3_0-2.3.30-1/openldap-devel-2.3.30-1

[Svend Sorensen]

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/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Files with Win32 "hidden" attribute

[Corinna Vinschen]

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 attribute set, I cannot overwrite them. For example:
> 
> jaipur:~$ echo xxx >foo
> jaipur:~$ echo yyy >foo
> jaipur:~$ attrib +h foo
> jaipur:~$ echo zzz >foo
> bash: foo: Permission denied
> jaipur:~$ echo zzz >bar
> jaipur:~$ cp bar foo
> cp: cannot create regular file `foo': Permission denied
> jaipur:~$ attrib -h foo
> jaipur:~$ echo zzz >foo
> jaipur:~$ cp bar foo
> jaipur:~$
> 
> In case this is happening because of some local misconfiguration, I've
> attached cygcheck output.
> 
> If it is actually a genuine problem, is it something that can be
> fixed? It's a nuisance having Cygwin's behaviour affected by something
> it officially takes no notice of.

Thanks for the report.  I found a tiny comment in MSDN which explains
why this happens.  I'll apply an appropriate patch to Cygwin.


Thanks again,
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/

1.5.22-1: Error by using man (ap)

[Alexander Palm]

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
help2man 1.35.1-1 OK
man  1.6d-2   OK
perl_manpages5.8.7-5  OK
xfig-man 3.2.4-2  OK
XFree86-man  4.3.0-10 OK
xorg-x11-man-pages   6.8.99.901-1 OK
xorg-x11-man-pages-html  6.8.99.901-1 OK

If I call the man command following is happens:

$ man man
fgets: No such file or directory
Error reading man page /usr/share/man/man1/man.1.gz
No manual entry for man

$ man bash
Error executing formatting or display command.
System command (cd "/usr/share/man" && (echo ".ll 9.0i"; echo ".nr LL 9.0i"; 
echo ".pl 1100i"; /usr/bin/cat '/usr/share/man/man1/bash.1'; echo ".\\\""; echo 
".pl \n(nlu+10") | /usr/bin/tbl | /usr/bin/nroff -c -mandoc | /usr/bin/less 
-isrR) exited with status 14592.
No manual entry for bash

$ man if
fgets: No such file or directory
Error reading man page /usr/share/man/man1/bash_builtins.1.gz
No manual entry for if

$ man wget
fgets: No such file or directory
Error reading man page /usr/share/man/man1/wget.1.gz
No manual entry for wget

What is wrong? Please help me.

Thanks, Alex

--
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: 1.5.22: Error from anything using the cygwin dll

[Mikkel Erup]

>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 in safe mode without network.
I guess that source can be ruled out.

>Christopher Faylor wrote:
>And, this wouldn't be a situation of multiple cygwins on the
>machine,
>would it?

Nope. Searched the hdd for any duplicate cyg*dll files for the
sake of it. None present.

>And, as has been previously requested, cygcheck output would be
>useful.

If you read my original post in this thread you'll see that I
attached the ouput of cygcheck -s -v -r.
I know cygcheck doesn't use cygwin1.dll. It produces the error
running id.exe, though. I just closed the message box and let
it finnish anyway.

>DaveK wrote:
>Or Logitech.  Never let us forget Logitech.  Never let us forget
Logitech
>and their truly wondrous "process monitor".  How anyone ever
managed to get ...

I'm using a logitech mouse but the default windows driver and
no extra logitech blowware ;)

>Larry Hall wrote:
>I'm betting on virus scanners/firewalls or some
network driver.

My av software is not startet in safe mode with networking. 
Neither is my firewall.
I'll try removing the drivers for my wifi card as well as 
for the onboard lan card temporarely.
I think it must boil down to something like that as cygwin
works in safe mode without networking.

>Bryan Dessent wrote:
>The clincher for me is when he said it works in safe mode
without
>networking, but not in safe mode with networking... Kind of
screams
>"shoddy VPN client" or somesuch.

Right. I have no VPN client, though, and only essential system
services are started in safe mode with networking so as mentioned
I guess it more or less boils down to a driver issue.
I'll report the result when I've tried removing the network 
drivers.


 

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.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: NTFS fragmentation redux

[Vladimir Dergachev]

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 associated with an inode.  "ls -i" dumps the inode number.
> A quick hack (attached) displays segments for either extX or (using
> xfs_bmap) xfs. I couldn't find a similar tool for jfs or reiser (at least
> not in my distro).
>

Cool, thank you !

fragfilt.ext does not quite work for me. Also, looking at the code, it is not 
obvious whether it takes indirect blocks into account - but I am not that 
fluent in perl, so, perhaps I missed it.

Here is a piece of output from my debugfs:


(IND):118948480, (898060-898435):118948488-118948863, 
(898436-898660):118949376-118949600, (898661-899083):118949612-118950034, 
(IND):118950035, (899084-900107):118950036-118951059, (IND):118951060, 
(900108-901131):118951061-118952084, (IND):118952085, 
(901132-902155):118952086-118953109, (IND):118953110, 
(902156-902741):118953111-118953696, (902742-903179):118953701-118954138, 
(IND):118954139, (903180-903760):118954140-118954720, 
(903761-904203):118955745-118956187, (IND):118956188, 
(904204-904783):118956189-118956768, (904784-905227):118957813-118958256, 
(IND):118958257, (905228-906251):118958258-118959281, (IND):118959282, 
(906252-906760):118959283-118959791

> > From indirect observation ext3  does not have fragmentation nearly that
> > bad until the filesystem is close to full or I would not be able to reach
> > sequential read speeds (the all-seeks speed is about 6 MB/sec for me, I
> > was getting 40-50 MB/sec). This was on much larger files though.
>
> ---
> On an empty partition, I created a deterministic pathological case. Lots
> little files all separated by holes.  ext3 (default mount) just
> allocated 4k blocks in a first come-first serve manner.  XFS apparently
> looked for larger allocation units as the file was larger than 4K.
> In that regard, it's similar to NT.  I believe both use a form of B-Tree
> to manage free space.

I see. Well, I was concerned with non-pathological case of having lots of 
contiguous free space and apparent inability of NTFS to handle slowly grown 
files (i.e. writes in append mode). A common usage case are logfiles and 
downloads.

>
> > Which journal option was the filesystem mounted with ?
>
> ---
>   I can't see how that would matter, but default. For speed of
> test, I mounted both with noatime,async & xfs also got
> nodiratime and logbuffs=8 (or deletes take way long).

Thank you, just wanted to cover all possibilities.

>
> > I actually implemented a workaround that calls "fsutil file createnew
> > FILESIZE" to preallocate space and then write data in append mode
> > (after doing seek 0).
>
> ---
>   I wonder if it does the same thing as dd or if it uses
> the special call to tell the OS what to expect.  FWIW,
> "cp" used some smallish number of blocks (4 or 8, I think), so
> it is almost guaranteed to give you about the worse possibly
> fragmented file! :-)  Most likely the other file utils will
> give similar allocation performance (not so good).

I believe it is a special call that tells the filesystem to reserve needed 
space, but does not write anything to disk. I wonder whether it leaks 
information from deleted files.

Btw, I found out that IE writes files downloaded from the web into the 
temporary directory - and they end up all broken in tiny pieces, but, after 
that, it *copies* them to the actual location (instead of doing a move as 
would be reasonable). The copy ends up not being fragmented as, my guess, IE 
now knows its sides and asks for it.

 best

Vladimir Dergachev


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

mno-cygwin dll woes

[Hugo Duncan]

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 -lmsvcrt, so  
short of editting the specs file, how is it possible to link only with  
msvcr80?

I have found various old discussions of this issue but nothing recent.

Any help appreciated,

Hugo



I have:

gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)
CYGWIN_NT-5.1 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin


 

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.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: 1.5.22: Error from anything using the cygwin dll

[Mikkel Erup]

--- 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 Cygwin produces the errors described. 
> Cygwin only works for me in safe mode without network.
> I guess that source can be ruled out.
> 
> >Christopher Faylor wrote:
> >And, this wouldn't be a situation of multiple cygwins on the
> >machine,
> >would it?
> 
> Nope. Searched the hdd for any duplicate cyg*dll files for the
> sake of it. None present.
> 
> >And, as has been previously requested, cygcheck output would
> be
> >useful.
> 
> If you read my original post in this thread you'll see that I
> attached the ouput of cygcheck -s -v -r.
> I know cygcheck doesn't use cygwin1.dll. It produces the error
> running id.exe, though. I just closed the message box and let
> it finnish anyway.
> 
> >DaveK wrote:
> >Or Logitech.  Never let us forget Logitech.  Never let us
> forget
> Logitech
> >and their truly wondrous "process monitor".  How anyone ever
> managed to get ...
> 
> I'm using a logitech mouse but the default windows driver and
> no extra logitech blowware ;)
> 
> >Larry Hall wrote:
> >I'm betting on virus scanners/firewalls or some
> network driver.
> 
> My av software is not startet in safe mode with networking. 
> Neither is my firewall.
> I'll try removing the drivers for my wifi card as well as 
> for the onboard lan card temporarely.
> I think it must boil down to something like that as cygwin
> works in safe mode without networking.
> 
> >Bryan Dessent wrote:
> >The clincher for me is when he said it works in safe mode
> without
> >networking, but not in safe mode with networking... Kind of
> screams
> >"shoddy VPN client" or somesuch.
> 
> Right. I have no VPN client, though, and only essential system
> services are started in safe mode with networking so as
> mentioned
> I guess it more or less boils down to a driver issue.
> I'll report the result when I've tried removing the network 
> drivers.
> 

Hmm. Removing the drivers and disabling the ethernet OB card
in the bios and physically removing the wifi card didn't help.
Manually disabling the extra services that run in safe mode with
networking and not in normal safe mode didn't make cygwin run 
either.
Could someone advice on how to debug this further. Maybe a
link or something.
I need to get the NFS server running and I would really prefer
not paying big $$$ for an inferiour windows product.



 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

--
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: NTFS fragmentation redux

[Christopher Faylor]

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.
>>
>> ---
>>  There's a debugfs for ext2/ext3 that allows you to dump all of the
>> segments associated with an inode.  "ls -i" dumps the inode number.
>> A quick hack (attached) displays segments for either extX or (using
>> xfs_bmap) xfs. I couldn't find a similar tool for jfs or reiser (at least
>> not in my distro).
>>
>
>Cool, thank you !
>
>fragfilt.ext does not quite work for me. Also, looking at the code, it is not 
>obvious whether it takes indirect blocks into account - but I am not that 
>fluent in perl, so, perhaps I missed it.
>
>Here is a piece of output from my debugfs:
>
>
>(IND):118948480, (898060-898435):118948488-118948863, 
>(898436-898660):118949376-118949600, (898661-899083):118949612-118950034, 
>(IND):118950035, (899084-900107):118950036-118951059, (IND):118951060, 
>(900108-901131):118951061-118952084, (IND):118952085, 
>(901132-902155):118952086-118953109, (IND):118953110, 
>(902156-902741):118953111-118953696, (902742-903179):118953701-118954138, 
>(IND):118954139, (903180-903760):118954140-118954720, 
>(903761-904203):118955745-118956187, (IND):118956188, 
>(904204-904783):118956189-118956768, (904784-905227):118957813-118958256, 
>(IND):118958257, (905228-906251):118958258-118959281, (IND):118959282, 
>(906252-906760):118959283-118959791

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.

Please take this somewhere else.

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/

[OT] RE: mno-cygwin dll woes

[Danny Smith]

> 
> 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-cygwin -L/tmp foo.c

However, any required dll's that also depended on msvcrt.dll would still
bring in 
the system lib.

Danny


--
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: [OT] RE: mno-cygwin dll woes

[Hugo Duncan]

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  
sure the copied lib files exist, but much better than editting spec files.

Appreciate the help,

Hugo



 

Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.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/

Problem with /usr/sbin/sendmail ==> /usr/bin/exim

[Pierre A. Humblet]

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 this is the case on your installation, remove /usr/sbin/sendmail.exe
and create the proper symbolic link:
ln -s /usr/bin/exim /usr/sbin/sendmail

Pierre




--
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: Problem with /usr/sbin/sendmail ==> /usr/bin/exim

[René Berber]

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/exim.exe, which does not exist.
> 
> If this is the case on your installation, remove /usr/sbin/sendmail.exe
> and create the proper symbolic link:
> ln -s /usr/bin/exim /usr/sbin/sendmail

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`
-- 
René Berber


--
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: NTFS fragmentation under Cygwin & not NT/XP; redux

[Linda Walsh]

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 to have several utils that deal with
ext2/ext3.  If  ext2/ext3 performance relative to NTFS is a verboten
discussion and has nothing to do with Cygwin, then perhaps
these utils shouldn't be in Cygwin??   


> uname -sro
CYGWIN_NT-5.1 1.5.22(0.156/4/2) Cygwin
> apropos ext2
debugfs  (8)  - ext2/ext3 file system debugger
dumpe2fs (8)  - dump ext2/ext3 filesystem information
e2fsck   (8)  - check a Linux ext2/ext3 file system
e2fsck [fsck](8)  - check a Linux ext2/ext3 file system
e2image  (8)  - Save critical ext2/ext3 filesystem data to a file
e2label  (8)  - Change the label on an ext2/ext3 filesystem
mke2fs   (8)  - create an ext2/ext3 filesystem
mke2fs [mkfs](8)  - create an ext2/ext3 filesystem
resize2fs(8)  - ext2/ext3 file system resizer
tune2fs  (8)  - adjust tunable filesystem parameters on ext2/ext3 fi
lesystems
law> apropos ext3
debugfs  (8)  - ext2/ext3 file system debugger
dumpe2fs (8)  - dump ext2/ext3 filesystem information
e2fsck   (8)  - check a Linux ext2/ext3 file system
e2fsck [fsck](8)  - check a Linux ext2/ext3 file system
e2image  (8)  - Save critical ext2/ext3 filesystem data to a file
e2label  (8)  - Change the label on an ext2/ext3 filesystem
mke2fs   (8)  - create an ext2/ext3 filesystem
mke2fs [mkfs](8)  - create an ext2/ext3 filesystem
resize2fs(8)  - ext2/ext3 file system resizer
tune2fs  (8)  - adjust tunable filesystem parameters on ext2/ext3 fi
lesystems
--
The discussion has been about NTFS and how NT-native apps handle
fragmentation compared to Cygwin.

Cygwin's performance with NTFS (both default and optimized) was being
compared to linux's allocation performance on "xfs" and "ext2(&3)".

Two responses clarifying the test conditions on ext2/3 were asked and
then you declare the whole "discussion"[sic] as having nothing to do
with Cygwin?  Perhaps not caring for the topic, you haven't been
reading it?   The discussion has everything to do with the performance
on NTFS, the underlying filesystem that cygwin recommends vs. ext2/ext3. 


As for your assertion that ext2/ext3 have nothing to do with cygwin,
the cygwin distribution contains/provides several utilities ( as
shown above) for for creating, checking, debugging, resizing,
tuning imaging, labeling and dumping ext2/ext3 file systems.

The data I processed was output from "debugfs" -- a utility that also
exists on cygwin.

How can we begin to determine how well or poorly cygwin on top of NT
does if we aren't allowed to discuss how well ext2/ext3 perform.
For whatever reasons, they are the only non-NT file systems
cygwin seems to have utilities for.

-l





--
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: cygport bug

[Yaakov S (Cygwin Ports)]

-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 patching cygport; any advice from other
> maintainers who have made a package with an included perl module?

Try the attached .cygport and .src.patch with a stock cygport.  I will
consider adding some logic to detect the (IMO erraneous) use of
site_perl instead of vendor_perl.


Yaakov
Cygwin Ports
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFa7DlpiWmPGlmQSMRAoSYAJ4v4vaHDGVkb6tkImo/ZbxyCKRrUgCePgdU
01ZN6Eg5Sz4GWMALabja+RE=
=QtrQ
-END PGP SIGNATURE-
# git.cygport - directions for packaging git for cygwin

# Copyright (C) 2006 Eric Blake
# This file is free software; I give unlimited permission to copy and/or
# distribute it, with or without modifications, as long as this notice is
# preserved.

inherit perl

DESCRIPTION="Fast Version Control System"
HOMEPAGE=http://git.or.cz
SRC_URI="http://kernel.org/pub/software/scm/$PN/$P.tar.bz2 \
http://kernel.org/pub/software/scm/$PN/$P.tar.bz2.sign";

MAKEOPTS='prefix=/usr'

src_compile()
{
  # git does not include a configure script
  lndirs
  cd $B
  cygmake
}

src_install()
{
  cd $B
  cyginstall
  perl_postinst
}

# Local Variables:
# fill-column: 72
# mode: sh
# sh-indentation: 2
# End:
diff -urN -x CYGWIN-PATCHES -x 'aclocal.m4*' -x ltmain.sh -x 'config.*' -x 
depcomp -x install-sh -x missing -x mkinstalldirs -x autom4te.cache -x 
'*compile' -x Makefile.in.in -x 'intltool*.in' -x 'xml-i18n-*.in' -x '*.pyc' -x 
'*.mo' -x '*.gmo' -x ABOUT-NLS -x Makevars.template -x COPYING -x INSTALL -x 
mdate-sh -x '*.orig' -x '*.rej' -x '*~' -x '*.temp' -x texinfo.tex -x ylwrap -x 
configure -x gnome-doc-utils.make -x gnome-doc-utils.m4 -x intltool.m4 -x 
omf.make -x xmldocs.make origsrc/git-1.4.4.1/Makefile src/git-1.4.4.1/Makefile
--- origsrc/git-1.4.4.1/Makefile2006-11-22 20:38:07.0 -0600
+++ src/git-1.4.4.1/Makefile2006-11-27 21:37:38.748875000 -0600
@@ -369,11 +369,8 @@
 endif
 ifeq ($(uname_O),Cygwin)
NO_D_TYPE_IN_DIRENT = YesPlease
-   NO_D_INO_IN_DIRENT = YesPlease
NO_STRCASESTR = YesPlease
-   NO_SYMLINK_HEAD = YesPlease
NEEDS_LIBICONV = YesPlease
-   NO_C99_FORMAT = YesPlease
# There are conflicting reports about this.
# On some boxes NO_MMAP is needed, and not so elsewhere.
# Try uncommenting this if you see things break -- YMMV.
@@ -769,7 +766,7 @@
 
 perl/Makefile: perl/Git.pm perl/Makefile.PL GIT-CFLAGS
(cd perl && $(PERL_PATH) Makefile.PL \
-   PREFIX='$(prefix_SQ)')
+   PREFIX='$(prefix_SQ)' INSTALLDIRS=vendor)
 
 doc:
$(MAKE) -C Documentation all

--
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: Problem with /usr/sbin/sendmail ==> /usr/bin/exim

[René Berber]

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 6.4-1 .
-- 
René Berber


--
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: 1.5.22: Error from anything using the cygwin dll

[Hugh McMaster]

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
Outpost Firewall and the problem starts. Once I had uninstalled the
software, the problem disappears.  According to the Agnitum Forums,
the developers are working on a solution to the problem.

A workaround is to uninstall version 4 of the firewall, and install
version 3.51.  This will provide firewall protection for the computer,
while allowing the use of Cygwin as well.

Hope this helps,

Hugh


On 28/11/06, Mikkel Erup wrote:

Could someone advice on how to debug this further. Maybe a
link or something.
I need to get the NFS server running


--
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: Installation problem(?) for grace: HOW DO I GET old xorgs?

[moka]

Αρχικό μήνυμα από  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 cmd.exe. Naturally cygwin links only
> work in a cygwin shell. bash, ash, zsh, tcsh, ... pick your poison.
> 
> > was that the directory for  cygX11R6.dll was not in the path. I fixed that
> and
> > also put the actual path for gracebat
> Well, using cygwin.bat would have solved that for you too. (And would
> have given you a nice bash prompt.)


> 
> > . c:cygwinusrsharegracebin before c:cygwinbin, so  a command would look
> Looks really funny, you lost your backslashes in the mail ;)
> 
> > for the actual executables
> >  before the symlinks. 
> > So I run
> > c:mydir> c:cygwinusrsharegracebingracebat test.dat -hdevice JPEG
> > -printfile gtest.jpg
> > or
> > c:mydir> gracebat test.dat -hdevice JPEG -printfile gtest.jpg
> > 
> > It runs instantly, but produced NO file gtest.jpg
> > 
> > (Before adding the actual executable directory to the path before the bin,
> it
> > just hung there)
> > 
> > 
> > Also, if I try to run grace by clicking on its icon(not the symlink), it
> does
> > nothing
> > If I run
> > c:mydir> grace
> > it does nothing
> No wonder, half of it's paths are missing. Start it from a shell ...
> 
> > 
> > but if I do
> > c:mydir> ash
> > 
> > $grace
> >  I get back 
> > grace>1
> 
> like you did here.
> 
> > If I do 
> > c:mydir> xmgrace
> > I get  Can't open display
> > Failed initializing GUI, exiting
> > 
> > So, it looks like an X-problem. How do I go about  solving it?Αρχικό μήνυμα
> από
> 
> The X-problem seems to be that the X-server is not running. Try using
> startxwin.bat. (This one actually works if you "click" on it.) *shudder*
> 
>   Volker
> 
> 
> -- 
> PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
> key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D
> 
> 

So the bottom line is I should run this from a bash prompt. Here is what I am
afraid of: The script actually running and calling gracebat is a (n
Activestate) perl script
 that interfaces with an Oracle database via DBI and DBD:Oracle. This
 was a pain to install and  is using MS-VisualC++. So with cygwin
 I should go all out cygwin, i.e. use cygwin's Perl, not activestate's, hope
that cygwin's perl includes DBI and DBD-Oracle and  run everything from a bash
prompt. If other windows processes run at the same time(for instance other perl
scripts), that's fine. Am I understanding this right?


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

Updated (and new) cygport patches

[Charles Wilson]

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 patch
(2) split out the portion of the relocatable patch that deals
with packages having postinstall/preremove scripts that "go with"
packages other than the main.
(3) relocation part of relocatable patch (new: dorelsym script)
(4) autoconf-2.61 support

--
Chuck


=

(1) Updated mixed download protocol patch (original here:
http://cygwin.com/ml/cygwin/2006-11/msg00137.html )
against CVS latest.

2006-11-28 Charles Wilson <...>

* bin/cygport.in (src_fetch_auto): new function. Autodetects
protocol of passed-in URI (mirror|http|ftp) and errors if
no recognized protocol detected
(src_fetch_auto_warn): new function. Autodetects protocol
of passed-in URI (mirror|http|ftp) and issues a warning if
no recognized protocol detected
(src_fetch): call src_fetch_auto_warn for 2nd..Nth SRC_URI
regardless of download method (cvs|svn|git|mirror|http|ftp)
of first SRC_URI.  If !(cvs|svn|git), call src_fetch_auto
for first SRC_URI -- which will error if first SRC_URI's
protocol is unrecognized.
(src_prep_init_hook): new function. no-op.
(src_prep_fini_hook): new function. no-op.
(src_prep): call src_prep_init_hook and src_prep_fini_hook.


* lib/cvs.cygclass: extract first name from SRC_URI and use that
to generate tarball name. Ensure that working directory is
unchanged by a call to cvs_fetch.
* lib/svn.cygclass: extract first name from SRC_URI and use that
to generate tarball name. Ensure that working directory is
unchanged by a call to svn_fetch.
* lib/git.cygclass: extract first name from SRC_URI and use that
to generate tarball name. Ensure that working directory is
unchanged by a call to git_fetch.

=

(2) split out the portion of the relocatable patch (original here:
http://cygwin.com/ml/cygwin/2006-10/msg00743.html ) that deals
with packages having postinstall/preremove scripts that "go with"
packages other than the main.  (e.g. gettext has no postinstall,
but gettext-devel does)

2006-11-28 Charles Wilson <...>

* bin/prep_gnu_info.sh: allow cygport client to suppress
automatic install-info (useful if: subpackages each have own
explicit postinstall scripts, and each subpackage "owns"
certain info files.  To activate *suppression*, set
SUPPRESS_AUTOMATIC_INSTALLINFO to non-empty.  Default behavior
is unchanged from current.
* bin/cygport.in (__prepetc): allow ${C}/${PN}.postinstall
and ${C}/${PN}.sh as synonyms for ${C}/postinstall.sh (however,
presence of more than one of these causes error message).
Allow ${C}/${PN}.preremove as synonym for ${C}/preremove.sh
(but presence of both causes error message).  Allow for
${C}/${pkg_name[${n}]}.postinstall and/or
${C}/${pkg_name[${n}]}.preremove [n > 1].

=

(3) relocation part of relocatable patch (original...see link above)

NEW FILE: bin/prep_relocated_libtool_la.sh
   make sure that .la files don't have references to their
   temporary --prefix.

NEW FILE: lib/relocatable.cygclass
   mainly just "turns on" the relocation support (and "turns off"
   /usr/lib/cygports/bin/ that don't have appropriate support.

NEW FILE: bin/dorelsym
   automagically computes relative path between two absolute paths
   and creates a relative symlink.  That is:
   dorelsym ${D}/usr/share/terminfo ${D}/usr/lib/terminfo
   will do
   (cd ${D}/usr/lib && ln -fs ../share/terminfo terminfo)
   This is important when variables appear in the target and symlink
   names, and you don't know the true relative path a priori.

2006-11-28 Charles Wilson <...>

* bin/Makefile.am: add new files prep_relocated_libtool_la.sh
and dorelsym
* bin/prep_relocated_libtool_la.sh: new file
* lib/Makefile.am: add new file relocatable.cygclass
* lib/relocatable.cygclass: new file
* bin/cygport.in (_ENABLE_RELOCATION): new global variable
(_RELOCDIR): new global variable
(__init_relocation): new function
(__check_relocation): new function
(__maybe_relocate): new function (main hook for relocatation
support, called by other cygport functions)
(cygconf): Add support for ${_RELOCDIR} and --enable-relocatable
(docinto): Add support for ${_RELOCDIR}
(exeinto): Add support for ${_RELOCDIR