cygwin1.dll

cygwin1.dll

[flav astraud]

hello,

I would like to make an exe containing the dll. that could work
without the cygwin1.dll

thanks
-- 
flav

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[MarketLogix]

[-- Attachment #1: Type: text/plain, Size: 22 bytes --]

application/nextmail


[-- Attachment #2: bin00000.bin --]
[-- Type: text/plain, Size: 1704 bytes --]

begin 600 .tar.475.cygwin1_dll.attach
M'YV0+EX`&$BPH,&#"!,J7,BPH4.$(&C`N%&C!@@`(#+&H$'C8L:/,#Q^')DQ
M)(@;,6K<@!%CA@P:-C[>D!$C!L8:#W/JW,FS)X`Z<^B$D9,10!LV>'PJO(.F
M3!DV2J-*G4JUJM6K#].X(5,&CPLY=,Q@'4L60`P8,&QP%`EB8T>,(T/")2F#
MYHR,*%6R=$G#8MN),S'"*$NX\,^@0XL>37J5J5.HAB-+GDQYJH(G3Z#,80$B
M"0@R;]R<H`."#AJM:TJC"4/:=)D\(%`,R7/&#=`4(.Z\J<.&C`(V:=:44<T:
MA)TR<F"WJ3,&#8@0T$'L2*%`@9@T<]94%U+FC%809M[(N3.4*QD0;<K,F1/F
M3!D=U9N$20/<S9D63+#3T0%B3&BA8Y`V!FUW:-5"4VS``<0<N\DQ1AGDR5&&
M"P/6!A2%;[2Q`PARU.$&"&+`5H8>1[6A0'Y!M5"%&W/4(<8<8\B1AACO@<!#
M&_.Q0<<;.E18H!LM>-CBBS'.6$8+B_7`GAM?R8%A&PLV^.`<7Y5!QFIT/.G#
MB?JU,(6+,,I((W\WYKACCP0:.&281D99AX/J57DE:UIRF6(0#IYV')EHT$$'
M'#J\\`*#;TXI)Y9/OG#4"SYJ]<*6*-+1`A1O!$4FCO2=V:@;;L))I81S9NE?
M&Y!VB<13@-J(J8X\;GH@JIT:"BJBH_K`&0]]_AGHH%+&.2N=HRK*Q@LCF!%&
M''-L.4496R''GZMOW.$&<K'Z:B6M&2I`Q%-I'`=J"U3PB%Z.6IT!`G!!]9<F
MIX1Z>BBPV1HA1X;\F<%&&':`$$90<H11QWD\V(NO"_O2T>^_0)0!1QI"N6"&
M',JZJ$89`3Z[;@PND,$&&PJ$:_$9/U8;X805VD;EJ-JR5N.7;G!V%@C+P@&"
M#&B%%,,-.L0@@PXSY`#""C6'A,(135!!W1-RG!&&&VGHP5H:H?%7Q,)"Q28O
ML\V!,$2&<-1!!W(PCY$&UL/!B,8;;[!Q-!S(/6V?EWD$548;_'%EAE8,/P5;
M%4XD@84"E"+&1@M!D$&&A.OQMQ&'=0QG1]I"I2$A9SG0(,-*(*PAX5'?73>&
M-P:7H8`1'@8(M1O\;=U&UU\3-8789,-,Q[_,TJ$`%BW(1Y^S(!3!1!,@;.'M
M'*?/[()%4#`Q0Q?5(<C&&RQ4YYENO)T'G'"EO3$N]DN#T-5P_KD1.=/VJ3:<
MQFRX0)R`N_66FWC:%6C:;JTUI2[(6F&,?G6F+;W&'`IH00M`H`"!V:$Z`E3`
M%9;6&NT)"4Q%HA%XYM4&U6#G7/KY@0*6M15]H4<]['%/]N[WHR"Q"()B*H/(
MAD(RVICL2=510&5F2,,:VO"&.,RA#G?(PQ[Z\(=`#*(0ATC$(AKQB$A,HA*7
MR,0F.O&)4(RB%*=(Q2I:\8I8S*(6M\C%+GKQBV`,HQC'2,8RFO&,:$RC&M?(
MQC:Z\8UPC*,<YTC'.MKQCGC,HQ[WR,<^^O&/@`RD(`=)R$(:\I"(3*0B%\G(
$1CHRB(UP
`
end

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[gothrg]

All,

I hope someone can help me with this error.  It is getting highly annoying
to restart my laptop when this happens.  It is when I am using cygwin
commands in DOS that normally messes it up.

I have followed these instructions from the error below and have found that
I only have 1 cygwin1.dll file.  I could have sworn that I DL'd the newest
version of cygwin earlier this year already.

I there a way to tell windows when to use dos and when to use cygwin since
it can't seem to figure it out on it's own.

Regards,

Mike


    983 [main] ? (3676)
C:\cygwin\home\liguori\VendorCode\julius-3.5.2-quickstar
t-windows\bin\julian.exe: *** fatal error -
C:\cygwin\home\liguori\VendorCode\ju
lius-3.5.2-quickstart-windows\bin\julian.exe: *** system shared memory
version m
ismatch detected - 0x8A88009C/0x75BE009C.
This problem is probably due to using incompatible versions of the cygwin
DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
-- 
View this message in context: http://old.nabble.com/cygwin1.dll-tp28232579p28232579.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: cygwin1.dll

[Dave Korn]

On 13/04/2010 17:19, gothrg wrote:

> I hope someone can help me with this error.  It is getting highly annoying
> to restart my laptop when this happens.  It is when I am using cygwin
> commands in DOS that normally messes it up.
> 
> I have followed these instructions from the error below and have found that
> I only have 1 cygwin1.dll file.  I could have sworn that I DL'd the newest
> version of cygwin earlier this year already.

  But then what is "julius-3.5.2-quickstart-windows"?  It's not the usual
place for a Cygwin installation... it does sound like you have two of them,
one shipped as part of whatever julius is (presumably a port of something from
linux)?

    cheers,
      DaveK


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

Re: cygwin1.dll

[gothrog]

>  But then what is "julius-3.5.2-quickstart-windows"?  It's not the usual
>place for a Cygwin installation... it does sound like you have two of them,
>one shipped as part of whatever julius is (presumably a port of something
from
>linux)?

julius is an open source speech recognition tool.  If you want to know more
about it here is the site
www.voxforge.com

You might have a point about that, even though it isn't a cygwin component. 
I may to need install the windows build on the C: drive.  This may just be
avoiding a problem then fixing it.  I do still get this error if I do linux
commands such as 'ls' in dos.  I noticed that once I get this error and
cygwin wasn't opened already, I can't launch a cygwin terminal.  The
terminal appears quickly and disappears.

Mike



Dave Korn-6 wrote:
> 
> On 13/04/2010 17:19, gothrg wrote:
> 
>> I hope someone can help me with this error.  It is getting highly
>> annoying
>> to restart my laptop when this happens.  It is when I am using cygwin
>> commands in DOS that normally messes it up.
>> 
>> I have followed these instructions from the error below and have found
>> that
>> I only have 1 cygwin1.dll file.  I could have sworn that I DL'd the
>> newest
>> version of cygwin earlier this year already.
> 
>   But then what is "julius-3.5.2-quickstart-windows"?  It's not the usual
> place for a Cygwin installation... it does sound like you have two of
> them,
> one shipped as part of whatever julius is (presumably a port of something
> from
> linux)?
> 
>     cheers,
>       DaveK
> 
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/cygwin1.dll-tp28232579p28233313.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Cygwin1.dll

[Brian Dessent]

Reply to the mailing list, not to me.

sroberts82@yahoo.com wrote:

> Hi Brian thank you very much for your answer.
> Why then, when I build with borland say, there is no such dependancy and I can just give that exe to anyone and it just works?

It still has a dependency on a C runtime library, it's just that that
library MSVCRT.DLL happens to be already installed in your Windows
directory so you can pretend that it's not there if you squint hard
enough.  You can achieve the same thing with gcc by using MinGW.  But as
I already said, this means using only the functions and APIs that
Windows provides, which means no POSIX emulation.

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/

Cygwin1.dll

[sroberts82]

Hi,
Can someone help me understand this, its probably really straightforward but
I can't find an answer for this. 
Why is it when I build the most basic helloworld.exe and try and run it I
get told of a dependancy on cygwin1.dll? Why do I need this dll, and what
how do I build to avoid needing this? 
Thanks.
Stephen
-- 
View this message in context: http://www.nabble.com/Cygwin1.dll-tf4734709.html#a13539592
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: Cygwin1.dll

[Brian Dessent]

sroberts82 wrote:

> Can someone help me understand this, its probably really straightforward but
> I can't find an answer for this.
> Why is it when I build the most basic helloworld.exe and try and run it I
> get told of a dependancy on cygwin1.dll? Why do I need this dll, and what

When you build that program that calls printf("hello world"), where do
you think that implementation of printf comes from?  On linux you have a
libc.so, on Cygwin you have a cygwin1.dll, they are analogous.

> how do I build to avoid needing this?

You don't.  Or you use something other than Cygwin.

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: Cygwin1.dll

[Charles D. Russell]

Brian Dessent wrote:
> sroberts82 wrote:
> 
>> Can someone help me understand this, its probably really straightforward but
>> I can't find an answer for this.
>> Why is it when I build the most basic helloworld.exe and try and run it I
>> get told of a dependancy on cygwin1.dll? Why do I need this dll, and what
> 
> When you build that program that calls printf("hello world"), where do
> you think that implementation of printf comes from?  On linux you have a
> libc.so, on Cygwin you have a cygwin1.dll, they are analogous.
> 
>> how do I build to avoid needing this?
> 
> You don't.  Or you use something other than Cygwin.
> 

Not as drastic as it sounds.  Look at the compiler flag -mno-cygwin. 
Very handy if you occasionally want to distribute executables without 
cygwin1.dll.


--
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: Cygwin1.dll

[Brian Dessent]

"Charles D. Russell" wrote:

> > You don't.  Or you use something other than Cygwin.
> 
> Not as drastic as it sounds.  Look at the compiler flag -mno-cygwin.
> Very handy if you occasionally want to distribute executables without
> cygwin1.dll.

That would fall under "use something other than Cygwin" because you are
not using Cygwin any more in that case, you are using MinGW.  This means
you can't use any POSIX emulated functions.

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: cygwin1.dll

[Larry Hall (Cygwin)]

On 10/10/2005 03:58 PM, SaSHa SHokovic wrote:
> im new in this mailing list, so i dont have any archyve about this
> problem. I want to use XWin.exe and im getting that where is no
> cygwin1.dll, i reinstalled it, bet it didnt help. Is there any procedure
> how can  i solve it?


Yes.  Read and follow the problem reporting guidelines at:

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

You should also make use of the documentation provided at:

> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/

Please note that this isn't a Cygwin X issue but rather an install/general
Cygwin issue.  If you follow-up on this thread, please remove the 'cygwin-
xfree' address from your replies.  I've set the Reply-To field to follow-up
to the appropriate list.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (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/

cygwin1.dll

[Виталий Стасюк]

cygwin-1.5.13-1

give me "cygwin1.dll" plz


--
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: cygwin1.dll

[Brian Dessent]

Âèòàëèé Ñòàñþê wrote:

> cygwin-1.5.13-1
> 
> give me "cygwin1.dll" plz

This list only supports installations of Cygwin done with the setup.exe
installer from cygwin.com.  If you used that you'd have cygwin1.dll
already, so it's likely that you're using someone else's packaged
binaries.  Ask them.

If you just want the DLL it's available from any of the cygwin mirrors
in the "cygwin" package, or in snapshot form on cygwin.com.

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: cygwin1.dll

[Christopher Faylor]

On Fri, Jul 09, 2004 at 09:49:46PM -0500, Joshua Halls wrote:
>Yes it is open source (not GPL but the source code is freely available for
>no fee of any kind, it is DIKU derived).  
>
>The whole point of releasing this is for people who would never download or
>touch cygwin (or code for that matter) to simply run on their machines for
>building/testing purposes.  Anyway, thanks for the information.

The GPL doesn't really care why you are releasing the software.  If you
provide the cygwin*-src.tar.bz2 archive you should be fine.

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

cygwin1.dll

[Joshua Halls]

Yes it is open source (not GPL but the source code is freely available for
no fee of any kind, it is DIKU derived).  

The whole point of releasing this is for people who would never download or
touch cygwin (or code for that matter) to simply run on their machines for
building/testing purposes.  Anyway, thanks for the information.

--Josh

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.716 / Virus Database: 472 - Release Date: 7/5/2004
 


--
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: cygwin1.dll

[jim.a.davidson]

Igor,
Thanks for this info.
The only Cygwin executables being installed will be those to support OpenSSH
on 
that machine e.g. ssh-keygen,scp,sftp etc.
I still do not have a clear understanding of how a user could "hijack" a
cygwin process
running as system account,effectively bypassing system security.
Any info. would be most appreciated.
Thanks. 


> Best Regards
> Jim 
> 		_______________________________________________
> 		BTcd  Computing Partners
> 		Intelligent Systems Management            



-----Original Message-----
From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
Sent: 24 January 2003 16:36
To: Davidson,JA,Jim,YES82 R
Cc: cygwin@cygwin.com
Subject: Re: cygwin1.dll


On Fri, 24 Jan 2003 jim.a.davidson@bt.com wrote:

> Sirs,
> We are proposing to use the Red Hat OpenSSH package on our NT/W2K servers
> but some concerns
> have been raised re. the Cygwin1.dll shared memory vulnerability.
> As the only Cygwin application running on these machines will be OpenSSH I
> am not sure how
> significant a risk may exist.
> Can you please explain how this vulnerabilty could be exploited so that we
> can determine
> what if any counter measures we could deploy.
> Thanks.

Jim,

I'd like to correct one misconception in your message.  You said that
OpenSSH (I assume you mean sshd) will be "the only Cygwin application
running on these machines".  However, any time a user logs on, sshd will
spawn a shell, and that will spawn whatever other applications the user
runs.  Some of them will most certainly be Cygwin applications.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[jim.a.davidson]

Sirs,
We are proposing to use the Red Hat OpenSSH package on our NT/W2K servers
but some concerns
have been raised re. the Cygwin1.dll shared memory vulnerability.
As the only Cygwin application running on these machines will be OpenSSH I
am not sure how
significant a risk may exist.
Can you please explain how this vulnerabilty could be exploited so that we
can determine
what if any counter measures we could deploy.
Thanks.

> Best Regards
> Jim 
> 		_______________________________________________
> 		BTcd  Computing Partners
> 		Intelligent Systems Management               
> 
> 	     _______________________________________________
 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin1.dll

[Igor Pechtchanski]

On Fri, 24 Jan 2003 jim.a.davidson@bt.com wrote:

> Sirs,
> We are proposing to use the Red Hat OpenSSH package on our NT/W2K servers
> but some concerns
> have been raised re. the Cygwin1.dll shared memory vulnerability.
> As the only Cygwin application running on these machines will be OpenSSH I
> am not sure how
> significant a risk may exist.
> Can you please explain how this vulnerabilty could be exploited so that we
> can determine
> what if any counter measures we could deploy.
> Thanks.

Jim,

I'd like to correct one misconception in your message.  You said that
OpenSSH (I assume you mean sshd) will be "the only Cygwin application
running on these machines".  However, any time a user logs on, sshd will
spawn a shell, and that will spawn whatever other applications the user
runs.  Some of them will most certainly be Cygwin applications.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[Bob Carruthers]

I down loaded the initial cygwin offering, installed it,
and then tried to run it.  I got the message back that
the cygwin could not find cygwin1.dll, and although it's
in the software list, it does appear on the list generated
by setup.  Is it somewhere I haven't yet found, or do I
have to load it specially.  I used the download, followed
the install from disk option.

Regards, Bob Carruthers

-- 

Bob Carruthers
Applications Consultant
Cray UK Ltd

2 Brewery Court
High Street
Theale
Reading
Berks
RG7 5AH

Email: crjrc@cray.com

Mobile:         +44 (0)7710 570962
Home Office:    +44 (0)1304 389305
Home Fax:       +44 (0)1304 389304
Office Fax:     +44 (0)118 903 3208/9

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[S.T. Cheok]

I would like to find out the reason why I can't run any .exe files in 
dos prompt after installing cygwin especially those compiled with 
cygwin. It says cygwin1.dll missing. What does that mean 
and how do I fix that? I'm using Windows 98 currently. Thank you..

donald

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin1.dll

[Collin Grady]

     Have you tried rebooting to make sure that cygwin1.dll is in your path?
I've found that it isn't always updated without a reboot.
     -Collin Grady

Democracy: The bludgeoning of the people, by the people, and for the people

----- Original Message -----
From: "S.T. Cheok" <een1stc@ECU-01.NOVELL.LEEDS.AC.UK>
To: <cygwin@sourceware.cygnus.com>
Sent: Monday, December 10, 2001 5:42 AM
Subject: cygwin1.dll


> I would like to find out the reason why I can't run any .exe files in
> dos prompt after installing cygwin especially those compiled with
> cygwin. It says cygwin1.dll missing. What does that mean
> and how do I fix that? I'm using Windows 98 currently. Thank you..
>
> donald
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[Amoediun Trepcoze]

where can I download just the lastest cygwin1.dll?
or can u email it to me?please?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin1.dll

[Ronald Landheer]

Go to www.cygwin.com and click on "install Cygwin now". This will download
the setup program, which will set up a Cygwin environment for you, wit
whatever you select and it's dependencies - including but not exclusively
cygwin1.dll

If you need it for a program that relies on it, but does't supply it, ask
the author.

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Amoediun Trepcoze
> Sent: woensdag 5 december 2001 15:25
> To: cygwin@cygwin.com
> Subject: cygwin1.dll
>
>
> where can I download just the lastest cygwin1.dll?
> or can u email it to me?please?
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 08:21 PM 8/27/2001, Neil Lunn wrote:
>I'd like to know what peoples exact facination with putting cygwin1.dll in
>their Windows system directory is anyway. This should only ever be needed
>when programs are launched independantly of a shell like bash. Mostly things
>like inetd "as a service" which you can't do on Win98 anyway.

I too am fascinated by the many people who's proclivity is to short-circuit
the install program (setup.exe) and move (or put a copy of) cygwin1.dll
into the Windows system directory.  I take exception with your caveat that
it is necessary to do this to launch programs independently of bash.  It 
is *not*.  One can always add the Cygwin bin directory to their Windows 
path (preferably at the front but if you know what you're doing, put it 
anywhere in the list).  Copying or moving cygwin1.dll to any directory is
an action that creates an unsupported installation.  If you're willing to
accept the fact that the list will not spend time helping you with problems
with your custom installation, then I see no problem with doing as you see
fit.  However, it should be clear that this list overwhelmingly rejects 
the notion of custom installations, for sanity sake.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin1.dll

[Neil Lunn]

>-----Original Message-----
>From: Ivan Petrovich [ mailto:cavatina@vayu.niar.twsu.edu ]
>Sent: Tuesday, August 28, 2001 10:26 AM
>To: Neil Lunn
>Subject: Re: cygwin1.dll
>
>
>Neil Lunn a e'crit:
>
>> Look under the Advanced Tab from the properties my "My 
>Computer". There is a
>> section on environment variables. You want to change PATH.
>> 
>
>I couldn't find the Advanced Tab there. I have Windows 98. Sorry, I'm
>not familiar with Windows. (That's why I'm using cygwin.) :)
>
>If you can suggest another place to look for the Advanced Tab, I'd
>appreciate it.
>
>Thanks

Probably becuase of the original question mentioning Windows ME is why I
said this. Look around and I'm sure you'll find it. It can't hurt to
understand a little bit about windows, otherwise why use it?

I'd like to know what peoples exact facination with putting cygwin1.dll in
their Windows system directory is anyway. This should only ever be needed
when programs are launched independantly of a shell like bash. Mostly things
like inetd "as a service" which you can't do on Win98 anyway.

--Neil
> 
>

__________________________________________________________________________
Please Note :
Only  the intended recipient is authorised to access or use this e-mail.
If you are not the intended recipient, please delete this e-mail and notify
the sender immediately. The contents of this e-mail are the writer's 
opinion and are not necessarily endorsed by the Gunz Companies
unless expressly stated.

We use virus scanning software but exclude all liability for viruses or
similar in any attachment.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin1.dll

[Ivan Petrovich]

Neil Lunn a e'crit:

> Probably becuase of the original question mentioning Windows ME is why I
> said this. Look around and I'm sure you'll find it. It can't hurt to
> understand a little bit about windows, otherwise why use it?

Thanks. I did look, but will look more. :)

> 
> I'd like to know what peoples exact facination with putting cygwin1.dll in
> their Windows system directory is anyway. This should only ever be needed

The reason is as follows. I am given a Window 98 machine at work to
perform certain tasks. I am not at liberty to make any major changes
to the OS installation or the software. However, I decided to install
cygwin so I can have tools in addition to what's there. And I have
thus far found it useful to be able to run little sed scripts, using
grep, etc. So I started building a collection of tools for what I
do. But it's best that I not write them as shell scripts since I am
the only one at work who has cygwin installed. For the sake of sharing
my tools with others, I've decided to write them in C. However,
the C programs compiled with gcc under cygwin won't run outside of
cygwin unless it can find the dll, hence my original question. Even if
I end up having to install cygwin on all the machines at work to be
able to run these programs, it would still be beneficial to run them
without starting the cygwin shell window because my coworkers don't
care to use bash or tcsh. All they want is to run the programs.

As for "why use it", not everyone uses computers by choice. :)

Thanks a lot again. Regards. :)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin1.dll

[Christopher Faylor]

On Wed, Aug 29, 2001 at 12:50:01AM -0600, Ivan Petrovich wrote:
>Neil Lunn a e'crit:
>> I'd like to know what peoples exact facination with putting cygwin1.dll in
>> their Windows system directory is anyway. This should only ever be needed
>
>The reason is as follows. I am given a Window 98 machine at work to
>perform certain tasks. I am not at liberty to make any major changes
>to the OS installation or the software.

And putting random DLLs in your system directory isn't considered a
major change?

>However, the C programs compiled with gcc under cygwin won't run
>outside of cygwin unless it can find the dll, hence my original
>question.  Even if I end up having to install cygwin on all the
>machines at work to be able to run these programs, it would still be
>beneficial to run them without starting the cygwin shell window because
>my coworkers don't care to use bash or tcsh.  All they want is to run
>the programs.

There is no reason to start bash just to run a cygwin executable.  You
are going to put your programs in a directory.  Put cygwin1.dll in the
same directory.

Problem solved.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin1.dll

[Neil Lunn]

>-----Original Message-----
>From: Jinbo Huang [ mailto:jinbo@CS.UCLA.EDU ]
>Sent: Thursday, August 23, 2001 1:11 PM
>To: cygwin@cygwin.com
>Subject: cygwin1.dll
>
>
>After installing the Cygwin package (on Windows ME) do I need 
>to manually
>place the cygwin1.dll in my Windows/System32 dir? cuz the 
>installation does
>not seem to have done it.

!!!!!!DONT DO THAT!!!!

If you need cygwin1.dll to be in your path add the directory where it is
installed to you path.


--Neil

>
>JH
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>

__________________________________________________________________________
Please Note :
Only  the intended recipient is authorised to access or use this e-mail.
If you are not the intended recipient, please delete this e-mail and notify
the sender immediately. The contents of this e-mail are the writer's 
opinion and are not necessarily endorsed by the Gunz Companies
unless expressly stated.

We use virus scanning software but exclude all liability for viruses or
similar in any attachment.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[Jinbo Huang]

After installing the Cygwin package (on Windows ME) do I need to manually
place the cygwin1.dll in my Windows/System32 dir? cuz the installation does
not seem to have done it.

JH


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Robert Collins]

> -----Original Message-----
> From: Jonadab the Unsightly One [ mailto:jonadab@bright.net ]
> 
> # If I install a cygwin1.dll with my program, where should I 
> install it?
> # obviously in some directory that is in the *standard* path 
> for windows
> 
> That is not obvious.
> 
<snip>
> The problem you do NOT solve by this is that if the
> user tries to run your app and some other Cygwin app
> at the same time there can be problems in RAM, at
> runtime.  Order might matter, and other oddities.

Order won't matter. The presence of the dll in the same directory as the
program will cause it to be loaded first by windows. And the shared
memory area will most likely be different - thus causing a failure.
 
> # The only satisfying solution I've found personally is 
> # delivering a reduced (ought to be minimal but is not) 
> # cygwin install with my program (on the same CDROM).

Thats actually a good solution. Using setup.exe and only offering the
cygwin1.dll package (and sources) will mean that if the user has cygwin
already, setup won't install the old version, and if they install a
newer version of cygwin later, setup.exe will find the prior cygwin1.dll
because the mount table will be in the registry.
 
Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Mark Keil]

I'm curious

Just why are Microsoft's dynamic linking mechanism problematic?

And what are the implications and why do you
think that Cygwin uses dynamic linking?

Thanks, Mark


-----Original Message-----
From: Jonadab the Unsightly One [ mailto:jonadab@bright.net ]
Sent: Wednesday, July 18, 2001 11:11 AM
To: cygwin@cygwin.com
Subject: Re: CYGWIN1.DLL



# I agree 100% with most of what was written here.  In fact, I think it
# think it might even be nice to add it to the documentation.
# 
# However, I do not agree that static linking is generally a 
# universally good idea for any platform.  

I was talking about Microsoft platforms specifically, because
Microsoft's dynamic linking mechanism is problematic.  Any
platform of course may implement something (e.g., dynamic 
libraries) well or poorly.

I also understand (or think I understand) why Cygwin uses 
dynamic linking, and it doesn't bother me tremendously,
but it does have some implications -- which are really 
Microsoft's fault, but impact Cygwin nonetheless.  Some
of these implications come home to roost when we start
talking about different people distributing different
packages that are built against different versions of 
Cygwin.  There is potential there for problems.

-- 
Your font seems to be:    proportional     fixed
                                             ^
                                             |

(Fontmeter only accurate for about 90% of fonts.)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Bernard Dautrevaux]

> -----Original Message-----
> From: Andrej Borsenkow [ mailto:Andrej.Borsenkow@mow.siemens.ru ]
> Sent: Wednesday, July 18, 2001 5:09 PM
> To: Bernard Dautrevaux; cygwin@cygwin.com
> Subject: RE: CYGWIN1.DLL
> 
> 
> >
> > If I install a cygwin1.dll with my program, where should I 
> install it?
> > obviously in some directory that is in the *standard* path 
> for windows
> > programs, so probably in \WINNT\system32 (as /cygwin/bin is 
> usually NOT in
> > the path for standard windows program).
> >
> > So if I install my program AFTER cygwin, I got two 
> cygwin1.dll and if I
> > install cygwin after my program I got only one, but my 
> program probably no
> > longer run...
> >
> 
> That is what I meant. Intelligent setup that would check for 
> cygwin1.dll and
> would *not* try to install the second copy. Probably 
> remembering location in
> registry for future runs.

That would be nice, although that means that the PATH for cygwin programs
should be adjusted accordingly... (and that double-clicking on bash.exe will
probably no more work as cygwin1.dll will not be in the same place as
bash.exe, which is I think one of the reasons why ALL cygwin executables are
in the same directory mounted both as /bin and /usr/bin: have ONE
cygwin1.dll but have it everywhere a cygwin executable needs it).

> 
> Assuming that you use the same setup to install both cygwin and your
> program, that is O.K.?

Anyway using the same setup is my last option: that will also install my own
program in cygwin's /bin and so all will work EVEN if setup si not so
smart...)

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Bernard Dautrevaux]

> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
> Sent: Wednesday, July 18, 2001 4:54 PM
> To: Bernard Dautrevaux; 'cygwin@cygwin.com'
> Subject: RE: CYGWIN1.DLL
> 
> 
> At 10:10 AM 7/18/2001, Bernard Dautrevaux wrote:
> > > -----Original Message-----
> > > From: Christopher Faylor [ mailto:cgf@redhat.com ]
> > > Sent: Wednesday, July 18, 2001 7:02 AM
> > > To: cygwin@cygwin.com
> > > Subject: Re: CYGWIN1.DLL
> > > 
> > > 
> > > On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote:
> > > >yOn Tue, 17 Jul 2001, Christopher Faylor wrote:
> > > >
> 
> <snip>
> 
> 
> > > 
> > > >Probably, intelligent setup that checks for existence of 
> cygwin dll
> > > >and download/update it only if needed makes more sense.
> > > 
> > > Actually the current version of setup.exe has some 
> > > preliminary code for
> > > doing just this.
> > > 
> >
> >The problem with relying on setup to fix that (e.g. 
> suppressing any already
> >present cygwin1.dll on the system when installing cygwin) is 
> only part of
> >the problem.
> >
> >If I install a cygwin1.dll with my program, where should I 
> install it?
> >obviously in some directory that is in the *standard* path 
> for windows
> >programs, so probably in \WINNT\system32 (as /cygwin/bin is 
> usually NOT in
> >the path for standard windows program).
> 
> 
> No, it can go in the same directory as the program you're installing,

Sure, but

> although that doesn't solve the potential duplication problem.

not only it doesn't solve it but worsened it if I install several programs
in several places :-)

> 
> 
> >So if I install my program AFTER cygwin, I got two 
> cygwin1.dll and if I
> >install cygwin after my program I got only one, but my 
> program probably no
> >longer run...
> 
> 
> For the former case, this is true if the installation process 
> for your 
> program is flawed enough to ignore the existing cygwin1.dll 
> installed by 
> setup.exe.  

The problem is that cygwin can be installed *anywhere* on the system, even
on T:\quite\obscure\place :-), so finding it is not simple, then arranging
for the program to find it will require careful analysis of where
cygwin1.dll is (and which one to use if I finally find two) and where does
the PATH points then automatically modify the PATH... not so simple to say
anyone not doing this is seriously "flawed" :-)

> The latter case is still a potential issue.

Sure, and probably an important one... I don't like so much the situation
where installing a package just broke another one in some obscure way by
deleting one of its files ;-|

> 
> 
> >I think that's part of the dreadfull DLL-HELL syndrom :-)
> 
> 
> Yes, quite.
> 
> 
> >Part of the problem will be avoided if setup installed cygwin1.dll in
> >/WINNT/system32, but this had probably been over-discussed 
> already :-)
> 
> 
> 
> Yes, it has.  Putting the Cygwin path to cygwin1.dll in the 
> Windows path
> is a better solution if you need/want to use a Cygwin program in the 
> Windows environment.
> 

The problem is that is not done by setup (for obvious reasons!) so the user
has to do it manually if needed while we would all like a solution that
avoid any manual tinkering of the user environment.

> 
> >The only satisfying solution I've found personally is 
> delivering a reduced
> >(ought to be minimal but is not) cygwin install with my 
> program (on the same
> >CDROM).
> 
> 
> This works too.

Note that distributing cygwin also requires either to setup the PATH
correctly or install your programs either with setup (the cleaner way) or at
least in th esame place as cygwin binaries (which your program is anyway),
but this is I think the only real option to obtain some automatic/universal
way to setup (no pun intended) an end-user environment.

Regards,

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Bernard Dautrevaux]

> -----Original Message-----
> From: Christopher Faylor [ mailto:cgf@redhat.com ]
> Sent: Wednesday, July 18, 2001 7:02 AM
> To: cygwin@cygwin.com
> Subject: Re: CYGWIN1.DLL
> 
> 
> On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote:
> >yOn Tue, 17 Jul 2001, Christopher Faylor wrote:
> >
> >> On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote:
> >> >But, I did want to point out that there are good reasons 
> for desiring a
> >> >statically linked executable that are not in violation of 
> the cygwin
> >> >license.
> >>
> >> I don't think I've seen a good reason for this in this thread.
> >>
> >> The fact that you could have two disparate versions of the 
> cygwin DLL
> >> on your system is not, in any way, an argument for a 
> statically linked
> >> cygwin.  Conflicts between two versions of cygwin have nothing to
> >> do with the DLLness of Cygwin.
> >>
> >
> >Actually, it is very good argument *against* static linking. 
> In this case
> >nothing can help if you have two different programs linked with two
> >different versions. Somebody will have to rebuild every 
> single program
> >with new version of Cygwin as soon it is released ... nightmare.
> 
> Right!  Good point.
> 
> >Probably, intelligent setup that checks for existence of cygwin dll
> >and download/update it only if needed makes more sense.
> 
> Actually the current version of setup.exe has some 
> preliminary code for
> doing just this.
> 

The problem with relying on setup to fix that (e.g. suppressing any already
present cygwin1.dll on the system when installing cygwin) is only part of
the problem.

If I install a cygwin1.dll with my program, where should I install it?
obviously in some directory that is in the *standard* path for windows
programs, so probably in \WINNT\system32 (as /cygwin/bin is usually NOT in
the path for standard windows program).

So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
install cygwin after my program I got only one, but my program probably no
longer run...

I think that's part of the dreadfull DLL-HELL syndrom :-)

Part of the problem will be avoided if setup installed cygwin1.dll in
/WINNT/system32, but this had probably been over-discussed already :-)

The only satisfying solution I've found personally is delivering a reduced
(ought to be minimal but is not) cygwin install with my program (on the same
CDROM).

HTH

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Larry Hall (RFK Partners, Inc)]

At 10:10 AM 7/18/2001, Bernard Dautrevaux wrote:
> > -----Original Message-----
> > From: Christopher Faylor [ mailto:cgf@redhat.com ]
> > Sent: Wednesday, July 18, 2001 7:02 AM
> > To: cygwin@cygwin.com
> > Subject: Re: CYGWIN1.DLL
> > 
> > 
> > On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote:
> > >yOn Tue, 17 Jul 2001, Christopher Faylor wrote:
> > >

<snip>


> > 
> > >Probably, intelligent setup that checks for existence of cygwin dll
> > >and download/update it only if needed makes more sense.
> > 
> > Actually the current version of setup.exe has some 
> > preliminary code for
> > doing just this.
> > 
>
>The problem with relying on setup to fix that (e.g. suppressing any already
>present cygwin1.dll on the system when installing cygwin) is only part of
>the problem.
>
>If I install a cygwin1.dll with my program, where should I install it?
>obviously in some directory that is in the *standard* path for windows
>programs, so probably in \WINNT\system32 (as /cygwin/bin is usually NOT in
>the path for standard windows program).


No, it can go in the same directory as the program you're installing,
although that doesn't solve the potential duplication problem.


>So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
>install cygwin after my program I got only one, but my program probably no
>longer run...


For the former case, this is true if the installation process for your 
program is flawed enough to ignore the existing cygwin1.dll installed by 
setup.exe.  The latter case is still a potential issue.


>I think that's part of the dreadfull DLL-HELL syndrom :-)


Yes, quite.


>Part of the problem will be avoided if setup installed cygwin1.dll in
>/WINNT/system32, but this had probably been over-discussed already :-)



Yes, it has.  Putting the Cygwin path to cygwin1.dll in the Windows path
is a better solution if you need/want to use a Cygwin program in the 
Windows environment.


>The only satisfying solution I've found personally is delivering a reduced
>(ought to be minimal but is not) cygwin install with my program (on the same
>CDROM).


This works too.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Andrej Borsenkow]

>
> If I install a cygwin1.dll with my program, where should I install it?
> obviously in some directory that is in the *standard* path for windows
> programs, so probably in \WINNT\system32 (as /cygwin/bin is usually NOT in
> the path for standard windows program).
>
> So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
> install cygwin after my program I got only one, but my program probably no
> longer run...
>

That is what I meant. Intelligent setup that would check for cygwin1.dll and
would *not* try to install the second copy. Probably remembering location in
registry for future runs.

Assuming that you use the same setup to install both cygwin and your
program, that is O.K.?


-andrej


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Wed, Jul 18, 2001 at 07:08:50PM +0400, Andrej Borsenkow wrote:
>>
>> If I install a cygwin1.dll with my program, where should I install it?
>> obviously in some directory that is in the *standard* path for windows
>> programs, so probably in \WINNT\system32 (as /cygwin/bin is usually NOT in
>> the path for standard windows program).
>>
>> So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
>> install cygwin after my program I got only one, but my program probably no
>> longer run...
>>
>
>That is what I meant. Intelligent setup that would check for cygwin1.dll and
>would *not* try to install the second copy. Probably remembering location in
>registry for future runs.

Not installing cygwin1.dll could potentially mean that all of the packages that
you just installed won't work due to a reliance by the packages on newer features
in cygwin.  cygwin1.dll is supposed to be backwards api compatible but that
doesn't really apply here.

In any event, this still isn't strictly a dll issue, as you have previously
pointed out.  If the program was linked statically with an older version of
cygwin and stumbled across some registry or file system leavings from a newer
version, then there would be problems.

If you are going to be installing a program which relies on cygwin, then the
best plan would be to first check the registry for a sign of cygwin.  Then,
check the path to see if you can find a version of the DLL.  If you find it,
check the version against the version that you're using.  If it is newer, then
your application should work fine.  Otherwise, if the dll is older or if you
can't find cygwin1.dll in the path, then issue appropriate warnings.

Check cygcheck.cc for information on how to get extended version info
from cygwin1.dll.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Jonadab the Unsightly One]

# If I install a cygwin1.dll with my program, where should I install it?
# obviously in some directory that is in the *standard* path for windows

That is not obvious.

If Cygwin itself installs cygwin1.dll, it could reasonably put
it in a public place like that (although what it does instead is
at least as reasonable), but if you distribute cygwin1.dll with 
something else, the most probably place to put it is in the
directory where you install your program.  This does not solve
all of the potential problems, but it solves a couple of them:

1.  You will not accidentally overwrite the dll that Cygwin
    installed (with potentially a different version), thus
    trashing the Cygwin installation (if there is one).  A
    Cygwin upgrade will also not impact your app directly,
    in terms of files installed on the drive.  (What's in
    memory at any given time is another matter.)

2.  If the user uninstalls Cygwin, but keeps your app, it
    will still work.

3.  Since your copy of the DLL is with your app, the user
    at least knows what's what.  This is lost on clueless
    users but important for advanced users trying to track
    down conflicts.

4.  If your app's install directory is customiseable,
    users can install multiple versions of your app,
    provided they don't try to execute them simultaneously.

The problem you do NOT solve by this is that if the
user tries to run your app and some other Cygwin app
at the same time there can be problems in RAM, at
runtime.  Order might matter, and other oddities.

# So if I install my program AFTER cygwin, I got two cygwin1.dll and if I
# install cygwin after my program I got only one, but my program probably no
# longer run...

The above solves this, too.  

The unsolved problem is that it is not safe to run your 
program and another Cygwin program at the same time in
arbitrary order, unless care is taken to synchronise 
versions at every upgrade.  Welcome to the DLL Gaza.

# The only satisfying solution I've found personally is 
# delivering a reduced (ought to be minimal but is not) 
# cygwin install with my program (on the same CDROM).

Simply *requiring* cygwin (and saying "you need at least
versions such-and-such) is an option that seems to solve
most of the problems; you could include a Cygwin install
that will work for those who don't have it, but keep it
optional so that any who *have* Cygwin can skip it.

If the Cygwin DLL is fully backward-compatible, I 
think this solves pretty near all the problems.  
I think.  Probably.  Unless I'm missing something.

-- 
Your font seems to be:    proportional     fixed
                                             ^
                                             |

(Fontmeter only accurate for about 90% of fonts.)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Joshua Franklin]

Just an idea, you might just recompile the DLL with a
different registry entry and file name. That's the
only compatibility problem with having two, no?



__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Larry Hall (RFK Partners, Inc)]

At 04:12 PM 7/17/2001, Joshua Franklin wrote:
>Just an idea, you might just recompile the DLL with a
>different registry entry and file name. That's the
>only compatibility problem with having two, no?


No, as Chris and I answered earlier.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 01:12:48PM -0700, Joshua Franklin wrote:
>Just an idea, you might just recompile the DLL with a
>different registry entry and file name. That's the
>only compatibility problem with having two, no?

No.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Jonadab the Unsightly One]

# On Tue, Jul 17, 2001 at 01:12:48PM -0700, Joshua Franklin wrote:
# >Just an idea, you might just recompile the DLL with a
# >different registry entry and file name. That's the
# >only compatibility problem with having two, no?
# 
# No.

And this is a general principle (for DLLs) that transcends 
Cygwin entirely:  it is never a good idea to have two 
versions of the same DLL in any shared location on the 
same computer.  

If each application's installation routine puts its 
DLLs in the same user-specified directory where the
rest of the application's files (notably the EXEs)
are stored, and if the application deliberately 
loads them only from there, and if registry entries 
are version-specific, then a carefully-designed 
application can get away with having two versions 
installed on the same PC, as long as they aren't 
run at the same time.  Otherwise, just having two 
versions installed is a bad idea.  *Running* two 
versions of the same DLL at the same time is 
*definitely* asking for trouble.  This includes 
Microsoft DLLs such as VBRUN and MSVCRT and so on,
even if the version number is different.  (Well,
definitely if only the minor version number is
different; I'm not stone cold certain whether a
change in the major version number resolves the
problem, but I doubt it.  I think for the problem
to truly be resolved the two versions would have
to not provide any of the same functions, but
now I'm getting into technical details beyond
what I really know.)

Basically, Microsoft's implementation of dynamic
libraries is inherently broken, and there's really
nothing Cygwin (or anyone else) can do about that.
(Microsoft's DLLs may not be the only broken 
implentation of the dynamic linking concept, but 
that's either here nor there.)

RAM prices being what they are, static linking
is arguably The Only Good Way to compile anything
you want to distribute for use on Microsoft 
platforms.  However, the purpose of Cygwin is
to run Unixy stuff on Windows; producing 
software for general distribution is, AFAIK,
a non-goal for the project.  Not that I am 
intimately acquainted with the project's goals,
but that's the sense I got from the claims made
(and not made) on the website.  This is unlike
DJGPP, which definitely bills itself as a 
development environment for general use.  Of
course, there's no particular reason you can't
use Cygwin to do something that wasn't its
stated goal, but there's even less warrantee
of fitness for purpose than the "we intend
it but promise nothing" that you get if you 
use it for the intended goal.


-- 
Your font seems to be:    proportional     fixed
                                             ^
                                             |

(Fontmeter only accurate for about 90% of fonts.)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 10:42:18PM -0400, Jonadab the Unsightly One wrote:
>RAM prices being what they are, static linking is arguably The Only
>Good Way to compile anything you want to distribute for use on
>Microsoft platforms.

I agree 100% with most of what was written here.  In fact, I think it
might even be nice to add it to the documentation.

However, I do not agree that static linking is generally a universally
good idea for any platform.  There are many advantages to shared
libraries -- especially when the shared libraries are guaranteed to
be backwards compatible.

>However, the purpose of Cygwin is to run Unixy stuff on Windows;
>producing software for general distribution is, AFAIK, a non-goal for
>the project.  Not that I am intimately acquainted with the project's
>goals, but that's the sense I got from the claims made (and not made)
>on the website.  This is unlike DJGPP, which definitely bills itself as
>a development environment for general use.  Of course, there's no
>particular reason you can't use Cygwin to do something that wasn't its
>stated goal, but there's even less warrantee of fitness for purpose
>than the "we intend it but promise nothing" that you get if you use it
>for the intended goal.

Well, if you can run unix applications under Cygwin and the unix
application is intended to produce a general distribution, then Cygwin
would, by extension be intended for a general distribution.

However, the fact that the Cygwin DLL is required for programs that use
Cygwin shouldn't be too much of a surprise.  Certain shared libraries
are needed on linux, too -- even when linking statically.  Windows also
requires certain DLLs no matter how you link your program.  Think of
Cygwin as one of those DLLs.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Jonadab the Unsightly One]

# I agree 100% with most of what was written here.  In fact, I think it
# think it might even be nice to add it to the documentation.
# 
# However, I do not agree that static linking is generally a 
# universally good idea for any platform.  

I was talking about Microsoft platforms specifically, because
Microsoft's dynamic linking mechanism is problematic.  Any
platform of course may implement something (e.g., dynamic 
libraries) well or poorly.

I also understand (or think I understand) why Cygwin uses 
dynamic linking, and it doesn't bother me tremendously,
but it does have some implications -- which are really 
Microsoft's fault, but impact Cygwin nonetheless.  Some
of these implications come home to roost when we start
talking about different people distributing different
packages that are built against different versions of 
Cygwin.  There is potential there for problems.

-- 
Your font seems to be:    proportional     fixed
                                             ^
                                             |

(Fontmeter only accurate for about 90% of fonts.)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Robinow, David]

> From: Eric M. Monsler [ mailto:emonsler@beamreachnetworks.com ]
> Subject: Re: CYGWIN1.DLL
> One example:  I've written a small utility to pass a specialized
> message-format between UDP and the PC's serial port.  Its distribution
> is entirely within our company.  
> 
> I currently have both the application and the .dll checked in 
> to our CM
> tools under "utils", so that folks can run it without having cygwin
> installed on their PC.  
> 
> Only a few of us have cygwin installed, but there is a potential
> conflict problem with having two cygwin1.dll files, if the CM'd version
> lags or leads the version on any given developer's desktop.  Thus far,
> the cygwin users here are a) mostly knowledgeable enough to deal with
> the issue, and b) few enough that I can support them if the conflict
> ocurred.
  It should be possible to modify 'setup' to handle this.  I anticipate
needing something like this myself (somewhere between "soon" and
"some day".

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Robinow, David]

> From: Chris Wenk [ mailto:christophe.wenk@kuehne-nagel.com ]
> Subject: RE: CYGWIN1.DLL
> How can I distribute then an executable without the 
> cygwin1.dll ?
1) Use -mnocygwin
2) Use unix instead of Windows
3) Use a Microsoft, Borland, or somebody else's compiler

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 08:39:18AM -0400, Robinow, David wrote:
>> From: Chris Wenk [ mailto:christophe.wenk@kuehne-nagel.com ]
>> Subject: RE: CYGWIN1.DLL
>> How can I distribute then an executable without the 
>> cygwin1.dll ?
>1) Use -mnocygwin

-mno-cygwin

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

does patch.exe work different than other unx patch tools?

[Armin Theissen]

Hi, 

I searched the website for this problem, but cannot find anything 
so I want to ask you here. 

I have a patch (see attachment, supposed to patch three files down the 
directory tree) which won't work using the patch.exe tool provided with 
cygwin. However, it works perfectly with other patch.exe tools 
(UnxUtils from http://www.edv.agrar.tu-muenchen.de/~syring/win32/UnxUtils.html )
and on unix systems itself. 

I wonder what could make the patch work with the cygwin patching 
tool. 

The patch command is 'patch -b -p2'

Any ideas? 

thanks

armin



-----------------------------------------------------------------
Armin dot Theissen at sun dot com           phone +353 1 819 9080
SUN Microsystems Ireland                       (SUN intern 19080)
East Point Business Park, Boole House   Dublin 3, Rep. of Ireland 


-----------------------------------------------------------------
Armin dot Theissen at sun dot com           phone +353 1 819 9080
SUN Microsystems Ireland                       (SUN intern 19080)
East Point Business Park, Boole House   Dublin 3, Rep. of Ireland 

CYGWIN1.DLL

[Jnb ZI / Chris Wenk]

Hi there 

Is it possible to bind the runtime into the executable program instead 
of having CYGWIN1.DLL in the Windows folder.
If yes, how ?

Thanks 
Chris

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Corinna Vinschen]

On Tue, Jul 17, 2001 at 02:21:01PM +0200, Jnb ZI / Chris Wenk wrote:
> Hi there 
> 
> Is it possible to bind the runtime into the executable program instead 
> of having CYGWIN1.DLL in the Windows folder.
> If yes, how ?

No, it's not possible and please don't copy the Cygwin DLL into the
Windows folder. Just let it where it should be, in the <cygwin root>/
bin folder. You will avoid much trouble with your installation.

However, sometimes I'm wondering why people want to do this and
then I'm feeling forced to point to the licensing terms of Cygwin:

http://cygwin.com/licensing.html

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: CYGWIN1.DLL

[Chris Wenk]

How can I distribute then an executable without the 
cygwin1.dll ?
rgds
Chris

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Corinna Vinschen
Sent: 17 July 2001 02:32
To: cygwin@cygwin.com
Subject: Re: CYGWIN1.DLL


On Tue, Jul 17, 2001 at 02:21:01PM +0200, Jnb ZI / Chris Wenk wrote:
> Hi there 
> 
> Is it possible to bind the runtime into the executable program instead 
> of having CYGWIN1.DLL in the Windows folder.
> If yes, how ?

No, it's not possible and please don't copy the Cygwin DLL into the
Windows folder. Just let it where it should be, in the <cygwin root>/
bin folder. You will avoid much trouble with your installation.

However, sometimes I'm wondering why people want to do this and
then I'm feeling forced to point to the licensing terms of Cygwin:

http://cygwin.com/licensing.html

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Corinna Vinschen]

On Tue, Jul 17, 2001 at 02:39:33PM +0200, Chris Wenk wrote:
> How can I distribute then an executable without the 
> cygwin1.dll ?

You can't. And why would you like to do that? Is the resulting
code at least GPL'd? Remember to read http://cygwin.com/licensing.html .

The only way to distribute an executable without Cygwin DLL is to
not link against it, using only Mingw and native Win32 API functionality.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[James E. LaBarre]

Probably to simplify installations for end users that don't have
cygwin.  That said, I'd expect the -mingw method would *be* the simplest
for end users; if they specifically need cygwin functionality, then
including more of cygwin would be the way to go (having the added
benefit of being upgradable as new cygwin builds come out).


BTW: "Reply All" didn't work on this message, perhaps because the "To"
line was messed up on the original message?


Corinna Vinschen wrote:
> 
> On Tue, Jul 17, 2001 at 02:39:33PM +0200, Chris Wenk wrote:
> > How can I distribute then an executable without the
> > cygwin1.dll ?
> 
> You can't. And why would you like to do that? Is the resulting
> code at least GPL'd? Remember to read http://cygwin.com/licensing.html .
> 
> The only way to distribute an executable without Cygwin DLL is to
> not link against it, using only Mingw and native Win32 API functionality.
> 
> Corinna
> 
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Corinna Vinschen]

On Tue, Jul 17, 2001 at 10:40:57AM -0400, James E. LaBarre wrote:
> Probably to simplify installations for end users that don't have
> cygwin.  That said, I'd expect the -mingw method would *be* the simplest
> for end users; if they specifically need cygwin functionality, then
> including more of cygwin would be the way to go (having the added
> benefit of being upgradable as new cygwin builds come out).
> 
> 
> BTW: "Reply All" didn't work on this message, perhaps because the "To"
> line was messed up on the original message?

No, the "To:" line I'm using is by intend. That helps to get
messages only once and to keep people from sending messages
off-list.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 10:40:57AM -0400, James E. LaBarre wrote:
>Probably to simplify installations for end users that don't have
>cygwin.  That said, I'd expect the -mingw method would *be* the simplest
>for end users; if they specifically need cygwin functionality, then
>including more of cygwin would be the way to go (having the added
>benefit of being upgradable as new cygwin builds come out).

Interesting speculation, but you really can't pick and choose pieces
of cygwin when linking with -mno-cygwin.  It's an all or nothing thing.
Either use -mno-cygwin or don't.  You can't do things like "Hmm.  I
don't want cygwin's path code but I do like fork, so I'll just load
the fork part."

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[James E. LaBarre]

OK, I meant that the difference between Mingw & regular Cygwin is that
Mingw makes a simpler install for newbies, while using cygwin.dll, etc.
allows you to make use of all the other functionality of cygwin (bash,
command line utils, etc.).  It's a tradeoff of what your intended target
is.

Christopher Faylor wrote:
> 
> On Tue, Jul 17, 2001 at 10:40:57AM -0400, James E. LaBarre wrote:
> >Probably to simplify installations for end users that don't have
> >cygwin.  That said, I'd expect the -mingw method would *be* the simplest
> >for end users; if they specifically need cygwin functionality, then
> >including more of cygwin would be the way to go (having the added
> >benefit of being upgradable as new cygwin builds come out).
> 
> Interesting speculation, but you really can't pick and choose pieces
> of cygwin when linking with -mno-cygwin.  It's an all or nothing thing.
> Either use -mno-cygwin or don't.  You can't do things like "Hmm.  I
> don't want cygwin's path code but I do like fork, so I'll just load
> the fork part."

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 12:02:16PM -0400, James E. LaBarre wrote:
>OK, I meant that the difference between Mingw & regular Cygwin is that
>Mingw makes a simpler install for newbies, while using cygwin.dll, etc.
>allows you to make use of all the other functionality of cygwin (bash,
>command line utils, etc.).  It's a tradeoff of what your intended target
>is.

It's not really a tradeoff if we are talking about linking a program.
You seem to be confused between the concept of cygwin1.dll and the
cygwin distribution.  They are two different things.

The original poster wanted to build an application that didn't rely on
the Cygwin DLL.  He wasn't talking about bash, command line utils, etc.

I was trying to correct the impression that you seemed to be giving that
it was possible to pick and choose cygwin pieces while linking a program.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Eric M. Monsler]

Corinna Vinschen wrote:
> 
> On Tue, Jul 17, 2001 at 02:39:33PM +0200, Chris Wenk wrote:
> > How can I distribute then an executable without the
> > cygwin1.dll ?
> 
> You can't. And why would you like to do that?
(snip)

SPOILER: I'm not asking for a change!

One example:  I've written a small utility to pass a specialized
message-format between UDP and the PC's serial port.  Its distribution
is entirely within our company.  

I currently have both the application and the .dll checked in to our CM
tools under "utils", so that folks can run it without having cygwin
installed on their PC.  

Only a few of us have cygwin installed, but there is a potential
conflict problem with having two cygwin1.dll files, if the CM'd version
lags or leads the version on any given developer's desktop.  Thus far,
the cygwin users here are a) mostly knowledgeable enough to deal with
the issue, and b) few enough that I can support them if the conflict
ocurred.

I'm not saying that there should be a way to create a statically linked
cygwin executable.  Doing so would certainly allow, and possibly
encourage, widespread license violations.  But, I did want to point out
that there are good reasons for desiring a statically linked executable
that are not in violation of the cygwin license.


Eric

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Kurt Roeckx]

On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote:
> 
> One example:  I've written a small utility to pass a specialized
> message-format between UDP and the PC's serial port.  Its distribution
> is entirely within our company.  
> 
> I currently have both the application and the .dll checked in to our CM
> tools under "utils", so that folks can run it without having cygwin
> installed on their PC.  
> 
> Only a few of us have cygwin installed, but there is a potential
> conflict problem with having two cygwin1.dll files, if the CM'd version
> lags or leads the version on any given developer's desktop.  Thus far,
> the cygwin users here are a) mostly knowledgeable enough to deal with
> the issue, and b) few enough that I can support them if the conflict
> ocurred.

I am in about the same situation.  There are serveral PCs which
run my software.  The software is installed on the NT server, and
only one of the other PCs has cygwin installed, but the dll is
all over the place, and I'm not sure which one it will load to
start with.  I'm sure some of them are still B20.

> I'm not saying that there should be a way to create a statically linked
> cygwin executable.  Doing so would certainly allow, and possibly
> encourage, widespread license violations.  But, I did want to point out
> that there are good reasons for desiring a statically linked executable
> that are not in violation of the cygwin license.

I don't see what it would encourage license violations.  You know
give 2 files, which will be turned into 1.  You should give a
written offer for all the sources in both cases.

Anyway, I'm of the opinion the DLL should be LGPL.  It wouldn't
force us to release software under the GPL if it's linked against
it.

May I also point out that if you download the binaries, it
doesn't even say under which license it is.  After running setup
nowhere did it mention it was GPL, nor can I find any file which
says it is.  I guess that's the pain if you distribute something
binary, and not everything has the same license.

The setup program itself, under what license does that fall?
Where are the sources of it, if they are available?


Kurt


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Charles S. Wilson]

Kurt Roeckx wrote:

> 
> Anyway, I'm of the opinion the DLL should be LGPL.  It wouldn't
> force us to release software under the GPL if it's linked against
> it.
> 


You're missing the whole point.  That requirement is WHY cygwin is 
released under the GPL.  It's a feature, not a bug.  (Also, the FSF 
considers the LGPL to be a failed experiment, and no longer recommends 
its use. Ever.)  With Red Hat's Cygnus-inherited modification to the GPL 
in clause 10, the GPL allows developers of free(speech) software to 
freely use cygwin.

However, if you want to be proprietary, then you have to purchase a 
special proprietary cygwin license.  Why should someone who wants to 
hoard their code be allowed to benefit from cygwin for free(beer)? 
Makers of proprietary software, that wish to use cygwin, OUGHT to pay 
for the privelege.  Or they can open source their product, and avoid paying.

> May I also point out that if you download the binaries, it
> doesn't even say under which license it is.  


Neither does the Red Hat installer, or the Suse installer.  Why is this 
a requirement?  All packages are opensource--of various licenses--and 
the source code is provided for everything.  Not all are GPL, but most are.

> After running setup
> nowhere did it mention it was GPL, nor can I find any file which
> says it is.


That's true.  It is prominently stated on the web page, but perhaps the 
cygwin-1.3.3.tar.bz2 package should contain /usr/doc/cygwin.license or 
something.

> I guess that's the pain if you distribute something
> binary, and not everything has the same license.


So we provide the most freedom possible: all packages are supplied with 
current source, including patches (or CVS) to revert to the "official" 
version.


> The setup program itself, under what license does that fall?
> Where are the sources of it, if they are available?


GPL.  CVS, or in the cygwin-src tarball, under winsup/cinstall.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Max Bowsher]

> > The setup program itself, under what license does that fall?
> > Where are the sources of it, if they are available?
>
>
> GPL.  CVS, or in the cygwin-src tarball, under winsup/cinstall.

For some inexplicable reason, the setup.exe sources are NOT in the
cygwin-src tarball. I wish they were.

Max.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Michael A. Chase]

I just downloaded "cygwin-1.3.2-1-src.tar.gz" and the winsup/cinstall/
directory is not there.

Because it has to be able to install cygwin1.dll, setup.exe does not use
cygwin1.dll.  Its source is available in the winsup/cinstall/ directory in
CVS.  Follow the "Contributing" link at http://cygwin.com to see how to get
it.  Read the entire page a couple times before you try anything.  There is
no "setup.cc" if that is what you are looking for; the entire
winsup/cinstall/ directory is used to build setup.exe.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "Max Bowsher" <max@bowshernet.freeserve.co.uk>
To: "Cygwin Maillist" <cygwin@cygwin.com>
Sent: Wednesday, July 18, 2001 15:04
Subject: Re: CYGWIN1.DLL


> > > The setup program itself, under what license does that fall?
> > > Where are the sources of it, if they are available?
> >
> > GPL.  CVS, or in the cygwin-src tarball, under winsup/cinstall.
>
> For some inexplicable reason, the setup.exe sources are NOT in the
> cygwin-src tarball. I wish they were.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Corinna Vinschen]

On Tue, Jul 17, 2001 at 08:40:05PM +0200, Kurt Roeckx wrote:
> I don't see what it would encourage license violations.  You know
> give 2 files, which will be turned into 1.  You should give a
> written offer for all the sources in both cases.
> 
> Anyway, I'm of the opinion the DLL should be LGPL.  It wouldn't
> force us to release software under the GPL if it's linked against
> it.

The point is that software which is linked against Cygwin has to
conform with the GPL, which basically means, if you release it
publically you'll have to release your sources as well.

What is the problem with that? Nobody hinders you to make
money with your project. As long as the sources are available
according to the GPL. That's the whole point of the GPL.

The only point I can see NOT to release the sources of your
application is, that you fear another person might simply
copy your stuff and you can't make money with it.

That's ok. You can have that with Cygwin as well. You just
have to buy a proprietary Cygwin license from RH and you are
allowed to release your stuff proprietary.

> The setup program itself, under what license does that fall?
> Where are the sources of it, if they are available?

It's GPL'd and the sources are part of the Cygwin DLL source tree.
They are available e.g. in the developer snapshots and via CVS.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote:
>But, I did want to point out that there are good reasons for desiring a
>statically linked executable that are not in violation of the cygwin
>license.

I don't think I've seen a good reason for this in this thread.

The fact that you could have two disparate versions of the cygwin DLL
on your system is not, in any way, an argument for a statically linked
cygwin.  Conflicts between two versions of cygwin have nothing to
do with the DLLness of Cygwin.

I am sure that there are probably some good reasons for a statically
linked cygwin.  I'm equally sure that it is unlikely to ever happen
since all that we ever hear is from users who want developers to
make this available for them.  Since I'm not aware of any developer
for whom this is an issue, it isn't likely to ever happen.

I'd probably be reluctant to make the functionality available anyway
for the reasons that Corinna mentions.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Andrej Borsenkow]

yOn Tue, 17 Jul 2001, Christopher Faylor wrote:

> On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote:
> >But, I did want to point out that there are good reasons for desiring a
> >statically linked executable that are not in violation of the cygwin
> >license.
>
> I don't think I've seen a good reason for this in this thread.
>
> The fact that you could have two disparate versions of the cygwin DLL
> on your system is not, in any way, an argument for a statically linked
> cygwin.  Conflicts between two versions of cygwin have nothing to
> do with the DLLness of Cygwin.
>

Actually, it is very good argument *against* static linking. In this case
nothing can help if you have two different programs linked with two
different versions. Somebody will have to rebuild every single program
with new version of Cygwin as soon it is released ... nightmare.

Probably, intelligent setup that checks for existence of cygwin dll
and download/update it only if needed makes more sense.

-andrej


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: CYGWIN1.DLL

[Christopher Faylor]

On Wed, Jul 18, 2001 at 08:41:26AM +0400, Andrej Borsenkow wrote:
>yOn Tue, 17 Jul 2001, Christopher Faylor wrote:
>
>> On Tue, Jul 17, 2001 at 10:09:49AM -0700, Eric M. Monsler wrote:
>> >But, I did want to point out that there are good reasons for desiring a
>> >statically linked executable that are not in violation of the cygwin
>> >license.
>>
>> I don't think I've seen a good reason for this in this thread.
>>
>> The fact that you could have two disparate versions of the cygwin DLL
>> on your system is not, in any way, an argument for a statically linked
>> cygwin.  Conflicts between two versions of cygwin have nothing to
>> do with the DLLness of Cygwin.
>>
>
>Actually, it is very good argument *against* static linking. In this case
>nothing can help if you have two different programs linked with two
>different versions. Somebody will have to rebuild every single program
>with new version of Cygwin as soon it is released ... nightmare.

Right!  Good point.

>Probably, intelligent setup that checks for existence of cygwin dll
>and download/update it only if needed makes more sense.

Actually the current version of setup.exe has some preliminary code for
doing just this.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin1.dll

[Mark H. Siffer]

Hello

I downloaded all the binaries for cygwin and ran setup.  The installation
seemed to go fine however when I run cygwin I get the error

A required .DLL file, CYGWIN1.DLL was not found.


Any ideas?



Thanks,
Mark Siffer


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

RE: cygwin1.dll

[Robert Mcnulty junior]

When i run setup, I let it pick the binaries for me. Sources are extra and
only needed by programmers. Or developers. I still have plans of integrating
the Platform SDK into my Cygwin distributions. From what i've been hearing,
we need more than the Cygwin API, the win32api and mingw support. There are
a lot of other nifty things that Visual C++ is getting to do that we can
implement them into a new cygwin-mingw-windows format. My plan along is to
expand Cygwin capabitilies by allowing more access to Windows. Think about
it. more stability and more stuff can be added as we make this thing support
Unix and Windows. Perhaps I can design a new compiler to use with the newer
Intel/Athelon chips all from my old pc.
Get cygwin-1.3.2-1.tar.gz. You skipped it when downloading the binaries.
It does have problems downloading but only if the packages are marked
"experimental".
I've been here for over two years now. Under other email alias's.
I'm trying to get right of my yahoo accounts and sticking with my bellsouth
account.

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Mark H. Siffer
Sent: Sunday, June 17, 2001 1:33 PM
To: cygwin@cygwin.com
Subject: cygwin1.dll


Hello

I downloaded all the binaries for cygwin and ran setup.  The installation
seemed to go fine however when I run cygwin I get the error

A required .DLL file, CYGWIN1.DLL was not found.


Any ideas?



Thanks,
Mark Siffer


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Christopher Faylor]

On Sun, Jun 17, 2001 at 01:33:29PM -0500, Mark H. Siffer wrote:
>Hello
>
>I downloaded all the binaries for cygwin and ran setup.  The installation
>seemed to go fine however when I run cygwin I get the error
>
>A required .DLL file, CYGWIN1.DLL was not found.
>
>
>Any ideas?

Install the cygwin package.  Your setup was not complete.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Cygwin1.dll

[Thomas Weiss]

Hello,
we have installed Cygwin on WIN98/PC, if we want to start it,
we get the message "Cygwin1.dll was not found."
How is it possible to get this DLL and where must be placed
the DLL?

With regards and best wishes

Thomas Weiss

******************************************************
Thomas Weiss                RFT Research & Development
Atzendorfer Strasse 19      D-39418 Stassfurt
Phone: +49-(0)3925-92903-37 Mail: thomas.weiss@rft.de
******************************************************

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

RE: Cygwin1.dll

[Jean Paul Périé]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

Hi Thomas

 I have the same trouble and for workaround I hace copy the "Cygwin1.dll"
from c:\cygwin\bin to c:\windows\sysyem
 Hope this help

Jean Paul

-----Message d'origine-----
De : cygwin-owner@sources.redhat.com
[ mailto:cygwin-owner@sources.redhat.com]De la part de Thomas Weiss
Envoyé : vendredi 8 juin 2001 09:36
À : cygwin@cygwin.com
Objet : Cygwin1.dll


Hello,
we have installed Cygwin on WIN98/PC, if we want to start it,
we get the message "Cygwin1.dll was not found."
How is it possible to get this DLL and where must be placed
the DLL?

With regards and best wishes

Thomas Weiss

******************************************************
Thomas Weiss                RFT Research & Development
Atzendorfer Strasse 19      D-39418 Stassfurt
Phone: +49-(0)3925-92903-37 Mail: thomas.weiss@rft.de
******************************************************

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin1.dll

[Andrew Markebo]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

DON'T put cygwin1.dll into windows&/system.

cygwin1.dll needs to be in a subdir mantioned in the PATH-variable,
normally the cygwin.bat (c:\cygwin\cygwin.bat) sets this.

Instead of copying cygwin1.dll into windows/system, set the path to
point to c:/cygwin/bin.

        /Andy

p.s. Is this a misuse or a bug in the installation?


/ Jean Paul Périé <jpperie@atmel.fr> wrote:
| Hi Thomas
| 
|  I have the same trouble and for workaround I hace copy the "Cygwin1.dll"
| from c:\cygwin\bin to c:\windows\sysyem
|  Hope this help
| 
| Jean Paul
| 
| -----Message d'origine-----
| De : cygwin-owner@sources.redhat.com
| [ mailto:cygwin-owner@sources.redhat.com]De la part de Thomas Weiss
| Envoyé : vendredi 8 juin 2001 09:36
| À : cygwin@cygwin.com
| Objet : Cygwin1.dll
| 
| 
| Hello,
| we have installed Cygwin on WIN98/PC, if we want to start it,
| we get the message "Cygwin1.dll was not found."
| How is it possible to get this DLL and where must be placed
| the DLL?
| 
| With regards and best wishes
| 
| Thomas Weiss
| 
| ******************************************************
| Thomas Weiss                RFT Research & Development
| Atzendorfer Strasse 19      D-39418 Stassfurt
| Phone: +49-(0)3925-92903-37 Mail: thomas.weiss@rft.de
| ******************************************************
| 
| --
| Want to unsubscribe from this list?
| Check out: http://cygwin.com/ml/#unsubscribe-simple
| 
| 
| --
| Want to unsubscribe from this list?
| Check out: http://cygwin.com/ml/#unsubscribe-simple

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2322 bytes --]

At 04:02 AM 6/8/2001, Andrew Markebo wrote:
>DON'T put cygwin1.dll into windows&/system.
>
>cygwin1.dll needs to be in a subdir mantioned in the PATH-variable,
>normally the cygwin.bat (c:\cygwin\cygwin.bat) sets this.
>
>Instead of copying cygwin1.dll into windows/system, set the path to
>point to c:/cygwin/bin.


Instead of doing that, go to www.cygwin.com and click on "Install Now",
perhaps trying a different mirror than the last time.  The rule is, if
you install Cygwin and it doesn't work, your install failed.  Run 
setup.exe and see if it resolves the issue.  Generally, setup failures
result from things like network or mirror problems.  Trying again (later?)
and using a different mirror is usually the fastest, easiest, and best
solution.  This is all in the FAQ by the way ... a very fine piece of 
documentation! :-)


>p.s. Is this a misuse or a bug in the installation?


Misuse clearly.


>/ Jean Paul Périé <jpperie@atmel.fr> wrote:
>| Hi Thomas
>| 
>|  I have the same trouble and for workaround I hace copy the "Cygwin1.dll"
>| from c:\cygwin\bin to c:\windows\sysyem
>|  Hope this help
>| 
>| Jean Paul
>| 
>| -----Message d'origine-----
>| De : cygwin-owner@sources.redhat.com
>| [ mailto:cygwin-owner@sources.redhat.com]De la part de Thomas Weiss
>| Envoyé : vendredi 8 juin 2001 09:36
>| À : cygwin@cygwin.com
>| Objet : Cygwin1.dll
>| 
>| 
>| Hello,
>| we have installed Cygwin on WIN98/PC, if we want to start it,
>| we get the message "Cygwin1.dll was not found."
>| How is it possible to get this DLL and where must be placed
>| the DLL?
>| 
>| With regards and best wishes
>| 
>| Thomas Weiss
>| 
>| ******************************************************
>| Thomas Weiss                RFT Research & Development
>| Atzendorfer Strasse 19      D-39418 Stassfurt
>| Phone: +49-(0)3925-92903-37 Mail: thomas.weiss@rft.de
>| ******************************************************
>| 
>| --
>| Want to unsubscribe from this list?
>| Check out: http://cygwin.com/ml/#unsubscribe-simple
>| 
>| 
>| --
>| Want to unsubscribe from this list?
>| Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

cygwin1.dll

[Cserveni Akos]

Dear Christopher,

I want to run cygwin under win98, but my system (win98) 
asks for the cygwin1.dll file. On the www.cygwin.com 
homepage there is a link indicating, that I can download 
the dll file from there ("Latest release (DLL version 
1.3.2): ..." ). But this link points to the setup.exe file 
not for the needed dll. Could you please tell me, where can 
I find that?

Thanks in advance,

       Akos



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Kirran.Bari]

Well, I'm running an .exe program that I didn't write, in MATLAB(math
application). Somewhere in there it must refer to a Unix function that
Windows can only handle if cygwin1.dll is present.  I need to alter the
search path of the program to include the system folder (don't know why it
isn't set like that already).

Thanks for all your help.
Kirran



                                                                                                                   
                    Earnie Boyd                                                                                    
                    <earnie_boyd@        To:     Kirran.Bari@sf.frb.org                                            
                    yahoo.com>           cc:     Earnie Boyd <cygwin@cygwin.com>                                   
                                         Subject:     Re: cygwin1.dll                                              
                    02/21/01                                                                                       
                    03:56 PM                                                                                       
                    Please                                                                                         
                    respond to                                                                                     
                    Earnie Boyd                                                                                    
                                                                                                                   
                                                                                                                   



Kirran.Bari@sf.frb.org wrote:
>
> Hi again,
>
> I didn't know you could have symlinks on a PC.
>
> The file was hidden as in:  my folder options were set to hide all system
> files, so I couldn't see the file and neither could the finder.  My
program
> (which should have read the file either way) is still not finding
> cygwin1.dll, but at least now I know that it is a problem with the .exe
> file, and not your installation kit.
>

Ok.  So what and how are you trying to run?  Are you executing Cygwin
via the Desktop Icon?  Are you running the program from a DOS command
window?

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com






--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Kirran.Bari]

Hi again,

I didn't know you could have symlinks on a PC.

The file was hidden as in:  my folder options were set to hide all system
files, so I couldn't see the file and neither could the finder.  My program
(which should have read the file either way) is still not finding
cygwin1.dll, but at least now I know that it is a problem with the .exe
file, and not your installation kit.

Thanks.
Kirran




                                                                                                                  
                    Earnie Boyd                                                                                   
                    <earnie_boyd@        To:     Kirran.Bari@sf.frb.org                                           
                    yahoo.com>           cc:     Earnie Boyd <cygwin@cygwin.com>                                  
                                         Subject:     Re: cygwin1.dll                                             
                    02/21/01                                                                                      
                    01:52 PM                                                                                      
                    Please                                                                                        
                    respond to                                                                                    
                    Earnie Boyd                                                                                   
                                                                                                                  
                                                                                                                  



Kirran.Bari@sf.frb.org wrote:
>
> Earnie,
>
> You're right - the setup log says that the file was installed right in
the
> bin folder.  The file is there but just hidden.
>

Hidden?  What do you mean hidden?  Do you have symlinks for /bin or
/usr/bin?  If you do have symlinks these are known not to work with
setup.exe which is by the way a non-Cygwin executable so it 1) doesn't
understand symlinks and 2) doesn't know about the Cygwin registry wrt
actually using it to find files are concerned.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com






--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Paul Garceau]

On 21 Feb 2001, at 14:27, the Illustrious Kirran.Bari@sf.frb.org wrote:

> 
> Hi again,
> 
> I didn't know you could have symlinks on a PC.

	You can't, not on Win9x/Me.  WinNT4 is a different story.
> 
> The file was hidden as in:  my folder options were set to hide
> all system files, so I couldn't see the file and neither could
> the finder.  My program (which should have read the file either
> way) is still not finding cygwin1.dll, but at least now I know
> that it is a problem with the .exe file, and not your
> installation kit.

	You might want to find your windows explorer (might be on your 
start menu somewhere, if not, you'll likely find executable 
under Windows\system) and open it.
	There are menu bar options there to allow you to see everything 
if you want to, including .dlls; which are also considered 
"hidden" under default Win9x/ME Explorer settings (not Internet 
Explorer, or IE, but Windows Explorer) which automatically 
disable postfixes which designate things like executables (.exe) 
and Dynamically Linked Library (.dll) files.  Cygwin1.dll is a 
".dll" file.

	Peace,

		Paul G.
> 
> Thanks.
> Kirran
> 
> 
> 
> 
> 
>                     Earnie Boyd                               
>                     <earnie_boyd@        To:    
>                     Kirran.Bari@sf.frb.org                       
>                             yahoo.com>           cc:     Earnie
>                     Boyd <cygwin@cygwin.com>                     
>                               
>                                 Subject:     Re: cygwin1.dll     
>                                                           
>                     02/21/01                                01:52
>                     PM                                Please     
>                                               respond to         
>                                           Earnie Boyd            
>                                        
> 
> 
> 
> 
> 
> Kirran.Bari@sf.frb.org wrote:
> >
> > Earnie,
> >
> > You're right - the setup log says that the file was installed
> > right in
> the
> > bin folder.  The file is there but just hidden.
> >
> 
> Hidden?  What do you mean hidden?  Do you have symlinks for /bin
> or /usr/bin?  If you do have symlinks these are known not to work
> with setup.exe which is by the way a non-Cygwin executable so it
> 1) doesn't understand symlinks and 2) doesn't know about the
> Cygwin registry wrt actually using it to find files are
> concerned.
> 
> Earnie.
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> 
> 
> 
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 
> 




Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

Kirran.Bari@sf.frb.org wrote:
> 
> Hi again,
> 
> I didn't know you could have symlinks on a PC.
> 
> The file was hidden as in:  my folder options were set to hide all system
> files, so I couldn't see the file and neither could the finder.  My program
> (which should have read the file either way) is still not finding
> cygwin1.dll, but at least now I know that it is a problem with the .exe
> file, and not your installation kit.
> 

Ok.  So what and how are you trying to run?  Are you executing Cygwin
via the Desktop Icon?  Are you running the program from a DOS command
window?

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Kirran.Bari]

Earnie,

You're right - the setup log says that the file was installed right in the
bin folder.  The file is there but just hidden.

Thanks.
Kirran Bari




                                                                                                                  
                    Earnie Boyd                                                                                   
                    <earnie_boyd@        To:     Kirran.Bari@sf.frb.org                                           
                    yahoo.com>           cc:     Earnie Boyd <cygwin@cygwin.com>                                  
                                         Subject:     Re: cygwin1.dll                                             
                    02/21/01                                                                                      
                    12:14 PM                                                                                      
                    Please                                                                                        
                    respond to                                                                                    
                    Earnie Boyd                                                                                   
                                                                                                                  
                                                                                                                  



Kirran.Bari@sf.frb.org wrote:
>
> Strange.  I downloaded all the files from one of your mirror sites
> yesterday and installed them, and could not find cygwin1.dll anywhere.  I
> wrote you assuming that perhaps the file was obsolete and not part of the
> new release.
>
> (i.e.  cygwin1.dll does not show up in either the folder 'latest' or the
> installed folder 'cygwin')
>

Cygwin1.dll is a piece of a package (care to guess which one?).  For
some reason that package did not install properly.  Executing
http://cygwin.com/setup.exe again will only install what wasn't
installed yesterday.  For a clue as to what happened there exists a
setup.log.full in the same path as setup.exe that you can review.

Earnie.

P.S.: I've reset the reply to back to the list and have CC'ed them on
the discussion for your convenience.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com






--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

Kirran.Bari@sf.frb.org wrote:
> 
> Earnie,
> 
> You're right - the setup log says that the file was installed right in the
> bin folder.  The file is there but just hidden.
> 

Hidden?  What do you mean hidden?  Do you have symlinks for /bin or
/usr/bin?  If you do have symlinks these are known not to work with
setup.exe which is by the way a non-Cygwin executable so it 1) doesn't
understand symlinks and 2) doesn't know about the Cygwin registry wrt
actually using it to find files are concerned.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Paul Garceau]

On 21 Feb 2001, at 16:52, the Illustrious Earnie Boyd wrote:

> Kirran.Bari@sf.frb.org wrote:
> > 
> > Earnie,
> > 
> > You're right - the setup log says that the file was installed
> > right in the bin folder.  The file is there but just hidden.
> > 
> 
> Hidden?  What do you mean hidden?

	Not sure, but think he means that the file is de-archived as a 
hidden file.  This is not unusual with Win9x systems which, by 
default, typically hide anything that looks anything like an 
executable, etc.  (postfixes, etc.).


>Do you have symlinks for /bin
> or /usr/bin?  If you do have symlinks these are known not to work
> with setup.exe which is by the way a non-Cygwin executable so it
> 1) doesn't understand symlinks and 2) doesn't know about the
> Cygwin registry wrt actually using it to find files are
> concerned.

	Win9x/ME, if I remember the original post properly, can't 
support symlinks.

	Peace,

		Paul G.

> 
> Earnie.
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 
> 




Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

Paul Garceau wrote:
>  
> >Do you have symlinks for /bin
> > or /usr/bin?  If you do have symlinks these are known not to work
> > with setup.exe which is by the way a non-Cygwin executable so it
> > 1) doesn't understand symlinks and 2) doesn't know about the
> > Cygwin registry wrt actually using it to find files are
> > concerned.
> 
>         Win9x/ME, if I remember the original post properly, can't
> support symlinks.
> 

Paul, Cygwin emulates symlinks for both WinNT and Win9x.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Paul Garceau]

On 21 Feb 2001, at 19:43, the Illustrious Earnie Boyd wrote:

> Paul Garceau wrote:
> >  
> > >Do you have symlinks for /bin
> > > or /usr/bin?  If you do have symlinks these are known not to
> > > work with setup.exe which is by the way a non-Cygwin
> > > executable so it 1) doesn't understand symlinks and 2)
> > > doesn't know about the Cygwin registry wrt actually using it
> > > to find files are concerned.
> > 
> >         Win9x/ME, if I remember the original post properly,
> >         can't
> > support symlinks.
> > 
> 
> Paul, Cygwin emulates symlinks for both WinNT and Win9x.

	Thanks for the clarification, Earnie.  "Emulation" vs. actual 
symlinks...I understand.

	Peace,

		Paul G.
> 
> Earnie.
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 
> 




Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 04:52 PM 2/21/2001, Earnie Boyd wrote:
>Kirran.Bari@sf.frb.org wrote:
> > 
> > Earnie,
> > 
> > You're right - the setup log says that the file was installed right in the
> > bin folder.  The file is there but just hidden.
> > 
>
>Hidden?  What do you mean hidden?  Do you have symlinks for /bin or
>/usr/bin?  If you do have symlinks these are known not to work with
>setup.exe which is by the way a non-Cygwin executable so it 1) doesn't
>understand symlinks and 2) doesn't know about the Cygwin registry wrt
>actually using it to find files are concerned.
>
>Earnie.



No I believe he means that he is using explorer to view and find things and
that its set up to hide things like DLLs.  Nasty option if you ask me...



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

Kirran.Bari@sf.frb.org wrote:
> 
> Strange.  I downloaded all the files from one of your mirror sites
> yesterday and installed them, and could not find cygwin1.dll anywhere.  I
> wrote you assuming that perhaps the file was obsolete and not part of the
> new release.
> 
> (i.e.  cygwin1.dll does not show up in either the folder 'latest' or the
> installed folder 'cygwin')
> 

Cygwin1.dll is a piece of a package (care to guess which one?).  For
some reason that package did not install properly.  Executing
http://cygwin.com/setup.exe again will only install what wasn't
installed yesterday.  For a clue as to what happened there exists a
setup.log.full in the same path as setup.exe that you can review.

Earnie.

P.S.: I've reset the reply to back to the list and have CC'ed them on
the discussion for your convenience.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

cygwin1.dll

[Kirran.Bari]

Hi

I'm trying to run a program in Matlab for NT that was developed
in its Unix version.  The person who wrote the program is
unavailable.  The program stops short at a dialogue box that
says it can't find cygwin1.dll.  Which file is this and where can I
get it?

KB


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 12:24 PM 2/21/2001, Kirran.Bari@sf.frb.org wrote:
>Hi
>
>I'm trying to run a program in Matlab for NT that was developed
>in its Unix version.  The person who wrote the program is
>unavailable.  The program stops short at a dialogue box that
>says it can't find cygwin1.dll.  Which file is this and where can I
>get it?


Go to www.cygwin.com and click on "Install Now".  If you really only 
need/want Cygwin to run the program you have, you can select only the cygwin
package.  This will get you cygwin1.dll with a minimum of other files.
You need to put the directory with cygwin1.dll in your path for this to 
all work generically in Windows.

Optionally, you can search your system to see if you have this file
already.  It may be that you have it but that its not in a location
that's in your path (or in the same place as the program you're running).



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Christopher Faylor]

On Wed, Feb 21, 2001 at 01:21:40PM -0500, Larry Hall (RFK Partners, Inc) wrote:
>At 12:24 PM 2/21/2001, Kirran.Bari@sf.frb.org wrote:
>>Hi
>>
>>I'm trying to run a program in Matlab for NT that was developed
>>in its Unix version.  The person who wrote the program is
>>unavailable.  The program stops short at a dialogue box that
>>says it can't find cygwin1.dll.  Which file is this and where can I
>>get it?
>
>
>Go to www.cygwin.com and click on "Install Now".  If you really only 
>need/want Cygwin to run the program you have, you can select only the cygwin
>package.  This will get you cygwin1.dll with a minimum of other files.
>You need to put the directory with cygwin1.dll in your path for this to 
>all work generically in Windows.
>
>Optionally, you can search your system to see if you have this file
>already.  It may be that you have it but that its not in a location
>that's in your path (or in the same place as the program you're running).

Also, if this is a commercial program, I'd like to know about it so that
I can get our lawyers involved.  It sounds like it probably isn't adhering
to the GPL.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

Kirran.Bari@sf.frb.org wrote:
> 
> Hi
> 
> I'm trying to run a program in Matlab for NT that was developed
> in its Unix version.  The person who wrote the program is
> unavailable.  The program stops short at a dialogue box that
> says it can't find cygwin1.dll.  Which file is this and where can I
> get it?
> 

http://cygwin.com/setup.exe

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: cygwin1.dll

[Earnie Boyd]

--- Gerrit Haase <gerrit.haase@t-online.de> wrote:
> Hi all,
> 
> > I suggest you try a different mirror to use during setup.
> > 
> > Cheers,
> > 
> > =====
> > Earnie Boyd
> 
> I just wonder what is the meaning of mirror, if there are not the 
> same files on all :-)
> 

They should (sometimes don't) have the same files.  It's the IP connection/
data throughput that's the problem.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[Chris Faylor]

On Fri, Oct 13, 2000 at 11:18:55AM -0700, Earnie Boyd wrote:
>--- Gerrit Haase <gerrit.haase@t-online.de> wrote:
>> Hi all,
>> 
>> > I suggest you try a different mirror to use during setup.
>> > 
>> > Cheers,
>> > 
>> > =====
>> > Earnie Boyd
>> 
>> I just wonder what is the meaning of mirror, if there are not the 
>> same files on all :-)
>> 
>
>They should (sometimes don't) have the same files.  It's the IP connection/
>data throughput that's the problem.

That's right.  sources.redhat.com is pretty swamped and sometimes the mirrors
can't get through to download the latest software.  That is one reason why
mirrors are not always up to date.  If the mirror is set up to only mirror
once every other day and they couldn't get through on the scheduled time
then that puts the mirror out of date.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[Earnie Boyd]

--- AGGIEMISTROT <mistrotm@neo.tamu.edu> wrote:
> Hello all,
> was wondering if anyof you are having this problem?  I just downloaded
> cygwin twice and installed it n two different systems and got the sane
> error.
> It seems the setup utility is not copy  the cygwin1.dll to either system.
> Where can I get the updated dll?
> 

I suggest you try a different mirror to use during setup.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[Gerrit Haase]

Hi all,

> I suggest you try a different mirror to use during setup.
> 
> Cheers,
> 
> =====
> Earnie Boyd

I just wonder what is the meaning of mirror, if there are not the 
same files on all :-)

Gerrit
-- 
Gerrit Haase

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[DJ Delorie]

> I just wonder what is the meaning of mirror, if there are not the 
> same files on all :-)

Mirrors may not be reliable, or may not have updated recently.
Nobody's perfect.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[AGGIEMISTROT]

Hello all,
was wondering if anyof you are having this problem?  I just downloaded
cygwin twice and installed it n two different systems and got the sane
error.
It seems the setup utility is not copy  the cygwin1.dll to either system.
Where can I get the updated dll?

Thanks...
J.M. Mistrot
mistrotm@neo.tamu.edu


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: cygwin1.dll

[Reynolds, John]

> -----Original Message-----
> From: Chris Faylor [ mailto:cgf@cygnus.com ]
> Sent: Tuesday, July 11, 2000 9:02 PM
> To: cygwin@sourceware.cygnus.com
> Subject: Re: cygwin1.dll
> 
[snip]
> I don't know who or what is installing in your winnt\system32 
> directory.
> Normal cygwin setup does not do that.  Remove this version.

I had a previous installation of gnupro-99r1g1 that put cygwin1.dll in a
couple of places but not winnt/system32. Don't know how it got there.
Regardless, deleting all extraneous copies solved my problem. Thanks to
Chris, Larry and Earnie for the help!


     - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is
confidential, proprietary, privileged or otherwise protected by law. The
information is solely intended for the named addressee (or a person
responsible for delivering it to the addressee). If you are not the intended
recipient of this message, you are not authorized to read, print, retain,
copy or disseminate this message or any part of it. If you have received
this e-mail in error, please notify the sender immediately by return e-mail
and delete it from your computer. 

Re: cygwin1.dll

[Earnie Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]

--- "Reynolds, John" <John.Reynolds@sciatl.com> wrote:
> Hello,
> 
> I previously installed cygwin 1.1.2. I had a need to install an earlier
> version and thought I was safe by using a separate tree. I ran into a
> problem running the cygwin port of Perl 5.6.0 and ran cygcheck -s -v and
> found this:
> 
>   755k 1999/09/16 C:\WINNT\System32\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=1999/9/1 6:10
>   575k 2000/06/07 c:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2000/6/6 22:20
> 
> Looks like the installation of the earlier version overwrote
> c:\WINNT\System32\cygwin1.dll. I assume it and the version in c:\cygwin\bin
> should be the same. Can I just copy the newer version into c:\WINNT\System32
> or will I need to reinstall cygwin-1.1.2.tar.gz? Any other files to worry
> about?
> 

AFAIR setup.exe doesn't put cygwin1.dll into the system32 directory.  You had
to copy it there or something else put it there.  Therefore, just delete the
cygwin1.dll in the windows system32 directory.

Regards,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[Reynolds, John]

Hello,

I previously installed cygwin 1.1.2. I had a need to install an earlier
version and thought I was safe by using a separate tree. I ran into a
problem running the cygwin port of Perl 5.6.0 and ran cygcheck -s -v and
found this:

  755k 1999/09/16 C:\WINNT\System32\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=1999/9/1 6:10
  575k 2000/06/07 c:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/6/6 22:20

Looks like the installation of the earlier version overwrote
c:\WINNT\System32\cygwin1.dll. I assume it and the version in c:\cygwin\bin
should be the same. Can I just copy the newer version into c:\WINNT\System32
or will I need to reinstall cygwin-1.1.2.tar.gz? Any other files to worry
about?

Thanks for your help and sorry for the ridiculous lawyer speak that gets
appended to all my emails!


     - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is
confidential, proprietary, privileged or otherwise protected by law. The
information is solely intended for the named addressee (or a person
responsible for delivering it to the addressee). If you are not the intended
recipient of this message, you are not authorized to read, print, retain,
copy or disseminate this message or any part of it. If you have received
this e-mail in error, please notify the sender immediately by return e-mail
and delete it from your computer. 

Re: cygwin1.dll

[Chris Faylor]

On Tue, Jul 11, 2000 at 05:49:32PM -0400, Reynolds, John wrote:
>I previously installed cygwin 1.1.2. I had a need to install an earlier
>version and thought I was safe by using a separate tree. I ran into a
>problem running the cygwin port of Perl 5.6.0 and ran cygcheck -s -v and
>found this:
>
>  755k 1999/09/16 C:\WINNT\System32\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwin1.dll" v0.0 ts=1999/9/1 6:10
>  575k 2000/06/07 c:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwin1.dll" v0.0 ts=2000/6/6 22:20
>
>Looks like the installation of the earlier version overwrote
>c:\WINNT\System32\cygwin1.dll. I assume it and the version in c:\cygwin\bin
>should be the same. Can I just copy the newer version into c:\WINNT\System32
>or will I need to reinstall cygwin-1.1.2.tar.gz? Any other files to worry
>about?
>
>Thanks for your help and sorry for the ridiculous lawyer speak that gets
>appended to all my emails!

There is no reason to install an older version of cygwin.  You are guaranteed
to get into trouble if you have two versions on your system.

I don't know who or what is installing in your winnt\system32 directory.
Normal cygwin setup does not do that.  Remove this version.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[Waker]

hello there.

is there any way to exclude cygwin1.dll from linking? i don't wanna
port any unix app to a win32, but want to compile some application
using cygwin, and cygwin1.dll is not required. how do i do this? is
there somehing like -nodefaultlib? =)

i used following command line:

g++ -o myapp myapp.cpp -Wl,-S,--strip-debug

thanx.

Best regards. Alexey Yakovenko, MW Group       [Frontier2/PC Team]
mailto: work@makpes.donobl.db.energy.gov.ua,
visit NGP(frontier2/pc) web page: http://www.mes.pssr.ru/ngp



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[Brendan Simon]

Waker wrote:

> hello there.
>
> is there any way to exclude cygwin1.dll from linking? i don't wanna
> port any unix app to a win32, but want to compile some application
> using cygwin, and cygwin1.dll is not required. how do i do this? is
> there somehing like -nodefaultlib? =)
>
> i used following command line:
>
> g++ -o myapp myapp.cpp -Wl,-S,--strip-debug
>
> thanx.

I think you want the -mnocygwin option.  Check Mumit Khan's web site
(there is a link to it on the soureceware.cygnus.com/cygwin page) for a
HOWTO on compiling apps that do not require the cygwin1.dll.  Basically
the compiler will link to the Microsoft libraries instead.

Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: cygwin1.dll

[Brendan Simon]

Waker wrote:

> hello there.
>
> is there any way to exclude cygwin1.dll from linking? i don't wanna
> port any unix app to a win32, but want to compile some application
> using cygwin, and cygwin1.dll is not required. how do i do this? is
> there somehing like -nodefaultlib? =)
>
> i used following command line:
>
> g++ -o myapp myapp.cpp -Wl,-S,--strip-debug
>
> thanx.

I think you want the -mnocygwin option.  Check Mumit Khan's web site
(there is a link to it on the soureceware.cygnus.com/cygwin page) for a
HOWTO on compiling apps that do not require the cygwin1.dll.  Basically
the compiler will link to the Microsoft libraries instead.

Brendan Simon.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

cygwin1.dll

[Waker]

hello there.

is there any way to exclude cygwin1.dll from linking? i don't wanna
port any unix app to a win32, but want to compile some application
using cygwin, and cygwin1.dll is not required. how do i do this? is
there somehing like -nodefaultlib? =)

i used following command line:

g++ -o myapp myapp.cpp -Wl,-S,--strip-debug

thanx.

Best regards. Alexey Yakovenko, MW Group       [Frontier2/PC Team]
mailto: work@makpes.donobl.db.energy.gov.ua,
visit NGP(frontier2/pc) web page: http://www.mes.pssr.ru/ngp



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com